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:
Attempting to apply an un-applicable errata to some content host (i.e. errata from some repository disabled on the content host) via hammer, Satellite's task finishes with warning, but hammer responds "Errata applied successfully". That makes wrong assumption the errata was applied.
Version-Release number of selected component (if applicable):
Sat 6.1.7
rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch
rubygem-hammer_cli_foreman_docker-0.0.3.10-1.el7sat.noarch
rubygem-hammer_cli_katello-0.0.7.21-1.el7sat.noarch
rubygem-hammer_cli_foreman-0.1.4.15-1.el7sat.noarch
rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch
rubygem-hammer_cli-0.1.4.13-1.el7sat.noarch
rubygem-hammer_cli_gutterball-0.0.1.3-1.el7sat.noarch
rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch
rubygem-hammer_cli_import-0.10.20-1.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. Have a content host (not capsule) and try to apply capsule-related errata:
hammer> content-host errata apply --errata-ids RHBA-2016:0076 --organization-id 1 --content-host-id 4b88921f-ff1b-474b-a657-90bd9b022638
Actual results:
Errata applied successfully
Expected results:
Ideally, provide equivalent information what pulp logs to /var/log/messages:
Feb 25 10:32:17 pmoravec-sat61-rhel7 pulp: pulp.server.webservices.middleware.exception:INFO: Unable to find errata with unit_key [{'id': 'RHBA-2016:0076'}] in bound repos [[u'Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Satellite_Tools_6_1_for_RHEL_7_Server_RPMs_x86_64', u'Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server']] to consumer [4b88921f-ff1b-474b-a657-90bd9b022638]
or at least the warning details from WebUI (here:
Error:
RestClient::BadRequest
400 Bad Request
though I do think this error should have the pulp error detail as well)
Additional info:
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: Attempting to apply an un-applicable errata to some content host (i.e. errata from some repository disabled on the content host) via hammer, Satellite's task finishes with warning, but hammer responds "Errata applied successfully". That makes wrong assumption the errata was applied. Version-Release number of selected component (if applicable): Sat 6.1.7 rubygem-hammer_cli_foreman_tasks-0.0.3.5-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.10-1.el7sat.noarch rubygem-hammer_cli_katello-0.0.7.21-1.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.15-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch rubygem-hammer_cli-0.1.4.13-1.el7sat.noarch rubygem-hammer_cli_gutterball-0.0.1.3-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch rubygem-hammer_cli_import-0.10.20-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. Have a content host (not capsule) and try to apply capsule-related errata: hammer> content-host errata apply --errata-ids RHBA-2016:0076 --organization-id 1 --content-host-id 4b88921f-ff1b-474b-a657-90bd9b022638 Actual results: Errata applied successfully Expected results: Ideally, provide equivalent information what pulp logs to /var/log/messages: Feb 25 10:32:17 pmoravec-sat61-rhel7 pulp: pulp.server.webservices.middleware.exception:INFO: Unable to find errata with unit_key [{'id': 'RHBA-2016:0076'}] in bound repos [[u'Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Satellite_Tools_6_1_for_RHEL_7_Server_RPMs_x86_64', u'Default_Organization-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_RPMs_x86_64_7Server']] to consumer [4b88921f-ff1b-474b-a657-90bd9b022638] or at least the warning details from WebUI (here: Error: RestClient::BadRequest 400 Bad Request though I do think this error should have the pulp error detail as well) Additional info: