Bug 1157655
| Summary: | [PPC] NIC is unplugged by default when adding new NIC to running VM, and there is no way to change it | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Michael Burman <mburman> |
| Component: | ovirt-engine | Assignee: | Nobody <nobody> |
| Status: | CLOSED DUPLICATE | QA Contact: | Michael Burman <mburman> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.4.1-1 | CC: | ecohen, gklein, iheim, lpeer, lsurette, mburman, michal.skrivanek, rbalakri, Rhev-m-bugs, yeylon |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | ppc64 | ||
| OS: | Linux | ||
| Whiteboard: | network | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-28 08:07:51 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1122979 | ||
|
Description
Michael Burman
2014-10-27 12:28:21 UTC
> If i change to 'true' from 'false' in- > vi /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties > os.other_ppc64.devices.network.hotplugSupport.value.3.4 = true > New NIC will be created plugged by default as it should. > Looks like it's part of the Hotplug/unplug support I don't understand. So does it work or not? Why/when did you change osinfo? Engine version? How is this different from bug 1154630? Hi Michal, As you can see at the last comments of bug 1154630, i thought also that this bug is a part of the hotplug/unplug support, but i was asked to open new bug on that. Engine version is written above, It work only after changing the relevant line in osinfo to 'true', But this should be 'true' by default. When adding new NIC to VM it should be plugged by default. Do you understand now? The only reason i changed this line in osinfo, was because i suspected that this bug is part of 1154630, and i wanted to check that. Ok. Thanks, that explains it. It is the same issue indeed so no need for two bugs *** This bug has been marked as a duplicate of bug 1154630 *** |