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.

Bug 1289133

Summary:	[RFE] Allow hammer hostgroup to set/update the root password field
Product:	Red Hat Satellite	Reporter:	Stephen Benjamin <stbenjam>
Component:	Hammer	Assignee:	Shlomi Zadok <szadok>
Status:	CLOSED ERRATA	QA Contact:	Corey Welton <cwelton>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.4	CC:	bbuckingham, bkearney, cwelton, sthirugn, xdmoon
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/11236
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 11:24:11 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:

Description Stephen Benjamin 2015-12-07 13:59:16 UTC

When you create a host group and associate it with an operating system, it is often useful to set the password (root) so that when you provision a system associated to this host group, you know what password to use when trying to ssh into the system. Currently one cannot use hammer hostgroup command to do that.

I'd like to request an improvement to hammer hostgroup so that one can set/update the password field. Perhaps something like:

<pre>
hammer hostgroup update --name=<name of existing host group> --password=<new value>
</pre>

or

<pre>
hammer hostgroup update --id=<id for existing host group> --password=<new value>
</pre>

This would be useful for automating provisioning scenarios via hammer.

Comment 1 Stephen Benjamin 2015-12-07 13:59:17 UTC

Created from redmine issue http://projects.theforeman.org/issues/11236

Comment 2 Stephen Benjamin 2015-12-07 13:59:22 UTC

Upstream bug assigned to szadok

Comment 3 Stephen Benjamin 2015-12-07 14:02:17 UTC

Would need: 

https://github.com/theforeman/hammer-cli-foreman/commit/84db9a65c44c6d4cbaf34cfd034e140d9a08f7bd

https://github.com/theforeman/foreman/commit/8caf49dbe303f791b8bde3065aae535601d959f0

Comment 8 Tazim Kolhar 2016-04-05 04:02:51 UTC

VERIFIED:
# rpm -qa foreman
foreman-1.11.0.9-1.el7sat.noarch



# hammer hostgroup update --id 1 --root-pass '*****'
[Foreman] Password for admin: 
Hostgroup updated


2016-04-05 00:01:07 [app] [I] Started PUT "/api/hostgroups/1" for ::1 at 2016-04-05 00:01:07 -0400
2016-04-05 00:01:07 [app] [I] Processing by Api::V2::HostgroupsController#update as JSON
2016-04-05 00:01:07 [app] [I]   Parameters: {"hostgroup"=>{"puppet_proxy_id"=>nil, "puppet_ca_proxy_id"=>nil, "puppetclass_ids"=>nil, "root_pass"=>"[FILTERED]"}, "apiv"=>"v2", "id"=>"1"}
2016-04-05 00:01:07 [app] [D] Setting current user thread-local variable to foreman_admin
2016-04-05 00:01:07 [app] [D] Setting current user thread-local variable to nil
2016-04-05 00:01:07 [app] [D] Setting current user thread-local variable to foreman_admin
2016-04-05 00:01:07 [app] [D] Setting current user thread-local variable to nil
2016-04-05 00:01:07 [app] [D] Setting current user thread-local variable to admin
2016-04-05 00:01:07 [app] [I] Authorized user admin(Admin User)
2016-04-05 00:01:07 [app] [D] Setting current user thread-local variable to admin
2016-04-05 00:01:07 [app] [D] Setting current location thread-local variable to none
2016-04-05 00:01:07 [app] [D] Setting current organization thread-local variable to none
2016-04-05 00:01:07 [app] [I]   Rendered api/v2/hostgroups/update.json.rabl (39.3ms)
2016-04-05 00:01:07 [app] [D] Body: {"subnet_id":1,"subnet_name":"test_subnet","operatingsystem_id":2,"operatingsystem_name":"RedHat 7.3","domain_id":1,"domain_name":"rhts.eng.bos.redhat.com","environment_id":1,"environment_name":"production","compute_profile_id":null,"compute_profile_name":null,"ancestry":null,"parent_id":null,"parent_name":null,"puppet_proxy_id":null,"puppet_ca_proxy_id":null,"ptable_id":61,"ptable_name":"Kickstart default","medium_id":9,"medium_name":"Default_Organization/Library/rhel7/rhel7_repo","architecture_id":1,"architecture_name":"x86_64","realm_id":null,"realm_name":null,"created_at":"2016-04-04 13:16:54 UTC","updated_at":"2016-04-05 04:01:07 UTC","id":1,"name":"hostgrp","title":"hostgrp","parameters":[],"template_combinations":[],"puppetclasses":[],"config_groups":[],"all_puppetclasses":[],"locations":[{"id":2,"name":"Default Location","title":"Default Location","description":null}],"organizations":[{"id":1,"name":"Default Organization","title":"Default Organization","description":null}]}
2016-04-05 00:01:07 [app] [I] Completed 200 OK in 116ms (Views: 34.0ms | ActiveRecord: 20.2ms)

Comment 11 Bryan Kearney 2016-07-27 11:24:11 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