Project

General

Profile

Actions

Bug #7971

closed

DHCP conflict still triggered for non-conflicting leases

Added by Lukas Zapletal over 9 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Orchestration
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

When I was reproducing a bug related to pull request #1430 I noticed that in my
case (Ruby 2.0) it's not the self object without hostname set, but always
other object.

This check should be commutative, I am not sure if Ruby optimizes the call or
this has changed somehow in the runtime. But since hostname of the new host is
always set (we have a validator for this), adding commutative property should
not work.

I believe this should fix a problem I have with OpenStack (Discovery) installer
(RHBZ#1152516).


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #5637: DHCP conflicts triggered for non-conflicting leasesClosedGreg Sutcliffe05/08/2014Actions
Actions

Also available in: Atom PDF