Bug 749454

Summary:	RFE: running tests should know current root password
Product:	[Retired] Beaker	Reporter:	Karel Srot <ksrot>
Component:	scheduler	Assignee:	Nick Coghlan <ncoghlan>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.5	CC:	bpeck, dcallagh, mcsontos, mishin, rmancy, stl
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	MC
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-11-07 07:23:18 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Karel Srot 2011-10-27 05:31:33 UTC

Description of problem:

Once the beaker infrastructure is changed and provisioned systems gets random root password, we will to know the root password in order to properly perform some RHTS tests.
Probably the best solution for us is to have the root password available through some environment variable (or stored in a file readable by root). 

There were some "workarounds"/solutions suggested on the beaker-devel list:

ssh keys - doesn't solve the problem with run_init command that needs the root password

changing root password in the test and restore it later - possible, but not the best solution for shared system - dedicated beaker system is not the only environment we use for test execution

password defined in kickstart - not possible for shared or already provisioned systems


Global variable with the root password requires minimal or none changes in current tests. I also believe that providing the root password to the running test is not a security issue for beaker systems (since the test itself is able to change it)

Comment 1 Bill Peck 2011-10-27 13:18:05 UTC

(In reply to comment #0)
> Description of problem:
> 
> Once the beaker infrastructure is changed and provisioned systems gets random
> root password, we will to know the root password in order to properly perform
> some RHTS tests.
> Probably the best solution for us is to have the root password available
> through some environment variable (or stored in a file readable by root). 
> 
> There were some "workarounds"/solutions suggested on the beaker-devel list:
> 
> ssh keys - doesn't solve the problem with run_init command that needs the root
> password
> 
> 

What is run_init?  and why will it not work with ssh_keys?

Thanks

Comment 2 Karel Srot 2011-10-31 06:34:18 UTC

run_init is a binary from policycoreutils package

DESCRIPTION
Run  a  init  script  under  the  proper context, which is specified in /etc/selinux/POLICY-TYPE/contexts/initrc_context.

This is necessary with MLS SELinux policy but we are testing it also with targeted policy.

> why will it not work with ssh_keys?

run_init prompts the user for the password. Please ask Dan Walsh regarding details.

Comment 3 Nick Coghlan 2012-10-17 04:36:28 UTC

Bulk reassignment of issues as Bill has moved to another team.

Comment 4 Min Shin 2012-11-07 07:23:18 UTC

This bugs is closed as it is either not in the current Beaker scope or we could not find sufficient data in the bug report for consideration.
Please feel free to reopen the bug with additional information and/or business cases behind it.