Bug 1658179
| Summary: | Upgrade host: VM migration failed on no hosts to migrate to, while manual migration succeeded. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Ilanit Stein <istein> | ||||||||
| Component: | General | Assignee: | Nobody <nobody> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | meital avital <mavital> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 4.2.8 | CC: | bugs, istein, michal.skrivanek, mperina, ratamir, Rhev-m-bugs | ||||||||
| Target Milestone: | --- | Flags: | rule-engine:
devel_ack?
|
||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2019-01-03 14:05:28 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Ilanit Stein
2018-12-11 13:06:12 UTC
Created attachment 1513369 [details]
engine.log
Created attachment 1513371 [details]
vdsm.log
Created attachment 1513372 [details]
upgrade.log
Migration of manually migratable vms has been added only in 4.3. Any reason you’re testing it with 4.2.z? In 4.2 this is expected behavior The bug refer actually to 2 issues: 1. A running VM that should have been migrated (automatically), further to Upgrade host, but failed to migrate. 2. Upgrade host process continues, due the VM automatic migration failed. Regarding the first one: The VM was defined to a specific host, and with 'Migration mode': "Allow manual and automatic migration." My understand is (and please correct me if I am wrong) that in such case automatic VM migration should have succeeded. However, it failed, with the error mentioned in the bug description. Under this understanding, I simply pressed in the RHV UI on VM->Migrate, and this migration worked successfully. Such VM migration operation is supported of course for all RHV versions. sorry, commented on a wrong bug. Yes, the VM should migrate when set to Automatic migration. It's ok if it fails though, it just should be retriggered few times. Only after that if there is really no other host which can accommodate the VM should eventually fail/time out. It could be this waiting is not implemented for the upgrade host task. Normally the PreparingToMaintenance state is indefinite. Moving to infra for considering that. What do you mean by "upgrade host process continues"? I see: 2018-12-11 13:04:49,796+02 ERROR [org.ovirt.engine.core.bll.hostdeploy.HostUpgradeCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-59) [82ce56d4-bf1e-48ea-9739-39c200941ea2] Host 'host_mixed_2' failed to move to maintenance mode. Upgrade process is terminated. Michal, thanks for your reply. Regarding the migration failure: In this RHV there are only 2 hosts, so no trials to further destination hosts is expected. It puzzles that the VM failed to migrate automatically, while manually it worked fine. That is, I would expect the manual migration to fail the same. I just reproduced this issue on my RHV, in case you are interested in investigating why the automatic migration fail? Regarding the Upgrade cluster process - I can't reproduce it - I suggest to consider this issue as closed. Feel free to reopen if reproduced again The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |