Bug 1879571

Summary: unable to kexec discovered hosts - satellite tries to reach wrong IP
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: Discovery PluginAssignee: Lukas Zapletal <lzap>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: egolov, lzap, rabajaj
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman_discovery-16.1.2 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:09:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Roman Plevka 2020-09-16 14:30:25 UTC
Description of problem:
This is a tracker for the following issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1848291#c4

The issue was not related to the BZ#1848291

Version-Release number of selected component (if applicable):
sat6.8.0-14

Comment 2 Bryan Kearney 2020-09-17 08:04:17 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30478 has been resolved.

Comment 6 Roman Plevka 2020-10-01 08:56:19 UTC
VERIFIED
on sat6.8.0-17

kexec is now attempted on both old (bootip fact) and new ip (orchestration reservation) addresses:

2020-10-01T04:49:47 [W|app|7c13509a] Unable to perform kexec on mac5254006f83e1 (https://192.168.122.35:8443): Timed out connecting to server
2020-10-01T04:49:50 [W|app|7c13509a] Unable to perform kexec on mac5254006f83e1 (https://10.1.5.93:8443): Failed to open TCP connection to 10.1.5.93:8443 (No route to host - connect(2) for "10.1.5.93" port 8443)
2020-10-01T04:49:50 [W|app|7c13509a] Unable to kexec

Comment 9 errata-xmlrpc 2020-10-27 13:09:00 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366