Bug 1056803
| Summary: | Creating a new VM fails with MAC_POOL_NOT_INITIALIZED | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Brian Harrington <bharrington> | ||||
| Component: | ovirt-engine | Assignee: | Mike Kolesnik <mkolesni> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Martin Pavlik <mpavlik> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 3.3.0 | CC: | acathrow, alonbl, iheim, kburres, lpeer, lyarwood, masayag, mkolesni, mpavlik, myakove, nyechiel, Rhev-m-bugs, tpoitras, yeylon | ||||
| Target Milestone: | --- | Keywords: | Triaged, ZStream | ||||
| Target Release: | 3.4.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Linux | ||||||
| Whiteboard: | network | ||||||
| Fixed In Version: | ovirt-3.4.0-beta3 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Previously, there was an undersized value in a config file that was causing an out of memory error. As a result, upgrading to 3.4 from an older version of Red Hat Enterprise Virtualization and attempting to create a new virtual machine would fail.
Now, the out of memory problem has been fixed, and creating new virtual machines on a newly-upgraded system works properly.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1065011 (view as bug list) | Environment: | |||||
| Last Closed: | 2014-06-09 15:09:25 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: | 1065011, 1078909, 1142926 | ||||||
| Attachments: |
|
||||||
|
Description
Brian Harrington
2014-01-22 23:31:18 UTC
In troubleshooting further I found the following values in the config: MacPoolRanges: 00:1A:4A:01:00:00-00:1A:4A:FF:FF:FF version: general MaxMacsCountInPool: 100000 version: general The MaxMacsCountInPool is *vastly* undersized for this range (as noted in https://access.redhat.com/site/solutions/236473). Potentially a more useful error message could be sent out? While there is no way to verify past bug 987825 I have a feeling this could have been the culprit. After verifying that there were no existing MAC addresses outside of the new range, changing the values to: # engine-config -s MacPoolRanges=00:1A:4A:01:00:00-00:1A:4A:02:FF:FF # engine-config -s MaxMacsCountInPool=132072 Solves the problem and VMs are now able to be created. What I see is that there was indeed a behavioral change in 3.3. Prior to 3.3, if the range would exceed the MAX then the pool would be partially initialized. Now, the pool is not initialized by a partial range (you can have several ranges so only those not "fitting" in the pool would not be added). Not sure this merits a fix, but probably a release note should be included. Also, in the new behavior you would get a MAC_POOL_NOT_ENOUGH_MAC_ADDRESSES error and not a MAC_POOL_NOT_INITIALIZED for this scenario, but if you can attach the engine log from your environment perhaps there is another culprit which is unrelated to MaxMacsCountInPool but does cause this error to appear. Created attachment 854512 [details]
ovirt-engine log
Here is the engine log as requested.
The change of behavior causes an out of memory error in case of a very big range. It's been decided to restore the original behavior, which will fix the out of memory error and also keep same beavior from previous versions. verified with Red Hat Enterprise Virtualization Manager Version: 3.4.0-0.2.master.el6ev [root@mp-rhevm34 ~]# engine-config -g MacPoolRanges MacPoolRanges: 00:1A:4A:01:00:00-00:1A:4A:02:FF:FF version: general [root@mp-rhevm34 ~]# engine-config -g MaxMacsCountInPool MaxMacsCountInPool: 5 version: general 2014-02-18 13:22:43,125 WARN [org.ovirt.engine.core.bll.network.vm.AddVmInterfaceCommand] (ajp-/127.0.0.1:8702-1) [457de3c] CanDoAction of action AddVmInterface failed. Reasons:VAR__TYPE__INTERFACE,VAR__ACTION__ADD,MAC_POOL_NOT_ENOUGH_MAC_ADDRESSES 2014-02-18 13:22:43,197 WARN [org.ovirt.engine.core.bll.network.vm.AddVmInterfaceCommand] (ajp-/127.0.0.1:8702-3) [1015dbce] CanDoAction of action AddVmInterface failed. Reasons:VAR__TYPE__INTERFACE,VAR__ACTION__ADD,MAC_POOL_NOT_ENOUGH_MAC_ADDRESSES This bug is referenced in ovirt-engine-3.4.0-beta3 logs. Moving to ON_QA verified with oVirt Engine Version: 3.4.0-0.11.beta3.el6 2014-02-19 14:51:14,329 WARN [org.ovirt.engine.core.bll.network.vm.AddVmInterfaceCommand] (ajp--127.0.0.1-8702-6) [163123e3] CanDoAction of action AddVmInterface failed. Reasons:VAR__TYPE__INTERFACE,VAR__ACTION__ADD,MAC_POOL_NOT_ENOUGH_MAC_ADDRESSES Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2014-0506.html |