Bug 1262359
Summary: | broker from 1.2.6.1 fails with VDSM 4.17 cause getVolumePath is no more avaialble | ||
---|---|---|---|
Product: | [oVirt] ovirt-hosted-engine-ha | Reporter: | Simone Tiraboschi <stirabos> |
Component: | Broker | Assignee: | Simone Tiraboschi <stirabos> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikolai Sednev <nsednev> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.2.6.1 | CC: | bugs, eedri, gklein, mavital, nsoffer, sbonazzo, stirabos |
Target Milestone: | ovirt-3.5.5 | Keywords: | Triaged |
Target Release: | 1.2.7.2 | Flags: | sbonazzo:
ovirt-3.5.z?
sbonazzo: blocker? rule-engine: planning_ack? sbonazzo: devel_ack+ rule-engine: testing_ack? |
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | integration | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-26 13:44:09 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Simone Tiraboschi
2015-09-11 13:35:14 UTC
Hmm I am not sure what to do about this as we can't change already released packages.. we can add conflicts to 3.5.z or just document this. getVolumePath was removed about a year ago in this commit: commit 5578d97c46cfbdc8019296d737655e5c274e738a Author: Federico Simoncelli <fsimonce> Date: Tue Sep 23 13:04:39 2014 +0000 hsm: remove obsolete getVolumePath verb We can remove the getVolumePath verb as it was never officially in use. Change-Id: I7d15dee9e805478f4b4d2bfcb7985484db77339e Signed-off-by: Federico Simoncelli <fsimonce> Reviewed-on: http://gerrit.ovirt.org/33353 Reviewed-by: Nir Soffer <nsoffer> Reviewed-by: Dan Kenigsberg <danken> This method was obsolete and was kept only for testing purposes; prepareImage should be used instead. Just introduce a new conflict for 3.5.5 Bug tickets that are moved to testing must have target release set to make sure tester knows what to test. Please set the correct target release before moving to ON_QA. Hi Simone, Please provide a bit more detailed info for reproduction: 1.I need to add 3.6 repos to the engine and upgrade it first, then to add 3.6 repos to the host and try to upgrade the vdsm only? 2.Or I have to leave the engine 3.5 and only upgrade the host's vdsm to 3.6 repos? If I'm trying to upgrade the engine first, then I'm failing with the: Error: Package: rhevm-setup-plugin-ovirt-engine-3.6.0.1-0.1.el6.noarch (qa-latest) Requires: rhevm >= 3.6.0 Installed: rhevm-3.5.5-0.1.el6ev.noarch (@rhev-3.5-el6) rhevm = 3.5.5-0.1.el6ev Error: rhevm-setup-plugin-ovirt-engine conflicts with rhevm-3.5.5-0.1.el6ev.noarch My environment consisted from one host with RHEL7.1 and RHEVM3.5.5-0.1.el6. For the host only, upgrading of the vdsm* worked for me with the following components: libvirt-python-1.2.8-7.el7_1.1.x86_64 libvirt-daemon-driver-nodedev-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-driver-storage-1.2.8-16.el7_1.4.x86_64 sanlock-python-3.2.2-2.el7.x86_64 libvirt-client-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-config-nwfilter-1.2.8-16.el7_1.4.x86_64 libvirt-lock-sanlock-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-driver-network-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-kvm-1.2.8-16.el7_1.4.x86_64 ovirt-hosted-engine-ha-1.2.7.2-1.el7ev.noarch vdsm-4.17.9-1.el7ev.noarch sanlock-3.2.2-2.el7.x86_64 libvirt-daemon-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-driver-secret-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-driver-qemu-1.2.8-16.el7_1.4.x86_64 ovirt-hosted-engine-setup-1.2.6.1-1.el7ev.noarch mom-0.5.1-1.el7ev.noarch sanlock-lib-3.2.2-2.el7.x86_64 qemu-kvm-rhev-2.1.2-23.el7_1.10.x86_64 libvirt-daemon-driver-nwfilter-1.2.8-16.el7_1.4.x86_64 libvirt-daemon-driver-interface-1.2.8-16.el7_1.4.x86_64 Red Hat Enterprise Linux Server release 7.1 (Maipo) Engine: rhevm-3.5.5-0.1.el6ev.noarch ovirt-host-deploy-1.3.2-1.el6ev.noarch ovirt-host-deploy-java-1.3.2-1.el6ev.noarch Red Hat Enterprise Linux Server release 6.7 (Santiago) This is the outprint of ovirt-ha-broker after the upgrade of vdsm* on host: systemctl status ovirt-ha-broker -l ovirt-ha-broker.service - oVirt Hosted Engine High Availability Communications Broker Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service; enabled) Active: active (running) since Tue 2015-10-20 11:47:07 IDT; 1h 19min ago Main PID: 18130 (ovirt-ha-broker) CGroup: /system.slice/ovirt-ha-broker.service └─18130 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker Oct 20 13:05:59 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mem_free.MemFree ERROR Failed to getVdsStats: VDSM initialization timeout Oct 20 13:06:06 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mgmt_bridge.MgmtBridge ERROR Failed to getVdsCapabilities: VDSM initialization timeout Oct 20 13:06:08 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker engine_health.CpuLoadNoEngine ERROR Failed to getVmStats: VDSM initialization timeout Oct 20 13:06:09 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mem_free.MemFree ERROR Failed to getVdsStats: VDSM initialization timeout Oct 20 13:06:17 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mgmt_bridge.MgmtBridge ERROR Failed to getVdsCapabilities: VDSM initialization timeout Oct 20 13:06:18 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker engine_health.CpuLoadNoEngine ERROR Failed to getVmStats: VDSM initialization timeout Oct 20 13:06:19 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mem_free.MemFree ERROR Failed to getVdsStats: VDSM initialization timeout Oct 20 13:06:27 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mgmt_bridge.MgmtBridge ERROR Failed to getVdsCapabilities: VDSM initialization timeout Oct 20 13:06:28 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker engine_health.CpuLoadNoEngine ERROR Failed to getVmStats: VDSM initialization timeout Oct 20 13:06:29 alma03.qa.lab.tlv.redhat.com ovirt-ha-broker[18130]: ovirt-ha-broker mem_free.MemFree ERROR Failed to getVdsStats: VDSM initialization timeout # systemctl restart ovirt-ha-broker && systemctl restart ovirt-ha-agent # systemctl status ovirt-ha-broker -l ovirt-ha-broker.service - oVirt Hosted Engine High Availability Communications Broker Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service; enabled) Active: active (running) since Tue 2015-10-20 13:07:22 IDT; 9s ago Process: 60543 ExecStop=/usr/lib/systemd/systemd-ovirt-ha-broker stop (code=exited, status=0/SUCCESS) Process: 60559 ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start (code=exited, status=0/SUCCESS) Main PID: 60572 (ovirt-ha-broker) CGroup: /system.slice/ovirt-ha-broker.service └─60572 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker Oct 20 13:07:22 alma03.qa.lab.tlv.redhat.com systemd-ovirt-ha-broker[60559]: Starting ovirt-ha-broker: [ OK ] Oct 20 13:07:22 alma03.qa.lab.tlv.redhat.com systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. [root@alma03 ~]# systemctl status ovirt-ha-broker -l ovirt-ha-broker.service - oVirt Hosted Engine High Availability Communications Broker Loaded: loaded (/usr/lib/systemd/system/ovirt-ha-broker.service; enabled) Active: active (running) since Tue 2015-10-20 13:07:22 IDT; 24s ago Process: 60543 ExecStop=/usr/lib/systemd/systemd-ovirt-ha-broker stop (code=exited, status=0/SUCCESS) Process: 60559 ExecStart=/usr/lib/systemd/systemd-ovirt-ha-broker start (code=exited, status=0/SUCCESS) Main PID: 60572 (ovirt-ha-broker) CGroup: /system.slice/ovirt-ha-broker.service └─60572 /usr/bin/python /usr/share/ovirt-hosted-engine-ha/ovirt-ha-broker Oct 20 13:07:22 alma03.qa.lab.tlv.redhat.com systemd-ovirt-ha-broker[60559]: Starting ovirt-ha-broker: [ OK ] Oct 20 13:07:22 alma03.qa.lab.tlv.redhat.com systemd[1]: Started oVirt Hosted Engine High Availability Communications Broker. During the upgrade of vdsm*, I've noticed that ovirt-hosted-engine-ha-1.2.7.2-1.el7ev.noarch remained the same, as it was already the latest before the upgrade and remained the same after it, so only vdsm* were upgraded and continued to work properly after restarting restart ovirt-ha-broker && restart ovirt-ha-agent on host. (In reply to Nikolai Sednev from comment #5) > Hi Simone, > Please provide a bit more detailed info for reproduction: > 1.I need to add 3.6 repos to the engine and upgrade it first, then to add > 3.6 repos to the host and try to upgrade the vdsm only? > 2.Or I have to leave the engine 3.5 and only upgrade the host's vdsm to 3.6 > repos? It should be the same regarding this topic. oVirt 3.5.5 has been released including fixes for this issue. |