fuel-devops create wrong CPU configuration for virtual machines
Bug #1464551 reported by
Bartłomiej Piotrowski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Fix Released
|
High
|
Sebastian Kalinowski | ||
Bug Description
On our test lab, creating Ubuntu environment with fuel-qa + fuel-devops causes provisioned nodes to kernel panic after reboot from bootstrap. This is caused by incorrect CPU configuration set by fuel-devops (and wrong feature autodetection made by libvirt).
To workaround it, we need to remove <cpu> section from virtual machine's XML config. This could be easily done on fuel-devops side by not specifying CPU model as introduced here[1]. This way libvirt will use sane defaults. I really doubt it can negatively affect tests performance; extensions like avx2 are almost never used inside precompiled packages to avoid compatibility issues.
[1] https:/
| Changed in fuel: | |
| assignee: | Fuel QA Team (fuel-qa) → Sebastian Kalinowski (prmtl) |
| Changed in fuel: | |
| status: | Confirmed → In Progress |
| tags: | added: non-release |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to fuel-devops (master) | #1 |
| Changed in fuel: | |
| status: | In Progress → Fix Committed |
| Changed in fuel: | |
| status: | Fix Committed → Fix Released |
| tags: |
added: area-qa removed: non-release |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/