Bug 1405493
Summary: | use /rhsm api to update content host facts | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Bryan Kearney <bkearney> |
Component: | Hammer | Assignee: | Tom McKay <tomckay> |
Status: | CLOSED ERRATA | QA Contact: | Jonathon Turel <jturel> |
Severity: | medium | Docs Contact: | |
Priority: | high | ||
Version: | 6.2.0 | CC: | bbuckingham, bkearney, dhlavacd, inecas, jcallaha, jturel, mhulan, tomckay, tstrachota |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1400697 | Environment: | |
Last Closed: | 2018-02-21 16:51:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1400697 | ||
Bug Blocks: |
Comment 2
Bryan Kearney
2016-12-16 18:55:30 UTC
Upstream bug component is Hammer Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17453 has been resolved. Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/17453 has been resolved. Verified against Sat 6.3 Snap 14 => I was able to update the facts for my content host via the following curl: curl -X PUT --cert /etc/pki/consumer/cert.pem --key /etc/pki/consumer/key.pem -H 'content-type: application/json' https://sat63-qa-rhel7.strangeways.example.com/rhsm/consumers/9047470a-2e65-41df-a586-a5d3c916f2cf/ -d '{"facts":{"myfact":"myvalue"}}' -k {"content":"Facts successfully updated."} Confirmed the save via hammer: hammer -u admin -p changeme fact list <snip> strangeways.usersys.redhat.com | myfact | myvalue </snip> 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-2018:0336
|