Back to bug 1403735

Who When What Removed Added
Sandro Bonazzola 2016-12-12 10:10:03 UTC Depends On 1396672
Link ID oVirt gerrit 68053
Link ID oVirt gerrit 68052
Link ID oVirt gerrit 67893
Status NEW MODIFIED
Target Milestone ovirt-4.0.7 ovirt-3.6.10
Simone Tiraboschi 2016-12-14 11:09:47 UTC Blocks 1403750
Target Milestone ovirt-3.6.10 ovirt-4.0.7
Doc Text Since 3.6 ovirt-ha-agent will read its configuration and the engine VM specification from the shared storage while till 3.5 they were just local files replicated on each involved host.
Modify the output of hosted-engine --vm-status to show if the configuration and the VM specification has been, on each reported host, correctly read from the shared storage.
Doc Type If docs needed, set a value Enhancement
errata-xmlrpc 2017-01-25 08:32:51 UTC Status MODIFIED ON_QA
Artyom 2017-02-28 12:48:06 UTC Keywords Triaged
Status ON_QA VERIFIED
CC alukiano
QA Contact nsednev alukiano
Megan Lewis 2017-03-06 07:07:01 UTC CC melewis
Doc Text Since 3.6 ovirt-ha-agent will read its configuration and the engine VM specification from the shared storage while till 3.5 they were just local files replicated on each involved host.
Modify the output of hosted-engine --vm-status to show if the configuration and the VM specification has been, on each reported host, correctly read from the shared storage.
With this update, the output of hosted-engine --vm-status has been modified to show if the configuration and the virtual machine specification has been correctly read from the shared storage on each reported host. Since Red Hat Enterprise Virtualization 3.6 ovirt-ha-agent has read the configuration and the virtual machine specification from the shared storage, whereas, until Red Hat Enterprise Virtualization 3.5 the configuration and virtual machine specification were local files replicated on each involved host.
errata-xmlrpc 2017-03-14 14:47:52 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-03-16 15:28:53 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-03-16 11:28:53 UTC

Back to bug 1403735