Bug 1613029
| Summary: | [docs][v2v] RHV should be configured to allow MAC addresses of virt-v2v migrated VMs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Mor <mkalfon> | ||||
| Component: | Documentation | Assignee: | Avital Pinnick <apinnick> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ilanit Stein <istein> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | future | CC: | adahms, apinnick, bugs, dagur, dfediuck, michal.skrivanek, rbarry, royoung | ||||
| Target Milestone: | ovirt-4.3.3 | Keywords: | Documentation | ||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.3+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-05-02 09:13:20 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Mor
2018-08-06 19:31:03 UTC
*** Bug 1612883 has been marked as a duplicate of this bug. *** I think it should elaborate on the different results you get with different mac pool settings. By default you do not need to touch anything, but the imported VMs will use MACs from outside of the pool. This might be surprising since any newly created VM will use MAC from the pool so they'll have entirely different MAC prefixes. OTOH If you choose to configure a MAC Pool range matching the VMware range then the conversion will fail if there is already a VM in the destination DC with the same MAC. Unless "allow duplicate MACs" is enabled for this MAC Pool. I wasn't able to reproduce it on another VM migration not using CSV as input method for VM names. changing severity to low. 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. 4.3.1 has been released a while ago, re-targeting to 4.3.3 for re-evaluation. this is a documentation bug actually Hi Avital, Did you already documented the above? If yes please send us a link and move this bug to on-qa so we could verify Michal, I've been testing v2v imports since RHV-4.2.8-4/CFME-5.10.0.32, and I never added the source mac address to the RHV mac pool range, however the imports worked fine. I wonder - Is this doc bug still relevant? Maybe the code behavior had changed, so that it no longer fails the import, if the source mac is not included in RHV mac pool? Thanks. Still relevant. comment#5 is very clear "If VMs are imported, and a MAC pool for that range has been created for RHV, the import may fail if an existing VM already has claimed that MAC" "If VMs are imported, and a MAC pool for that range has not been created, no steps are necessary, but additional interfaces created o that VM (and VMs created without importing) will not have MAC addresses in the same range" It's a question of desired behavior from the end user (In reply to Avital Pinnick from comment #15) Avital, for the step 6 you added, I would also mention that it's not mandatory. You may wish to configure a new pool matching the VMware range, or not. You will get a different behavior, but you may freely choose one or the other. We should perhaps say "Optional: " and describe briefly (as in comment #17, thanks Ryan!) the difference Thanks, michal LGTM |