Bug 1330603

Summary: Katello should be using host.comment instead of content_host.description
Product: Red Hat Satellite Reporter: Walden Raines <walden>
Component: HostsAssignee: Walden Raines <walden>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: NightlyCC: sghai, sthirugn
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/14822
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 11:06:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1326347    
Attachments:
Description Flags
the updated comment for host, is shown in webUI under content-host -> description none

Description Walden Raines 2016-04-26 14:42:21 UTC
Need to update katello to use host.comment rather than the deprecated content_host.description.  We also need to migrate content_host.description to host.comment as part of this fix.

Comment 1 Walden Raines 2016-04-26 14:42:23 UTC
Created from redmine issue http://projects.theforeman.org/issues/14822

Comment 2 Walden Raines 2016-04-26 14:42:27 UTC
Upstream bug assigned to walden

Comment 3 Walden Raines 2016-04-26 14:43:50 UTC
This bugzilla is basically just to track the katello changes needed for bug #1326347.

Comment 4 Walden Raines 2016-04-26 15:39:11 UTC
PR - https://github.com/Katello/katello/pull/5998

Comment 5 Bryan Kearney 2016-04-26 15:54:56 UTC
Upstream bug component is Hosts

Comment 7 Walden Raines 2016-04-28 13:50:24 UTC
Note when testing this that content_host.description has been removed and migrated to the existing field host.comment.

Comment 8 Bryan Kearney 2016-04-28 16:18:00 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14822 has been closed

Comment 9 Sachin Ghai 2016-05-12 09:57:31 UTC
Verified with sat6.2 GA snap10

As per host-unification feature, we don't have --description in hammer for content-host. This has been migrated to host as --comment.

~]# hammer -u admin -p changeme host create --help | grep comment
 --comment COMMENT                         Additional information about this host
[root@cloud- ~]# hammer -u admin -p changeme host update --help | grep comment
 --comment COMMENT                         Additional information about this host


Content-host doesn't have 'create' sub-command and neither --description option for "content-host update"


Here I updated the description/comment of a existing host:


[root@cloud- ~]# hammer -u admin -p changeme host list | grep test-host-comment
5  | test-host-comment 

# hammer -u admin -p changeme host update --comment 'testing description fields' --id 5
Host updated


----------------------------|------------------|------------|---------------|------------------
[root@cloud-qe-3 ~]# hammer -u admin -p changeme host info --id 5
Id:                 5
Name:               test-host-comment
Organization:       Default Organization
Location:           Default Location
Puppet CA Id:       
Puppet Master Id:   
Cert name:          test-host-comment
Managed:            no
Installed at:       
Last report:        
Network:            
    IP:  
    MAC:
Network interfaces: 
 1) Id:          10
    Identifier:  
    Type:        interface (primary, provision)
    MAC address: 
    IP address:  
    FQDN:
Operating system:   
    Build:                  no
    Custom partition table:
Parameters:         

Additional info:    
    Owner Id:   3
    Owner Type: User
    Enabled:    yes
    Comment:    
      testing description fields

Comment 10 Sachin Ghai 2016-05-12 09:59:01 UTC
Created attachment 1156620 [details]
the updated comment for host, is shown in webUI under content-host -> description

Comment 11 Bryan Kearney 2016-07-27 11:06:12 UTC
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/RHBA-2016:1501