Bug 1266172
| Summary: | Validation error when adding nic to vm: NETWORK_MAC_ADDRESS_IN_USE | ||
|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Marcin Mirecki <mmirecki> |
| Component: | BLL.Network | Assignee: | Alona Kaplan <alkaplan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Meni Yakove <myakove> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 3.6.0 | CC: | bazulay, bugs, danken, gcheresh |
| Target Milestone: | ovirt-3.6.0-rc | Flags: | rule-engine:
ovirt-3.6.0+
rule-engine: blocker+ ylavi: Triaged+ ylavi: planning_ack+ bazulay: devel_ack+ rule-engine: testing_ack+ |
| Target Release: | 3.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | network | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-04 11:26:44 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: | 1247966 | ||
Verified on 3.6.0-0.18.el6 THe problem started happen again. Engine try to assign MAC address that is already used in DB to VM NIC. Adding custom MAC from range succeeds. Though it looks like a different bug we get the same error message Verified on 3.6.0-0.18.el6 Comment2 is a different issue, so will open another bug oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one. |
Description of problem: When adding a network interface to a vm, a validation error is displayed: NETWORK_MAC_ADDRESS_IN_USE. Steps to Reproduce: 1. Go to vm tab, select interfaces sub tab 2. Click new, add interface, click ok 3. Error message is displayed: NETWORK_MAC_ADDRESS_IN_USE Additional info: The validation error is in MacAddressValidator:isMacAssignableValidator The reason is that the macPool used to validate the macs of new interfaces is initialized with the pool of possible macs, and not the macs actually used. This happens in MacPoolManagerRanges:44 : this.macsStorage = createMacsStorage(rangesBoundaries); The range boundaries are retrieved from the db using MacPoolDao.