Bug 1784867
| Summary: | [UI] Migration for VMs is disabled in the UI | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Polina <pagranat> | ||||||
| Component: | BLL.Virt | Assignee: | Michal Skrivanek <michal.skrivanek> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Polina <pagranat> | ||||||
| Severity: | urgent | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.4.0 | CC: | bpelled, bugs, mavital, mburman, michal.skrivanek, rbarry, tbaransk, vszocs | ||||||
| Target Milestone: | ovirt-4.4.0 | Flags: | pm-rhel:
ovirt-4.4+
mavital: blocker? |
||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | ovirt-engine-ui-extensions-1.0.11 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2020-05-20 20:03:25 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Polina
2019-12-18 14:31:15 UTC
Please provide at least an approximate timestamp or VM name with logs this large. There are lots of migration events in the log, but the ones at the end fail because the VM is destroyed before startup. Is your environment sane? libvirt logs? to sum up UI is presumably fixed in ovirt-engine-ui-extensions-1.0.11. API usage presumably works, errors mentioned in previous comments are caused by other issues (connectivity/networking/OVF update bug) unless there is anything else... NOTABUG then? (In reply to Ryan Barry from comment #20) > NOTABUG then? Hi I'm sorry, how this is not a bug? the UI migration is disabled on 4.4.0-14, always. In all cases. Right, but that's ovirt-engine-ui-extensions (the button), which is already tracked elsewhere (In reply to Ryan Barry from comment #22) > Right, but that's ovirt-engine-ui-extensions (the button), which is already > tracked elsewhere Great, so pls mark this bug as a dependency of the ovirt-engine-ui-extensions bug. This can give a QE hint when it's ready to be tested and when the ui extensions bug is fixed. it has been fixed since ovirt-engine-ui-extensions-1.0.11 (In reply to Michal Skrivanek from comment #24) > it has been fixed since ovirt-engine-ui-extensions-1.0.11 It can't be ON_QA, becasue ovirt-engine-ui-extensions-1.0.11 wasn't delivered with latest 4.4.0-14 build. It is still using ovirt-engine-ui-extensions-1.0.10-1.el7ev.noarch So the fix is not available for QE at the latest build, which means it is not ON_QA.. Created attachment 1656054 [details]
migration failure
Please also wait for https://bugzilla.redhat.com/show_bug.cgi?id=1776314 this week This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020. Since the problem described in this bug report should be resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report. |