Bug 1823674
Summary: | On creating a template during importing an image from OpenStack, an invalid machine type is generated | ||||||
---|---|---|---|---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Dominik Holler <dholler> | ||||
Component: | BLL.Virt | Assignee: | Shmuel Melamud <smelamud> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Nisim Simsolo <nsimsolo> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 4.4.0 | CC: | ahadas, bpelled, bugs, lsvaty, mavital, mburman, michal.skrivanek, rbarry, smelamud | ||||
Target Milestone: | ovirt-4.4.1 | Keywords: | Automation | ||||
Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
|
||||
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: | 2020-06-08 14:40:55 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 1824472 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Dominik Holler
2020-04-14 08:59:32 UTC
After checking with automation ovirt_template ansible module can't edit machine types, thus QE would be indeed blocked on this. Sorry for confusion. https://docs.ansible.com/ansible/latest/modules/ovirt_template_module.html the swapping of machine types is wrong. On el8 there's not a complete overlap in i440fx and q35 types so we must stop just swapping the substring. it needs to be set correctly in emulated_machine filed of cluster table, probably on bios type change in cluster. i.e. q35-rhel-8.1.0 for type 2,3 and i440fx-rhel-7.6.0 for type 1 Can this bug changed to MODIFIED? (In reply to Dominik Holler from comment #3) > Can this bug changed to MODIFIED? No. please review if there's really a test this bug is blocking. AFAICT it should not anymore. If it's indeed the case please remove AutomationBlocker. Meital, can you please confirm that you are not aware of any test case which is blocked by this bug? (In reply to Michal Skrivanek from comment #5) > please review if there's really a test this bug is blocking. > AFAICT it should not anymore. If it's indeed the case please remove > AutomationBlocker. As far as i know, this is not blocking automation anymore or any specific test. But maybe Meital knows about blocked test because of it. (In reply to Dominik Holler from comment #6) > Meital, can you please confirm that you are not aware of any test case which > is blocked by this bug? I'm not aware of any automation case that blocked by this bug *** This bug has been marked as a duplicate of bug 1830840 *** |