Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When trying to create an incremental update to a Content View (CV) version, applying some errata, it requires the environments to be listed where the version is, whereas there are cases where the CV version only lives in the Library or doesn't live in any Life Cycle Environment (LCE).
Version-Release number of selected component (if applicable):
6.1.7
How reproducible:
Always
Steps to Reproduce:
1. $ hammer content-view version incremental-update --content-view-version "xxx" --errata-ids yyy
Actual results:
The command fails.
Expected results:
The command succeeds and just applies the given errata(s) to the given CV version and creates a new CV minor version.
Additional info:
My use case:
LCEs are Library, Test, Prod
CV v1, v2 and v3 are in the Library (because CVa is never used directly, only through CCV)
CV v1 is used by CCV (Composite CV) in v10 promoted to Prod
CV v2 is used by CCV in v11 promoted to Test
CV v3 is used by CCV in v12 only published in Library
I want now to:
- add errata to CV v1, v2 and v3 generating v1.1, v2.1 and v3.1
- update CCV v10 to v1.1, CCV v11 to v2.1 and CCV v12 to v3.1 at a later stage
Note that CV might be used by other CCVs, but I don't think that's relevant here.
Moving to POST since upstream bug http://projects.theforeman.org/issues/14439 has been closed
-------------
Justin Sherrill
Applied in changeset commit:hammer-cli-katello|3a56a55a7ddc1f2aad4b9a061aff77204dfed18c.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2016:1501