2:47 p.m.
This is a multi-part message in MIME format.
--------------040205070708090903030405
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi All,
I have the following problem:
When I try to edit the configuration of a VM, VM being shut down, I go
to High Availability section, select the check box for Highly Available,
and try to increase afterwards the queue priority from Low to Medium or
High.
Despite the fact that I check the box for the Medium or High, after I
hit OK, and return to general information about VM, I see that Priority
remains unchanged to Low.
This is not what happens with the Highly Available check box, as
changing this value updates the general info tab when the VM is being
clicked.
Might this be a bug ?
I am using CentOS 6.3 with dreyou's repo, and the rpm packs I have
installed on the node controller are:
/ovirt-engine-setup-3.1.0-3.19.el6.noarch//
//ovirt-engine-config-3.1.0-3.19.el6.noarch//
//ovirt-engine-jbossas711-1-0.x86_64//
//ovirt-log-collector-3.1.0-16.el6.noarch//
//ovirt-iso-uploader-3.1.0-16.el6.noarch//
//ovirt-engine-backend-3.1.0-3.19.el6.noarch//
//ovirt-engine-webadmin-portal-3.1.0-3.19.el6.noarch//
//ovirt-engine-dbscripts-3.1.0-3.19.el6.noarch//
//ovirt-engine-genericapi-3.1.0-3.19.el6.noarch//
//ovirt-engine-tools-common-3.1.0-3.19.el6.noarch//
//ovirt-engine-3.1.0-3.19.el6.noarch//
//ovirt-engine-sdk-3.1.0.5-1.el6.noarch//
//ovirt-image-uploader-3.1.0-16.el6.noarch//
//ovirt-engine-userportal-3.1.0-3.19.el6.noarch//
//ovirt-engine-restapi-3.1.0-3.19.el6.noarch//
//ovirt-engine-notification-service-3.1.0-3.19.el6.noarch//
//ovirt-engine-cli-3.1.0.7-1.el6.noarch//
/
Also, this is the latest log from engine.log when I run the actions
described in the upper part.
/
2013-01-10 13:36:51,816 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: isQuotaDefault
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,820 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: isQuotaDefault
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,822 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: managedDeviceMap
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,825 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: managedDeviceMap
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,850 INFO [org.ovirt.engine.core.bll.UpdateVmCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] Running command: UpdateVmCommand
internal: false. Entities affected : ID:
96e6705a-030c-411a-b365-ad6ff3fcfb56 Type: VM
2013-01-10 13:36:51,868 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] START, IsValidVDSCommand(storagePoolId
= b6c128ae-5987-11e2-964c-001e8c47d368, ignoreFailoverLimit = false,
compatabilityVersion = null), log id: 35d20229
2013-01-10 13:36:51,873 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] FINISH, IsValidVDSCommand, return:
true, log id: 35d20229
2013-01-10 13:36:51,931 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] START,
UpdateVMVDSCommand(storagePoolId = b6c128ae-5987-11e2-964c-001e8c47d368,
ignoreFailoverLimit = false, compatabilityVersion = null,
storageDomainId = 00000000-0000-0000-0000-000000000000,
infoDictionary.size = 1), log id: 1e0c9f16
2013-01-10 13:36:51,953 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] FINISH, UpdateVMVDSCommand, log id:
1e0c9f16/
If anyone can give a clue about this, would be much appreciated.
Thanks
Alex.
--------------040205070708090903030405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
<br>
Hi All,<br>
<br>
I have the following problem:<br>
<br>
<br>
When I try to edit the configuration of a VM, VM being shut down, I
go to High Availability section, select the check box for
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Highly Available, and try to increase afterwards the queue priority
from Low to Medium or High.<br>
<br>
Despite the fact that I check the box for the Medium or High, after
I hit OK, and return to general information about VM, I see that
Priority remains unchanged to Low.<br>
<br>
This is not what happens with the Highly Available check box, as
changing this value updates the general info tab when the VM is
being clicked. <br>
<br>
Might this be a bug ?<br>
<br>
<br>
I am using CentOS 6.3 with dreyou's repo, and the rpm packs I have
installed on the node controller are:<br>
<br>
<small><i>ovirt-engine-setup-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-config-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-jbossas711-1-0.x86_64</i><i><br>
</i><i>ovirt-log-collector-3.1.0-16.el6.noarch</i><i><br>
</i><i>ovirt-iso-uploader-3.1.0-16.el6.noarch</i><i><br>
</i><i>ovirt-engine-backend-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-webadmin-portal-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-dbscripts-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-genericapi-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-tools-common-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-sdk-3.1.0.5-1.el6.noarch</i><i><br>
</i><i>ovirt-image-uploader-3.1.0-16.el6.noarch</i><i><br>
</i><i>ovirt-engine-userportal-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-restapi-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-notification-service-3.1.0-3.19.el6.noarch</i><i><br>
</i><i>ovirt-engine-cli-3.1.0.7-1.el6.noarch</i><i><br>
</i></small><br>
<br>
Also, this is the latest log from engine.log when I run the actions
described in the upper part.<br>
<br>
<i><small><br>
2013-01-10 13:36:51,816 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property:
isQuotaDefault for class
org.ovirt.engine.core.common.businessentities.VmStatic<br>
2013-01-10 13:36:51,820 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property:
isQuotaDefault for class
org.ovirt.engine.core.common.businessentities.VmStatic<br>
2013-01-10 13:36:51,822 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property:
managedDeviceMap for class
org.ovirt.engine.core.common.businessentities.VmStatic<br>
2013-01-10 13:36:51,825 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property:
managedDeviceMap for class
org.ovirt.engine.core.common.businessentities.VmStatic<br>
2013-01-10 13:36:51,850 INFO
[org.ovirt.engine.core.bll.UpdateVmCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] Running command:
UpdateVmCommand internal: false. Entities affected : ID:
96e6705a-030c-411a-b365-ad6ff3fcfb56 Type: VM<br>
2013-01-10 13:36:51,868 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] START,
IsValidVDSCommand(storagePoolId =
b6c128ae-5987-11e2-964c-001e8c47d368, ignoreFailoverLimit =
false, compatabilityVersion = null), log id: 35d20229<br>
2013-01-10 13:36:51,873 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] FINISH, IsValidVDSCommand,
return: true, log id: 35d20229<br>
2013-01-10 13:36:51,931 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] START,
UpdateVMVDSCommand(storagePoolId =
b6c128ae-5987-11e2-964c-001e8c47d368, ignoreFailoverLimit =
false, compatabilityVersion = null, storageDomainId =
00000000-0000-0000-0000-000000000000, infoDictionary.size = 1),
log id: 1e0c9f16<br>
2013-01-10 13:36:51,953 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] FINISH, UpdateVMVDSCommand,
log id: 1e0c9f16</small></i><br>
<br>
<br>
If anyone can give a clue about this, would be much appreciated.<br>
<br>
<br>
Thanks<br>
Alex.<br>
<br>
</body>
</html>
--------------040205070708090903030405--
3:13 p.m.
On 01/10/2013 01:47 PM, Alexandru Vladulescu wrote:
Hi All,
I have the following problem:
When I try to edit the configuration of a VM, VM being shut down, I go
to High Availability section, select the check box for Highly Available,
and try to increase afterwards the queue priority from Low to Medium or
High.
Despite the fact that I check the box for the Medium or High, after I
hit OK, and return to general information about VM, I see that Priority
remains unchanged to Low.
This is not what happens with the Highly Available check box, as
changing this value updates the general info tab when the VM is being
clicked.
Might this be a bug ?
I am using CentOS 6.3 with dreyou's repo, and the rpm packs I have
installed on the node controller are:
/ovirt-engine-setup-3.1.0-3.19.el6.noarch//
//ovirt-engine-config-3.1.0-3.19.el6.noarch//
//ovirt-engine-jbossas711-1-0.x86_64//
//ovirt-log-collector-3.1.0-16.el6.noarch//
//ovirt-iso-uploader-3.1.0-16.el6.noarch//
//ovirt-engine-backend-3.1.0-3.19.el6.noarch//
//ovirt-engine-webadmin-portal-3.1.0-3.19.el6.noarch//
//ovirt-engine-dbscripts-3.1.0-3.19.el6.noarch//
//ovirt-engine-genericapi-3.1.0-3.19.el6.noarch//
//ovirt-engine-tools-common-3.1.0-3.19.el6.noarch//
//ovirt-engine-3.1.0-3.19.el6.noarch//
//ovirt-engine-sdk-3.1.0.5-1.el6.noarch//
//ovirt-image-uploader-3.1.0-16.el6.noarch//
//ovirt-engine-userportal-3.1.0-3.19.el6.noarch//
//ovirt-engine-restapi-3.1.0-3.19.el6.noarch//
//ovirt-engine-notification-service-3.1.0-3.19.el6.noarch//
//ovirt-engine-cli-3.1.0.7-1.el6.noarch//
/
Also, this is the latest log from engine.log when I run the actions
described in the upper part.
/
2013-01-10 13:36:51,816 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: isQuotaDefault
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,820 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: isQuotaDefault
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,822 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: managedDeviceMap
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,825 WARN
[org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
(http--0.0.0.0-8443-2) Unable to get value of property: managedDeviceMap
for class org.ovirt.engine.core.common.businessentities.VmStatic
2013-01-10 13:36:51,850 INFO [org.ovirt.engine.core.bll.UpdateVmCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] Running command: UpdateVmCommand
internal: false. Entities affected : ID:
96e6705a-030c-411a-b365-ad6ff3fcfb56 Type: VM
2013-01-10 13:36:51,868 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] START, IsValidVDSCommand(storagePoolId
= b6c128ae-5987-11e2-964c-001e8c47d368, ignoreFailoverLimit = false,
compatabilityVersion = null), log id: 35d20229
2013-01-10 13:36:51,873 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] FINISH, IsValidVDSCommand, return:
true, log id: 35d20229
2013-01-10 13:36:51,931 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] START,
UpdateVMVDSCommand(storagePoolId = b6c128ae-5987-11e2-964c-001e8c47d368,
ignoreFailoverLimit = false, compatabilityVersion = null,
storageDomainId = 00000000-0000-0000-0000-000000000000,
infoDictionary.size = 1), log id: 1e0c9f16
2013-01-10 13:36:51,953 INFO
[org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
(http--0.0.0.0-8443-2) [52c2cdc2] FINISH, UpdateVMVDSCommand, log id:
1e0c9f16/
If anyone can give a clue about this, would be much appreciated.
Thanks
Alex.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
if you move to the hosts tab and back, does the value remain not updated?
(trying to understand if a ui refresh issue only)
3:50 p.m.
On 01/10/2013 02:13 PM, Itamar Heim wrote:
On 01/10/2013 01:47 PM, Alexandru Vladulescu wrote:
>
>
> Hi All,
>
> I have the following problem:
>
>
> When I try to edit the configuration of a VM, VM being shut down, I go
> to High Availability section, select the check box for Highly Available,
> and try to increase afterwards the queue priority from Low to Medium or
> High.
>
> Despite the fact that I check the box for the Medium or High, after I
> hit OK, and return to general information about VM, I see that Priority
> remains unchanged to Low.
>
> This is not what happens with the Highly Available check box, as
> changing this value updates the general info tab when the VM is being
> clicked.
>
> Might this be a bug ?
>
>
> I am using CentOS 6.3 with dreyou's repo, and the rpm packs I have
> installed on the node controller are:
>
> /ovirt-engine-setup-3.1.0-3.19.el6.noarch//
> //ovirt-engine-config-3.1.0-3.19.el6.noarch//
> //ovirt-engine-jbossas711-1-0.x86_64//
> //ovirt-log-collector-3.1.0-16.el6.noarch//
> //ovirt-iso-uploader-3.1.0-16.el6.noarch//
> //ovirt-engine-backend-3.1.0-3.19.el6.noarch//
> //ovirt-engine-webadmin-portal-3.1.0-3.19.el6.noarch//
> //ovirt-engine-dbscripts-3.1.0-3.19.el6.noarch//
> //ovirt-engine-genericapi-3.1.0-3.19.el6.noarch//
> //ovirt-engine-tools-common-3.1.0-3.19.el6.noarch//
> //ovirt-engine-3.1.0-3.19.el6.noarch//
> //ovirt-engine-sdk-3.1.0.5-1.el6.noarch//
> //ovirt-image-uploader-3.1.0-16.el6.noarch//
> //ovirt-engine-userportal-3.1.0-3.19.el6.noarch//
> //ovirt-engine-restapi-3.1.0-3.19.el6.noarch//
> //ovirt-engine-notification-service-3.1.0-3.19.el6.noarch//
> //ovirt-engine-cli-3.1.0.7-1.el6.noarch//
> /
>
> Also, this is the latest log from engine.log when I run the actions
> described in the upper part.
>
> /
> 2013-01-10 13:36:51,816 WARN
> [org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
> (http--0.0.0.0-8443-2) Unable to get value of property: isQuotaDefault
> for class org.ovirt.engine.core.common.businessentities.VmStatic
> 2013-01-10 13:36:51,820 WARN
> [org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
> (http--0.0.0.0-8443-2) Unable to get value of property: isQuotaDefault
> for class org.ovirt.engine.core.common.businessentities.VmStatic
> 2013-01-10 13:36:51,822 WARN
> [org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
> (http--0.0.0.0-8443-2) Unable to get value of property: managedDeviceMap
> for class org.ovirt.engine.core.common.businessentities.VmStatic
> 2013-01-10 13:36:51,825 WARN
> [org.ovirt.engine.core.compat.backendcompat.PropertyInfo]
> (http--0.0.0.0-8443-2) Unable to get value of property: managedDeviceMap
> for class org.ovirt.engine.core.common.businessentities.VmStatic
> 2013-01-10 13:36:51,850 INFO [org.ovirt.engine.core.bll.UpdateVmCommand]
> (http--0.0.0.0-8443-2) [52c2cdc2] Running command: UpdateVmCommand
> internal: false. Entities affected : ID:
> 96e6705a-030c-411a-b365-ad6ff3fcfb56 Type: VM
> 2013-01-10 13:36:51,868 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
> (http--0.0.0.0-8443-2) [52c2cdc2] START, IsValidVDSCommand(storagePoolId
> = b6c128ae-5987-11e2-964c-001e8c47d368, ignoreFailoverLimit = false,
> compatabilityVersion = null), log id: 35d20229
> 2013-01-10 13:36:51,873 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.IsValidVDSCommand]
> (http--0.0.0.0-8443-2) [52c2cdc2] FINISH, IsValidVDSCommand, return:
> true, log id: 35d20229
> 2013-01-10 13:36:51,931 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
> (http--0.0.0.0-8443-2) [52c2cdc2] START,
> UpdateVMVDSCommand(storagePoolId = b6c128ae-5987-11e2-964c-001e8c47d368,
> ignoreFailoverLimit = false, compatabilityVersion = null,
> storageDomainId = 00000000-0000-0000-0000-000000000000,
> infoDictionary.size = 1), log id: 1e0c9f16
> 2013-01-10 13:36:51,953 INFO
> [org.ovirt.engine.core.vdsbroker.irsbroker.UpdateVMVDSCommand]
> (http--0.0.0.0-8443-2) [52c2cdc2] FINISH, UpdateVMVDSCommand, log id:
> 1e0c9f16/
>
>
> If anyone can give a clue about this, would be much appreciated.
>
>
> Thanks
> Alex.
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
if you move to the hosts tab and back, does the value remain not updated?
(trying to understand if a ui refresh issue only)
Checked that before posting the original email, but it's not related to
refresh, or the switch doesn't change a thing.
Alex.
4334
days inactive
4334
days old
2 comments
2 participants
participants (2)
-
Alexandru Vladulescu -
Itamar Heim