Created attachment 665462 [details] screenshot of the error Description of problem: Edit Server option under Maintenance Mode is not working as expected. Version-Release number of selected component (if applicable): rhsc-2.1-qa18.el6ev How reproducible: Always Steps to Reproduce: 1. Place a servers into maintenance mode. 2. Once the "Status" shows as "Maintenance", click on "Edit" 3. You will see the option to edit two fields: "Server Cluster" and "Name". 4. Try to edit any of the fields and Click OK. Actual results: You will see the following error message: --------------- Error: xx.xx.xx.xx: Cannot edit Host. Host parameters cannot be modified while Host is operational. Please switch Host to Maintenance mode first. --------------- Note that the server is actually in Maintenance mode! :) Expected results: If we are allowing the users to edit the server in maintenance mode, it should succeed without any error. Additional info: Screenshots attached.
Engine logs please
(In reply to comment #2) > Engine logs please Since I've reinstalled the machine with the latest QA build, I'm unable to collect the engine logs for you. But I did tried to reproduce the issue with a fresh installation of the QA3 and also QA4 release and it's not reproducible now. Not sure the reason for that.
Created attachment 688982 [details] Engine logs I was able to reproduce this again in QA4. Attaching the engine.log
Edit Host in Maintenance fails when trying to edit a host that has been imported in the cluster. Reason: sshkeyfingerprint has value in db but no value is returned from UI. This field is seen as changed but this is not an updateable field
While one part of the fix is to send the fingerprint to engine, the error message clearly seems to be incorrect - it should say that fingerprint mismatch detected, or something like that. Sahina, can you please check this? Prasanth, can you confirm that this happens only in case of servers that got added to the cluster as part of "import gluster cluster" operation, and works fine if the server was added using "add server"?
(In reply to comment #6) > While one part of the fix is to send the fingerprint to engine, the error > message clearly seems to be incorrect - it should say that fingerprint > mismatch detected, or something like that. Sahina, can you please check this? > > Prasanth, can you confirm that this happens only in case of servers that got > added to the cluster as part of "import gluster cluster" operation, and > works fine if the server was added using "add server"? Shireesh, Yes, I can confirm that this happens only when I try to edit a host that has been imported in the cluster. The other servers that were added using "add server" doesn't show this error.
Patch sent to upstream: http://gerrit.ovirt.org/12218
verified in 2.1.0-0.qa7.el6rhs
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/RHBA-2013-1262.html