Description of problem: In the upgrade procedure each host is checking if the shared configuration volume exists or not and to do that we scan all the volumes on the hosted-engine storage domain. The issue is that after a reboot, ovirt-ha-agent will call prepareImage for metadata, lockspace and configuration image if present but not for the engine image. So getVolumesList will report an issue on iSCSI storage domains: [root@master-vds10 ~]# vdsClient -s 0 getVolumesList 09bb1168-4c09-4523-a5dd-35e5329b0736 00000000-0000-0000-0000-000000000000 ERROR: b7b859df-498f-434f-af48-18702dce341c : {'status': {'message': "Image path does not exist or cannot be accessed/created: ('/rhev/data-center/mnt/blockSD/09bb1168-4c09-4523-a5dd-35e5329b0736/images/2399b2ac-ec64-401e-b162-96106a46bab4',)", 'code': 254}} 1de06201-53c3-4b3b-a2a5-478d95dc5494 : hosted-engine.metadata. 5fe71750-0111-4989-976b-8575ca63750a : hosted-engine.lockspace. 51e6b26c-9707-4ac7-b8e2-c38fc36e4e39 : HostedEngineConfigurationImage. The upgrade procedure is quite picky on that and it stops the scan and so it doesn't found the configuration volume but it fails later on when it tries to create another one. It doesn't happens if the user doesn't reboot before restarting ovirt-ha-agent and it doesn't happens on NFS cause getVolumesList doesn't fails here after the reboot. Version-Release number of selected component (if applicable): ovirt-hosted-engine-ha-1.3.3.6 How reproducible: 100% Steps to Reproduce: 1. deploy hosted-engine 3.5 on at lest two hosts using iSCSI 2. upgrade the first host to 3.6 3. stop and disable ovirt-ha-agent on the second host 4. upgrade all the rpms of the second host to 3.6 and avoid restarting ovirt-ha-agent 5. reboot the second host 6. enable and restart ovirt-ha-agent to trigger the upgrade Actual results: it says MainThread::DEBUG::2016-01-11 11:31:51,456::image::86::ovirt_hosted_engine_ha.lib.image.Image::(prepare_images) Configuration image doesn't exist also if the Configuration image is already on the storage domain Expected results: MainThread::INFO::2016-01-11 15:51:07,559::upgrade::960::ovirt_hosted_engine_ha.lib.upgrade.StorageServer::(upgrade) Successfully upgraded Additional info:
Workaround: manually call vdsClient -s prepareImage for the engine image and restart ovirt-ha-agent
Simone this bug is on modified but still have a patch on NEW, can you check?
It's just a docstring but the code is really the same
(In reply to Simone Tiraboschi from comment #3) > It's just a docstring but the code is really the same This is on 3.6.2 and has patches on new that are less important and patches that unblock flow which are critical. Please move to QE is released in latest 3.6.2 and create a new bug for the other fix targeted to a later 3.6.z.
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.
wait for release 1.3.3.6
What do you man by this comment?
I mean that version of last package that I have ovirt-hosted-engine-setup-1.3.3.3-1.el7ev.noarch, but target release is 1.3.3.6, so I need package ovirt-hosted-engine-setup-1.3.3.6*.el7ev.noarch to verify this bug
my mistake, I confused setup package with ha package
Checked on ovirt-hosted-engine-ha-1.3.4.1-1.el7ev.noarch
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Now it fails due to https://bugzilla.redhat.com/show_bug.cgi?id=1274622#c13
Verified on ovirt-hosted-engine-ha-1.3.4.3-1.el7ev.noarch 1) Deploy 3.5 HE on two hosts 2) Upgrade engine to 3.6 3) Upgrade first host to 3.6 4) stop and mask ovirt-ha-agent on second host 5) update packages on second host 6) unmask ovirt-ha-agent on second host 7) reboot second host 8) check that upgrade pass on second host PASS