Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-38131

Rolling CV empty environment behavior is inconsistent

XMLWordPrintable

    • None
    • Hide
      .Creating a rolling content view without an environment causes error

      Creating a rolling content view without specifying an environment produces an error, in both UI and CLI.

      To work around this problem, use an existing library environment or create a new one when creating a rolling content view.
      Show
      .Creating a rolling content view without an environment causes error Creating a rolling content view without specifying an environment produces an error, in both UI and CLI. To work around this problem, use an existing library environment or create a new one when creating a rolling content view.
    • None
    • None

      Description of problem:

      2 issues:

      1) [root@ip-10-0-167-66 ~]# hammer content-view create --name test2 --organization-id 3 --rolling Could not create the content view: undefined method `any?' for nil:NilClass

      2) The UI allows you to make rolling CVs without any environment, which is pointless. No content will be distributed.

      How reproducible:

      100%

      Is this issue a regression from an earlier version:

      Yes

      Steps to Reproduce:

      hammer content-view create --name test2 --organization-id 3 --rolling

      Actual behavior:
      Ugly error is thrown when nil is passed for environment IDs

      When [] is passed for environment IDs, the rolling CV has no environments, which is pointless

      The UI also allows for the above, which needs fixing.

      Expected behavior:
      Library is assumed if no environments are passed in the API and the UI.

      Business Impact / Additional info:

       

              Unassigned Unassigned
              iballou@redhat.com Ian Ballou
              Vladimír Sedmík Vladimír Sedmík
              Jan Fiala Jan Fiala
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: