Project

General

Profile

Actions

Feature #15664

open

Permit duplicate unmanaged MAC addresses in compute orchestration

Added by Matthias Kneer almost 9 years ago. Updated almost 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Network
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hello,

We have the following scenario:

We have two oVirt management hosts with the same mac address ranges. We are using foreman as ENC and therefore all facts are also available on the foreman. When we try to create a new VM on the 2nd cluster (which came after the 1st cluster ;)) we always receive the following error - until we delete the facts for the conflicting host

Could not create the host:
Failed to destroy a compute OVA (mgmt02) (oVirt) instance <some_hostname>: Cannot remove VM: The following disks are locked: <some_hostname>_Disk1. Please try again in a few minutes.
mac 00:1a:4a:16:01:55 is already used by <some_other_hostname>

Is it possible to disable foremans check for a duplicated mac address?

Thanks in advance,
mat1010

Actions #1

Updated by Dominic Cleal almost 9 years ago

  • Category changed from Compute resources - oVirt to Network

This isn't possible for managed interfaces, the MAC must be unique or managed interfaces must be disabled (i.e. no DNS, DHCP, TFTP orchestration as these may be shared services).

Actions #2

Updated by Matthias Kneer almost 9 years ago

Dominic Cleal wrote:

This isn't possible for managed interfaces, the MAC must be unique or managed interfaces must be disabled (i.e. no DNS, DHCP, TFTP orchestration as these may be shared services).

Wouldn't it be enough to only check duplicated MAC addresses for foreman managed hosts? As I said - foreman is configured to act as ENC - so not all the hosts that are visible in foreman are actually managed by foreman / DNS, DHCP, TFTP.

Actions #3

Updated by Dominic Cleal almost 9 years ago

  • Subject changed from Duplicate mac address to Permit duplicate unmanaged MAC addresses in compute orchestration

Ah, there's an impl difference between the MAC uniqueness in NICs (Nic::Base checks only managed interfaces) and compute orchestration's retrieval of MACs (Orchestration::Compute#validate_foreman_attr checks all interfaces). When using a MAC from the compute resource, as it does with oVirt and others, the MAC uniqueness is global rather than only managed.

Actions

Also available in: Atom PDF