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 attempting to apply an errata to a host, whose katello agent wasn't being recognized, you are given a 400 error. Looking into journalctl while running the command gives the error below. This may be because the katello-agent is needed to determine applicable errata.
pulp.server.webservices.middleware.exception:INFO: Unable to find errata with unit_key [{'id': 'RHBA-2015:1910'}] in bound repos [[u'Default_Organization-rhel72_base-rhel7_repo']] to consumer [38129cab-92c0-4dd9-96c3-9f0ac11e001a]
Version-Release number of selected component (if applicable):
Satellite 6.2 Beta Snap 9.
How reproducible:
Always
Steps to Reproduce:
1. Supply a valid errata id when attempting to apply errata to a host that either doesn't have katello agent installed, or that satellite isn't recognizing katello agent properly
2. Check the error message that is returned
Actual results:
[root@qeblade36 ~]# hammer host errata apply --host-id 3 --errata-ids RHBA-2015:1910
[..............................................................................................................] [100%]
400 Bad Request
Expected results:
[root@qeblade36 ~]# hammer -u admin -p changeme host errata apply --host-id 3 --errata-ids RHBA-2015:1910
Unable to find errata with id 'RHBA-2015:1910' that can be applied to <host name>
Comment 3Zach Huntington-Meath
2016-04-27 17:40:22 UTC
The issue from this appears to come from the version of Restclient that we are using. When it returns a response with a code of 400 it doesn't give the whole response, just a 400 error. https://git.io/vwrGg
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the 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: When attempting to apply an errata to a host, whose katello agent wasn't being recognized, you are given a 400 error. Looking into journalctl while running the command gives the error below. This may be because the katello-agent is needed to determine applicable errata. pulp.server.webservices.middleware.exception:INFO: Unable to find errata with unit_key [{'id': 'RHBA-2015:1910'}] in bound repos [[u'Default_Organization-rhel72_base-rhel7_repo']] to consumer [38129cab-92c0-4dd9-96c3-9f0ac11e001a] Version-Release number of selected component (if applicable): Satellite 6.2 Beta Snap 9. How reproducible: Always Steps to Reproduce: 1. Supply a valid errata id when attempting to apply errata to a host that either doesn't have katello agent installed, or that satellite isn't recognizing katello agent properly 2. Check the error message that is returned Actual results: [root@qeblade36 ~]# hammer host errata apply --host-id 3 --errata-ids RHBA-2015:1910 [..............................................................................................................] [100%] 400 Bad Request Expected results: [root@qeblade36 ~]# hammer -u admin -p changeme host errata apply --host-id 3 --errata-ids RHBA-2015:1910 Unable to find errata with id 'RHBA-2015:1910' that can be applied to <host name>