Description of problem: The field "Memory Size" is editable when a VM is in UP state. This field should be disabled as the memory cannot be changed when the VM is up. Version-Release number of selected component (if applicable): RHEV 3.3.1-0.48 How reproducible: 100% Steps to Reproduce: 1. Start a VM 2. Edit the VM 3. Choose "System" menu 4. Enter a number to the "Memory size" field Actual results: It is possible to put a number Expected results: The field is disabled and the number is inpossible to fill.
what happens if you click ok? does the action continue and the vm is updated? or there is some error to the user? i verified on latest master this value indeed editable in UI, but if approving (change the value and click ok) there is a message to the user (canDoAction)
To add some further background here. The customer wants to hand over day to day operation of their RHEV environment to an operations team and wants to make things as foolproof as possible for them. So from their view the field should not be accessible unless it actually lets you change something.
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=6213964b16679d207e06f6ac3b85edc6d6bff22f
Window is still editable, although after trying to change the value, user receives an error: Error while executing action: RHEL6_5_VM3: There was an attempt to change VM values while the VM is not down. Please shut down the VM in order to modify these properties. As window is still editable I'm returning this bug to assigned. Package on my setup and repos: rhevm-3.4.0-0.5.master.el6ev.noarch [root@dhcp163-99 ~]# cat /etc/yum.repos.d/rhev.repo [qa-latest] name=QA Latest build baseurl=http://bob.eng.lab.tlv.redhat.com/builds/av5/el6/ enabled=1 gpgcheck=0 [rhel-65] name=RHEL_65 baseurl=http://globalsync.qa.lab.tlv.redhat.com/pub/rhel/released/RHEL-6/6.5/Server/x86_64/os/ enabled=1 gpgcheck=0 [rhel-65-optional] name=RHEL_65_OPTIONAL baseurl=http://globalsync.qa.lab.tlv.redhat.com/pub/rhel/released/RHEL-6/6.5/Server/optional/x86_64/os/ enabled=1 gpgcheck=0 [rhel-65-zstream] name=RHEL_65_Z baseurl=http://download.eng.bos.redhat.com/rel-eng/repos/RHEL-6.5-Z/x86_64/ enabled=1 gpgcheck=0 [JBoss_latest] name=jboss_latest baseurl=http://download.devel.redhat.com/devel/candidates/JBEAP/JBEAP-6.2.2.CP.CR2/rpms/jbappplatform-6.2-x86_64-server-6-rpm/ enabled=1 gpgcheck=0 [JBoss_stable] name=jboss_stable baseurl=http://download.eng.rdu2.redhat.com/released/JBEAP-6/6.2.1/puddle/x86_64/os/ enabled=1 gpgcheck=0
I remember that for the first time it was enabled for me as well and I had to refresh the browser, did you try to refresh the browser?
Refresh doesn't helped, we've seen this together, following our inspection, please take it to double check.
av5 should be tested with rhevm-3.4.0-0.12 (instead of rhevm-3.4.0-0.5)
Please provide the link for latest repo as I'm using this one: [qa-latest] name=QA Latest build baseurl=http://bob.eng.lab.tlv.redhat.com/builds/av5/el6/ enabled=1 gpgcheck=0 root@dhcp163-99 ~]# yum info rhevm Loaded plugins: product-id, rhnplugin, security, subscription-manager, versionlock This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. This system is receiving updates from RHN Classic or RHN Satellite. Installed Packages Name : rhevm Arch : noarch Version : 3.4.0 Release : 0.5.master.el6ev Size : 1.5 M Repo : installed From repo : qa-latest Summary : Management server for Open Virtualization URL : http://www.redhat.com/products/virtualization License : ASL 2.0 Description : Red Hat Enterprise Virtualization is a feature-rich server virtualization management : system that provides advanced capabilities for managing Red Hat : virtualization infrastructure for Servers and Desktops.
My misconfiguration issues, didn't knew that I should run "rhevm-setup" after "yum update rhevm-setup". Now after getting to right version memory field is greyed out as expected.
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-2014-0506.html