Project

General

Profile

Actions

Bug #28330

closed

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

Added by Lukas Zapletal almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Category:
Discovery plugin
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
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 2 (0 open2 closed)

Related to Discovery - Bug #16143: Discovered host IP address is not changed to fall within the subnet rangeClosedLukas ZapletalActions
Related to Discovery - Bug #30478: Kexec does not handle NEW/OLD discovered IPResolvedLukas ZapletalActions
Actions #1

Updated by The Foreman Bot almost 5 years ago

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

Updated by Lukas Zapletal almost 5 years ago

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

Updated by The Foreman Bot almost 5 years ago

  • Fixed in Releases Discovery Plugin 16.0 added
Actions #4

Updated by Anonymous almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions #5

Updated by Lukas Zapletal over 4 years ago

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

Also available in: Atom PDF