10:19 p.m.
This is a multi-part message in MIME format.
--------------050907020607010606010307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
During test day I've tested Martik Betak's feature "Enable configuration
of maximum allowed downtime during live migration per guest" (
https://bugzilla.redhat.com/1055434
<https://bugzilla.redhat.com/show_bug.cgi?id=1055434>).
For the tests I've created new VMs and tested the following:
_Webadmin_
- All newly added components to the Virtual Machine popup under the Host
tab appear correctly and well aligned with the rest of the components - OK
- The checkbox component of "Use custom migration downtime" works
correctly and grays out the input box when unchecked - OK
- The data entered in the input box is validated for input that does not
consist of numbers, empty value, a number not in the range or a negative
number - OK
- The valid number entered in the input is updated correctly in the
database - OK
- An existing migration downtime value is displayed correctly when
editing the VM - OK
- When unchecking the checkbox and saving the property in the database
is nullified - OK
_
__REST API_
- The valid number entered in the " migration_downtime" field is updated
correctly in the database - OK
- An existing migration downtime value is displayed correctly when
GETting the VM - OK
- A non existing migration downtime value of a VM is displayed as "-1" - OK
- Updating an existing migration downtime of a VM to "-1" nullifies the
value in the database - OK
_VDSM_
The correct migration downtime value set in the VM is transferred
correctly to "vmMigrate" command "downtime" parameter - OK
Summary: All the tests went ok without failures but during the test I've
found a bug regardless to the tests scope, when I tested a change of the
migration downtime in the cluster level it turns our that the value set
for the cluster custom properties via webadmin is not updated in the
database, a bug was opened for that issue -
https://bugzilla.redhat.com/1058703
<https://bugzilla.redhat.com/show_bug.cgi?id=1058703>
--------------050907020607010606010307
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 bgcolor="#FFFFFF" text="#000000">
Hi,<br>
During test day I've tested Martik Betak's feature "Enable
configuration of maximum allowed downtime during live migration per
guest" (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://bugzilla.redhat.com/show_bug.cgi?id=1055434">h...
For the tests I've created new VMs and tested the following:<br>
<br>
<u>Webadmin</u><br>
- All newly added components to the Virtual Machine popup under the
Host tab appear correctly and well aligned with the rest of the
components - OK<br>
- The checkbox component of "Use custom migration downtime" works
correctly and grays out the input box when unchecked - OK<br>
- The data entered in the input box is validated for input that does
not consist of numbers, empty value, a number not in the range or a
negative number - OK<br>
- The valid number entered in the input is updated correctly in the
database - OK<br>
- An existing migration downtime value is displayed correctly when
editing the VM - OK<br>
- When unchecking the checkbox and saving the property in the
database is nullified - OK<br>
<u><br>
</u><u>REST API</u><br>
- The valid number entered in the "
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
migration_downtime" field is updated correctly in the database - OK<br>
- An existing migration downtime value is displayed correctly when
GETting the VM - OK<br>
- A non existing migration downtime value of a VM is displayed as
"-1" - OK<br>
- Updating an existing migration downtime of a VM to "-1" nullifies
the value in the database - OK<br>
<br>
<u>VDSM</u><br>
The correct migration downtime value set in the VM is transferred
correctly to "vmMigrate" command "downtime" parameter -
OK<br>
<br>
<br>
Summary: All the tests went ok without failures but during the test
I've found a bug regardless to the tests scope, when I tested a
change of the migration downtime in the cluster level it turns our
that the value set for the cluster custom properties via webadmin is
not updated in the database, a bug was opened for that issue -
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://bugzilla.redhat.com/show_bug.cgi?id=1058703">h...
<br>
<br>
</body>
</html>
--------------050907020607010606010307--