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.
Descriptionsthirugn@redhat.com
2015-02-20 17:41:16 UTC
Description of problem:
Content hosts -> Errata tab: Add helptext to inform Applicable errata cannot be applied
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150217.0
How reproducible:
Always
Steps to Reproduce:
1. Upload a manifest, sync a repo (with errata)
2. Create multiple environments say Library -> QE
3. Create content view (cv3) and make sure Library has more errata than QE environment
4. Register a content host to QE environment
Actual results:
Go to Content host -> Errata tab
- 1. Select Current Environment (QE/cv3) - shows 'Installable errata'.
- 2. Select Previous Environment (Library/cv3) - shows 'Applicable errata'
- 3. Select Library Synced Content - shows 'Applicable errata'
For scenarios 2 and 3 above, I am not able to actually install errata as part of Incremental updates. I learnt later that Incremental Updates can be applied only from Content -> 'Errata'
Expected results:
For scenarios 2 and 3 above, make it obvious to the user that these are not installed by
- Adding clear help text that this is view only and install of these errata can be done only from Content -> Errata page.
- greying out errata selection options
and anything else which is necessary
Additional info:
Moving to POST since upstream bug http://projects.theforeman.org/issues/9670 has been closed
-------------
Walden Raines
Applied in changeset commit:katello|e077aa1b15c639a98f2ae9e8e59007ebd5f55a5b.
Comment 7sthirugn@redhat.com
2015-03-12 16:59:36 UTC
Verified.
Now when I select applicable errata in content host -> errata tab, I see the following:
Some of the Errata shown below may not be installable as they are not in this Content Host's Content View and Lifecycle Environment. In order to apply such Errata an Incremental Update is required. Click here to select Errata for an Incremental Update.
Version Tested:
Satellite-6.1.0-RHEL-6-20150311.1
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/RHSA-2015:1592