Bug 783625

Summary: The setup command should only allow password setting and viewing logs in single mode.
Product: Red Hat Enterprise Linux 5 Reporter: cshao <cshao>
Component: ovirt-nodeAssignee: Joey Boggs <jboggs>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.8CC: apevec, bgollahe, bsarathy, gouyang, jboggs, leiwang, lmiksik, mburns, mjenner, moli, ovirt-maint, sgordon, ycui
Target Milestone: rc   
Target Release: 5.8   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-node-1.0-84.el5 Doc Type: Bug Fix
Doc Text:
Previously when the Hypervisor was started in single user mode it was possible to view and change all configuration options when running the setup command. As of this update when the Hypervisor is started in single user mode only the password change and log viewing functionality is available.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-21 05:06:13 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 cshao 2012-01-21 06:17:47 UTC
Description of problem:
The setup command should only allow password setting and viewing logs while in single mode.

Version-Release number of selected component (if applicable):
rhev-hypervisor5-5.8-20120118.0.el5

How reproducible:
100%

Steps to Reproduce:
1. Auto install RHEV-H.
2. Enter single mode.
3. Run "setup" command.
  
Actual results:
- Configure authentication
- Set the hostname
- Networking setup
- Register Host to RHN
- Configure the host for RHEV
- View log
- Exit

Expected results:
In single mode keep only:
- Configure authentication
- View log
- Exit

Additional info:
There is a related bug 718703.

Comment 4 Guohua Ouyang 2012-01-31 06:52:35 UTC
Verified on 5.8-20120130 build, run setup in single mode can only see:
- Configure authentication
- View log
- Exit

Comment 5 Mike Burns 2012-02-09 21:24:09 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When running in single mode, a user could access all configuration options when running the setup command.  Now they only have access to changing the password with the setup command.

Comment 6 Stephen Gordon 2012-02-09 21:32:19 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When running in single mode, a user could access all configuration options when running the setup command.  Now they only have access to changing the password with the setup command.+Previously when the Hypervisor was started in single user mode it was possible to view and change all configuration options when running the setup command. As of this update when the Hypervisor is started in single user mode only the password is able to be changed.

Comment 7 Stephen Gordon 2012-02-09 21:52:48 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-Previously when the Hypervisor was started in single user mode it was possible to view and change all configuration options when running the setup command. As of this update when the Hypervisor is started in single user mode only the password is able to be changed.+Previously when the Hypervisor was started in single user mode it was possible to view and change all configuration options when running the setup command. As of this update when the Hypervisor is started in single user mode only the password change and log viewing functionality is available.

Comment 8 errata-xmlrpc 2012-02-21 05:06:13 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.

http://rhn.redhat.com/errata/RHSA-2012-0168.html