Hide Forgot
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)
(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
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.
Bulk reassignment of issues as Bill has moved to another team.
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.