Bug 1208416 - [scale]- Insufficient amount of free MACs.
Summary: [scale]- Insufficient amount of free MACs.
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 3.5.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ovirt-3.6.2
: ---
Assignee: Martin Mucha
QA Contact: Eldad Marciano
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-02 08:27 UTC by punit
Modified: 2016-02-10 19:15 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 14:35:53 UTC
oVirt Team: Network
Embargoed:
ylavi: ovirt-3.6.z?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)
engine logs (18.52 KB, text/plain)
2015-04-02 08:27 UTC, punit
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1219383 0 low CLOSED [MAC pool] limit range to 2^31 addresses via REST 2021-02-22 00:41:40 UTC
oVirt gerrit 39481 0 master ABANDONED engine: Insufficient free macs while there is enough macs in pool Never
oVirt gerrit 39483 0 ovirt-engine-3.5 ABANDONED engine: Insufficient free macs while there is enough macs in pool Never
oVirt gerrit 39484 0 ovirt-engine-3.5.2 ABANDONED engine: Insufficient free macs while there is enough macs in pool 2016-01-10 01:58:44 UTC

Internal Links: 1219383

Description punit 2015-04-02 08:27:33 UTC
Created attachment 1010059 [details]
engine logs

Description of problem:Already Set a range of MAC addresses(About 8000) for use by using engine-config -s MacPoolRanges ...but when deploy the VM with predefined OS template with 2 Network card attached..upto 893 VM's can be deployed but after that VM failed with "Insufficient amount of free MACs"..

[root@ccr01 ~]# engine-config -g MacPoolRanges
MacPoolRanges: 00:1A:4A:FA:F1:00-00:1A:4A:FA:F1:FC,00:1A:4A:FB:F2:00-00:1A:4A:FB:F2:FC,00:1A:4A:FC:F3:00-00:1A:4A:FC:F3:FC,00:1A:4A:FD:F4:00-00:1A:4A:FD:F4:FC,00:1A:4A:FE:F5:00-00:1A:4A:FE:F5:FC,00:1A:4A:FF:F6:00-00:1A:4A:FF:F6:FC,00:1A:4A:EA:F7:00-00:1A:4A:EA:F7:FC,00:1A:4A:EB:F8:00-00:1A:4A:EB:F8:FC,00:1A:4A:97:5A:00-00:1A:4A:97:5A:FD,00:1A:4A:97:5B:00-00:1A:4A:97:5B:FE,00:1A:4A:97:5C:00-00:1A:4A:97:5C:FE,00:1A:4A:97:5D:00-00:1A:4A:97:5D:FE,00:1A:4A:97:6A:00-00:1A:4A:97:6A:FE,00:1A:4A:97:6B:00-00:1A:4A:97:6B:FE,00:1A:4A:97:6C:00-00:1A:4A:97:6C:FE,00:1A:4A:97:6D:00-00:1A:4A:97:6D:FD version: general
[root@ccr01 ~]#

Inside the Engine the free mac address :- 

---------------
-bash-4.2$ psql -h localhost -U engine -d engine
Password for user engine:
psql (9.2.7)
Type "help" for help.
     
engine=> select count(*) from vm_interface where mac_addr is not NULL;
count
-------
1834
(1 row)
engine=>
-----------------


Upto 893 VM can be deployed with the same OS templates but after 893 can not be deployed with 2 Network card... 


Version-Release number of selected component (if applicable): 3.5.1.1-1.el7 


How reproducible:100%


Steps to Reproduce:

1. Create one VM with two Network card attached..once all done...make an template with it..
2. Set MAC Pool Range to a known(like 4000 mac address) range using engine-config (and restart ovirt-engine service)
3. Attempt to create 893 VM from this mac address pool range..
4. 894th VM will fail with the error "Insufficient amount of free MACs" 

Actual results:-VM failed to create through OS template with error "Insufficient amount of free MACs"..actually there are lots of Macs are free..

Expected results:- Should allow 2 NICs to be created with auto-assigned MACs..

Additional Info :- The VM can be create either i will remove both the network card from the template or remove one network card from template...

Screen Shots :- 
http://postimg.org/image/ilieryr9n/
http://postimg.org/image/ibbgw1gz1/
http://postimg.org/image/5clxdtpdf/

Comment 1 Lior Vernia 2015-04-08 13:10:15 UTC
Let's fix it for 3.6 before we decide if it needs backporting.

Punit, while your patch seems to fix *a* bug, mmucha tells me it doesn't fix *the* bug you encountered (and described here) - as that would yield a different error message.

Comment 2 Lior Vernia 2015-04-20 08:59:58 UTC
Moving back to 3.5.z to ease tracking.

Comment 3 Yaniv Lavi 2015-09-07 09:22:14 UTC
Can you please try to recreate this scale issue in 3.6?

Comment 4 Gil Klein 2015-09-09 09:04:19 UTC
Meni, can you try reproduce this issue?

Comment 5 Yaniv Lavi 2015-09-09 15:46:10 UTC
It's a scale issue.

Comment 6 Red Hat Bugzilla Rules Engine 2015-10-19 10:51:22 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 7 Eldad Marciano 2015-10-29 09:57:23 UTC
can you specify on which version this defect was found ?

Comment 8 Yaniv Lavi 2015-10-29 12:45:15 UTC
(In reply to Eldad Marciano from comment #7)
> can you specify on which version this defect was found ?

done

Comment 9 Dan Kenigsberg 2015-10-29 14:48:23 UTC
(In reply to Eldad Marciano from comment #7)
> can you specify on which version this defect was found ?

commit 0 says it was 3.5.1.1-1.el7

Comment 10 Dan Kenigsberg 2015-10-29 14:50:44 UTC
setting needinfo on QE (and lowering priority), as devel fails to reproduce the issue.

Comment 11 Eldad Marciano 2015-11-17 15:46:33 UTC
we ran 900 vms with no MACs errors at all on top of 3.6.0.
we had issue with that mac ranges due to the new configuration flow, in 3.6 we must to set new mac ranges via the engine UI > configure (right upper cornr) > MAC Address pool.

Comment 12 Martin Mucha 2015-11-18 07:46:19 UTC
by saying: "we had issue with that mac ranges due to the new configuration flow" are you saying that you had to move from using engine-config, or that you did  encounter some issues with rest? (~ as mac pools should be manageable through rest as well)

Comment 13 Yaniv Lavi 2015-11-18 10:25:34 UTC
Can you please try to recreate with latest 3.6?

Comment 14 Eldad Marciano 2015-11-18 14:02:16 UTC
(In reply to Martin Mucha from comment #12)
> by saying: "we had issue with that mac ranges due to the new configuration
> flow" are you saying that you had to move from using engine-config, or that
> you did  encounter some issues with rest? (~ as mac pools should be
> manageable through rest as well)

we had to move from using engine-config and change the mac ranges via the UI.

Comment 15 punit 2015-12-01 01:15:45 UTC
Hi,

Didn't try with ovirt 3.6...i will try and update..

Comment 16 Dan Kenigsberg 2015-12-03 14:35:53 UTC
Thank you punit! Please reopen this bug if it reproduces.


Note You need to log in before you can comment on or make changes to this bug.