Project

General

Profile

Bug #28330

Reboot/kexec is ussed against new (reserved) IP address

Added by Lukas Zapletal over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
Discovery plugin
Target version:
Discovery Plugin 16.0
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman_discovery/pull/492
Fixed in Releases:
Discovery Plugin 16.0
Found in Releases:

Description

With the #16143 change discovery now performs unused_ip call during provisioning. This changes IP address and creates DHCP reservation, however the discovered node still have the old lease. The fix is to use old lease IP to perform reboot or kexec API commands. There could be a race condition when a node already acquired new IP and reconfigured network, for this reason if the first request fails, there is additional second query against the reserved IP just to make sure.

Related issues

Related to Discovery - Bug #16143: Discovered host IP address is not changed to fall within the subnet rangeClosed
Related to Discovery - Bug #30478: Kexec does not handle NEW/OLD discovered IPResolved

Associated revisions

Revision d1c5199c (diff)
Added by Lukas Zapletal over 2 years ago

Fixes #28330 - reboot/kexec use old IP address

History

#1 Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman_discovery/pull/492 added

#2 Updated by Lukas Zapletal over 2 years ago

  • Related to Bug #16143: Discovered host IP address is not changed to fall within the subnet range added

#3 Updated by The Foreman Bot over 2 years ago

  • Fixed in Releases Discovery Plugin 16.0 added

#4 Updated by Anonymous over 2 years ago

  • Status changed from Ready For Testing to Closed

#5 Updated by Lukas Zapletal almost 2 years ago

  • Related to Bug #30478: Kexec does not handle NEW/OLD discovered IP added

Also available in: Atom PDF