It does not get downloaded on slow networks, therefore the kexec HTTPS call timeouts, subsequent calls are raising errors on exclusive FLOCK failure. This change downloads it in a separate thread. Side effect: all kexec calls now return immediately with success (even when the URL was wrong and the host will never download anything and kexec).
TRIAGE: Small fix, big customer. Requesting 6.8.
REL-ENG: Please pull smart_proxy_discovery_image-1.2.0 from upstream repo.
QA: Regression testing for kexec workflow.
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30149 has been resolved.
on sat6.8.0 snap6
# hammer -u admin -p changeme sync-plan info --id 1
Start Date: 2020/06/29 16:18:00
Recurring Logic ID: 1
Created at: 2020/06/29 15:18:53
Updated at: 2020/06/29 15:18:53
Next Sync: 2020/06/29 16:18:00
1) ID: 1
smart proxy is unable to perform kexec.
It is trying to access the wrong host IP.
the discovered host uses a temporary IP, and while provisioning it, a part of the orchestration creates a dhcp reservation with a new address.
The kexec part tries to use the new IP.
It looks like the facts hash is empty in the kexec method.
The behavior is the same as reported here: https://projects.theforeman.org/issues/30478#change-139614
Can you discover kexec host and then check if fact named discovery_bootip (not bootif but bootIP) is present please?
Two patches are actually needed to fix this one, one in core one in discovery.
re-tested the updated commit and both scenarios now work fine:
Since the kexec workflow issue is not related to this bug, i'm going to file a standalone BZ for it:
Since i was able to verify the kexec workflow using its patch, i can now put this BZ to VERIFIED.
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.