Bug 1953159
| Summary: | VM with next run configuration can't get IP after it's restarted becasue the VM's vNIC profile is set to <Empty> | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Qin Yuan <qiyuan> | ||||
| Component: | BLL.Network | Assignee: | eraviv | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Burman <mburman> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 4.4.6.5 | CC: | ahadas, bugs, dfodor, eraviv, lsvaty, mburman, michal.skrivanek, mperina, pmatyas | ||||
| Target Milestone: | ovirt-4.4.6 | Keywords: | Automation, Regression | ||||
| Target Release: | --- | Flags: | pm-rhel:
ovirt-4.4+
mperina: blocker? |
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | ovirt-engine-4.4.6.6 | Doc Type: | No Doc Update | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-05-05 05:36:18 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Qin Yuan
2021-04-24 08:41:59 UTC
please attach logs fro m engine, host, and guest Created attachment 1775159 [details]
logs_of_engine_host_guest
I noticed when the VM with next run configuration is stopped, its nic's profile changes to empty. Tried to select a vNic profile for the VM nic again, it can get IP then. As it's a regression + automation, I suspect it might be related to your recent changes for out of sync NICs - would it make sense? *** Bug 1954299 has been marked as a duplicate of this bug. *** Verified on - rhvm-4.4.6.6-0.10.el8ev.noarch This bugzilla is included in oVirt 4.4.6 release, published on May 4th 2021. Since the problem described in this bug report should be resolved in oVirt 4.4.6 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. |