Bug 1338780
Summary: | Unable to update content host name via hammer | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Andrii Balakhtar <abalakht> |
Component: | Hammer | Assignee: | Andrew Kofink <akofink> |
Status: | CLOSED ERRATA | QA Contact: | Peter Ondrejka <pondrejk> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | akofink, bbuckingham, jsherril |
Target Milestone: | Unspecified | Keywords: | Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
URL: | http://projects.theforeman.org/issues/15589 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-21 16:54:17 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Andrii Balakhtar
2016-05-23 12:20:35 UTC
Note, that as part of host unification hosts and content hosts are now combined into one object, (the host object). So you can update the host's name (via hammer host update), but we really aren't supporting updating of the hammer content host view's name anymore. Created redmine issue http://projects.theforeman.org/issues/15589 from this bug Moving to POST since upstream bug http://projects.theforeman.org/issues/15589 has been closed Verified in Sat 6.3 snap 5. The content-host sub-command has been removed but the update procedure works correctly under host: # hammer host subscription register --content-view-id="1" --organization-id="31" --name="XehsTnSPdubYUBECpJJq" --lifecycle-environment-id="1" # hammer host update --id="5" --new-name updated-name Host updated 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
|