Created attachment 938079[details]
qosheadingwrong
Description of problem:
CPU QOS has wrong heading when edited "Edit Storage QOS" instead of "Edit CPU QOS".
Version-Release number of selected component (if applicable):
rhevm-3.5.0-0.12.beta.el6ev.noarch
sanlock-3.1.0-2.el7.x86_64
qemu-kvm-rhev-1.5.3-60.el7_0.2.x86_64
vdsm-4.16.4-0.el7.x86_64
libvirt-daemon-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-secret-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-storage-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-qemu-1.1.1-29.el7_0.1.x86_64
libvirt-python-1.1.1-29.el7_0.1.x86_64
libvirt-lock-sanlock-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-kvm-1.1.1-29.el7_0.1.x86_64
libvirt-client-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-interface-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-nodedev-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-config-nwfilter-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-network-1.1.1-29.el7_0.1.x86_64
libvirt-daemon-driver-nwfilter-1.1.1-29.el7_0.1.x86_64
How reproducible:
100%
Steps to Reproduce:
1.Clusters->CPU profiles->new->Create any CPU profine with limitation to 50.
2.Data centers->QOS->CPU->new->create QOS with limit of 50.
3.Now try to edit created QOS and you'll see wrong heading just like it shown in attachment.
Actual results:
"Edit Storage QOS" instead of "Edit CPU QOS".
Expected results:
"Edit CPU QOS".
Additional info:
Screenshot attached.
Updated reproduction steps:
Steps to Reproduce:
1.Data centers->QOS->CPU->new->create QOS with limit of 50.
2.Clusters->CPU profiles->new->Create any CPU profine with limitation to 50.
3.Now try to edit created QOS and you'll see wrong heading just like it shown in attachment.
this bug status was moved to MODIFIED before engine vt5 was built,
hence moving to on_qa, if this was mistake and the fix isn't in,
please contact rhev-integ
Created attachment 938079 [details] qosheadingwrong Description of problem: CPU QOS has wrong heading when edited "Edit Storage QOS" instead of "Edit CPU QOS". Version-Release number of selected component (if applicable): rhevm-3.5.0-0.12.beta.el6ev.noarch sanlock-3.1.0-2.el7.x86_64 qemu-kvm-rhev-1.5.3-60.el7_0.2.x86_64 vdsm-4.16.4-0.el7.x86_64 libvirt-daemon-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-secret-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-storage-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-qemu-1.1.1-29.el7_0.1.x86_64 libvirt-python-1.1.1-29.el7_0.1.x86_64 libvirt-lock-sanlock-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-kvm-1.1.1-29.el7_0.1.x86_64 libvirt-client-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-interface-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-nodedev-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-config-nwfilter-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-network-1.1.1-29.el7_0.1.x86_64 libvirt-daemon-driver-nwfilter-1.1.1-29.el7_0.1.x86_64 How reproducible: 100% Steps to Reproduce: 1.Clusters->CPU profiles->new->Create any CPU profine with limitation to 50. 2.Data centers->QOS->CPU->new->create QOS with limit of 50. 3.Now try to edit created QOS and you'll see wrong heading just like it shown in attachment. Actual results: "Edit Storage QOS" instead of "Edit CPU QOS". Expected results: "Edit CPU QOS". Additional info: Screenshot attached.