Bug 1593800
| Summary: | [RFE] forbid new mac pools with overlapping ranges | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Igor Netkachev <inetkach> | |
| Component: | ovirt-engine | Assignee: | eraviv | |
| Status: | CLOSED ERRATA | QA Contact: | Michael Burman <mburman> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.1.8 | CC: | danken, dfediuck, dholler, emarcus, inetkach, lsurette, mburman, mperina, mtessun, pelauter, rdlugyhe, srevivo | |
| Target Milestone: | ovirt-4.4.0 | Keywords: | FutureFeature | |
| Target Release: | 4.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | sync-to-jira | |||
| Fixed In Version: | Doc Type: | Enhancement | ||
| Doc Text: |
When creating a new MAC address pool, its ranges must not overlap with each other or with any ranges in existing MAC address pools.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1639460 1767319 (view as bug list) | Environment: | ||
| Last Closed: | 2020-08-04 13:16:11 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: | 1639460 | |||
| Bug Blocks: | 1537414, 1767319 | |||
|
Description
Igor Netkachev
2018-06-21 15:26:55 UTC
Igor, in "Upon reboot", do you mean "upon ovirt-engine restart"? Would the customer upgrade to 4.2, or at least to the newest 4.1.z version? We have fixed macpool-related bugs in 4.1.11. Eitan, could you look into the customer logs and database? Dan, In customer's scenario it was reboot of hosted-engine VM, but I believe this equates to engine restart. I have asked customer to upgrade to at least 4.1.11 and re-test, will keep you updated on further progress. In my opinion, we need to: 1. warn users if they have mac pools with overlapping ranges. 2. disallow creating new mac pools that overlap exiting ones. In relation to part 2 in comment#7: a. I tested the same situation on a 4.3-master engine and there is no crash. just and error message that duplicates exists in no-duplicate mac pool. b. The crash I was referring to is for the scenario described in BZ1561080, BZ1554180 where if a mac pool constains duplicates, and a the mac pool is then marked with 'forbid duplicates' engine responds with dismay. comment 9 continued: but trying to edit\delete mac pools or vnics on the VMs does prove to cause lots of trouble and mis-behavior, so I would like to re-emphasize the importance of resolving the issue before any upgrade. Igor, please ack. Eitan, Thank you very much for bringing my attention to RHV mis-behavior in case MAC overlap is not removed prior to upgrade! I have forwarded this information to the customer, will let you know once there's any feedback. *** Bug 1537414 has been marked as a duplicate of this bug. *** *** Bug 1492577 has been marked as a duplicate of this bug. *** Warnings are going to be tracked in bug 1639460. Changes to the API behavior are postponed to 4.3. This bug has not been marked as blocker for oVirt 4.3.0. Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1. this bug will now only track the RFE for creating new mac pools. a clone - BZ#1767319 - has been created for the RFE for updating existing mac pools. WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
Verified on - rhvm-4.4.0-0.13.master.el7.noarch WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
WARN: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops: Bug status (VERIFIED) wasn't changed but the folowing should be fixed:
[Found non-acked flags: '{}', ]
For more info please contact: rhv-devops
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 (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3247 |