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-03-23 17:43:49 UTC
Description of problem:
Applying errata to a content host in a non-incremental update way via the new errata page failed
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-6-20150317.0
How reproducible:
Always
Steps to Reproduce:
1. Create two content views with filters so one has errata and the other doesnt.
2. Register two content hosts to each of these content views
3. Go to Content -> Errata -> Select an errata
4. It showed me 2 content hosts as expected
5. Now uncheck 'Only show content hosts where is currently installable in the host's Lifecycle Environment'.
6. I expected to see one content hosts and it showed up correctly
7. Now select the content host and click Next
8. Apply the errata
Actual results:
Failed with the following error in production.log
[ERROR 2015-03-23 13:30:53 pulp_rest #13143] RestClient.delete "https://ibm-x3250m4-05.lab.eng.rdu2.redhat.com/pulp/api/v2/consumer_groups/37d95da4-ef2b-42df-be3c-70b0e0a547cc/", "Accept"=>"*/*; q=0.5, application/xml", "Accept-Encoding"=>"gzip, deflate", "Authorization"=>"OAuth oauth_consumer_key=\"katello\", oauth_nonce=\"Bcc2vJzWaNc7LThXnjRukexVEIlL7n0sh0jb7nCk\", oauth_signature=\"YDs9tmXsOyXcha4AAk50QLVC3zA%3D\", oauth_signature_method=\"HMAC-SHA1\", oauth_timestamp=\"1427131853\", oauth_version=\"1.0\"", "accept"=>"application/json", "content_type"=>"application/json", "pulp-user"=>"admin-c8719da6"
| \n# => 200 OK | application/json 24 bytes
Expected results:
Errata is applied in the content host
Additional info:
When I tried to redo the same scenario - this is what happened:
1. Go to Content -> Errata -> Select an errata
2. It showed me 2 content hosts as expected
3. Now uncheck 'Only show content hosts where is currently installable in the host's Lifecycle Environment'.
4. I expected to see one content hosts and it showed up correctly
5. Now select the content host and click Next
6. Apply the errata
7. Now it said "You must select at least one Content Host in order to apply Errata."
Comment 2sthirugn@redhat.com
2015-03-23 17:50:48 UTC