Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1696862 - foreman-maintain service restart - should not require foreman-maintain-hammer.yml [NEEDINFO]
Summary: foreman-maintain service restart - should not require foreman-maintain-hammer...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Foreman Maintain
Version: 6.4.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: Unspecified
Assignee: Anurag Patel
QA Contact: Nikhil Kathole
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-05 19:04 UTC by sthirugn@redhat.com
Modified: 2019-04-06 05:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
bbuckingham: needinfo? (apatel)


Attachments (Terms of Use)

Description sthirugn@redhat.com 2019-04-05 19:04:36 UTC
Description of problem:
foreman-maintain service restart - requires hammer password

Version-Release number of selected component (if applicable):
satellite-6.5.0-11.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:

On satellite 6.4:
*****************
# rpm -q satellite
satellite-6.4.2-2.el7sat.noarch

# rpm -q rubygem-foreman_maintain
rubygem-foreman_maintain-0.2.11-1.el7sat.noarch

# ll /etc/foreman-maintain
total 4
-rw-r-----. 1 root root 880 Sep 26  2018 foreman_maintain.yml

# katello-service restart
Redirecting to 'foreman-maintain service'
Running Restart Services
================================================================================
Check if command is run as root user:                                 [OK]
--------------------------------------------------------------------------------
Restart applicable services: 
Stopping the following service(s):
rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflowd, goferd, httpd, puppetserver, foreman-proxy
\ All services stopped              


Satellite 6.5:
**************
# rpm -q satellite
satellite-6.5.0-11.el7sat.noarch

# rpm -q rubygem-foreman_maintain
rubygem-foreman_maintain-0.3.2-1.el7sat.noarch

# rm /etc/foreman-maintain/foreman-maintain-hammer.yml 
rm: remove regular file ‘/etc/foreman-maintain/foreman-maintain-hammer.yml’? y

# katello-service restart
Redirecting to 'foreman-maintain service'
Running preparation steps required to run the next scenarios
================================================================================
Setup hammer: 
Configuring Hammer CLI...
Hammer admin password: 
<ctrl+c>

# foreman-maintain service restart
Running preparation steps required to run the next scenarios
================================================================================
Setup hammer: 
Configuring Hammer CLI...
Hammer admin password: 

Actual results:
The new behavior of `katello-service restart` and `foreman-maintain service restart` requiring hammer credentials affects clone/upgrade scenarios using satellite-clone which happens in an automated fashion. There may be other scenarios which are affected too.

Expected results:
Traditionally `katello-service restart` and now `foreman-maintain service restart` never needed hammer password. It should continue remaining the same in Satellite 6.5.

Additional info:

Comment 4 Brad Buckingham 2019-04-05 19:28:58 UTC
Hi Anurag,

Can you or someone on foreman-maintain take a quick look at this bugzilla.  Is this change in behavior intended or required?

This bug originated from investigation in to the following bugzilla created for satellite-clone: bug 1696731.


Note You need to log in before you can comment on or make changes to this bug.