Description of problem: Clean install RHEV-H,configure network,then navigate to the RHEVM configuration screen,input correct "Management Server" and "Management Server Port",choose apply,after register rhevh into rhevm successfully, navigate to the Network page, check info "Managed by RHEV-M(Read Only)" on that page, so all labels should be grayed out,but hostname still could be reset. Version-Release number of selected component (if applicable): rhev-hypervisor6-6.4-20121015.1.el6 How reproducible: 100% Steps to Reproduce: 1. Install RHEV-H. 2. Configure network 3. Navigate to the RHEVM configuration screen,input correct "Management Server" and "Management Server Port",choose apply 4. After register rhevh into rhevm successfully, navigate to the Network page Actual result:. After step 4,check that info "Managed by RHEV-M(Read Only)" on that page, so all labels should be grayed out,but hostname still could be reset, Expect result: If prompt that "Managed by RHEV-M(Read Only)" on network page, so all labels should be grayed out and couldn't be edited
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
(In reply to haiyang,dong from comment #0) > Description of problem: > Clean install RHEV-H,configure network,then navigate to the RHEVM > configuration screen,input correct "Management Server" > and "Management Server Port",choose apply,after register rhevh into rhevm > successfully, navigate to the Network page, > check info "Managed by RHEV-M(Read Only)" on that page, so all labels should > be grayed out,but hostname still could be reset. What happens if user decided one day after the registration that he wants this RHEV-H registered as another hostname in another instance of RHEV-M? Suggesting user to press F2 go to shell etc doesn't look good to me. I do believe we might want to keep this as it's. Fabian, Arthur thoughts?
Hey, my general thinking would be: When RHEV-H is registered, lock all relevant places which shall not be editable by the user. That means we need to determine what details should not be changed by the user after RHEV-H has been registered. I.e. should it be allowed to change the hostname after registration? How is a host identified by engine? Based on the fqdn or ip? Second - We should provide a way to unregister from an engone which then let's the user (a) edit all fields again and (b) let the user connect RHEV-H to a different Engine.
Douglas, Can you please disable the change of hostname through TUI, once this host was registered.
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.