Support #19745
closed
Katello default template boot loop (wrong foreman_url)
Description
Hello,
after the host was built, it is still getting the same "install-kickstart" configuration over tftp. Over and over again. I have to shutdown the machine manually, chane the boot order to disk and start the mavm again. How cat i do fix it?
Files
| anaconda-ks.cfg | anaconda-ks.cfg | 5.25 KB | Kickstart file on installed host | ||
| production.log_finishing.txt | production.log_finishing.txt | 7.94 KB | production.log snippet | ||
| build_loop.jpg | View build_loop.jpg | 149 KB | the loop | ||
| 00-Katello_Kickstart_Default.erb | 00-Katello_Kickstart_Default.erb | 2.89 KB | Provisioning template |
Updated by Eric Helms over 7 years ago
- Project changed from Katello to Foreman
- Translation missing: en.field_release changed from 228 to 248
Updated by Daniel Lobato Garcia over 7 years ago
- Translation missing: en.field_release changed from 248 to 266
Updated by Anonymous over 7 years ago
- Translation missing: en.field_release deleted (
266)
Updated by Marek Hulán over 7 years ago
- Category set to TFTP
Please check the production.log and the foreman proxy logs. Either the callback to Foreman fails (e.g. some networking issue) so the host is not marked as built or the TFTP change fails for some reason. Also make sure you go through http://projects.theforeman.org/projects/foreman/wiki/Troubleshooting#How-to-provide-enough-info-to-get-help
Updated by Anonymous over 7 years ago
- File anaconda-ks.cfg anaconda-ks.cfg added
- File production.log_finishing.txt production.log_finishing.txt added
- File build_loop.jpg build_loop.jpg added
Hey,
Denis is absent on buisiness so i try to represent him.
Sadly we don't have any errors or exception logged neither in production.log nor in proxy.log.
The provisioning of a CentOS 7.3.1611 host finished without problems. I tried manually to "Inform the build system that we are done" like in the kickstart file and attached the appropriate production.log snippet.
Tell me if i can provide more specific information.
Updated by Marek Hulán over 7 years ago
Interesting, I reviewed your anaconda template and for some reason, it generates wrong url for "Inform the build system that we are done" callback. Normally it should look like
wget -q -O /dev/null --no-check-certificate http://+++foreman url+++/unattended/built?token=a2f97d38-2813-46e1-8839-a3ed522a006e
in your case it's
wget -q -O /dev/null --no-check-certificate http://+++foreman url+++/unattended/provision?token=a2f97d38-2813-46e1-8839-a3ed522a006e
Did you modify the template? Could you post it's current content? It seems Foreman never finds out that the host is built and therefore it does not even try to change the TFTP configuration.
Updated by Anonymous over 7 years ago
Resolving the provisioning templates shows that we're using '00-Katello Kickstart Default' for this host.
We only added some snippets to this template, we didn't touched the 'foreman_url'.
Updated by Daniel Lobato Garcia over 7 years ago
- Tracker changed from Bug to Support
- Subject changed from Build loop to Katello default template boot loop (wrong foreman_url)
I think the problem with it is that on 1.15 onward, the template was updated. `foreman_url` resolves to the provision URL, so to get the real one you have to call `foreman_url('built')`.
I believe you can get this fix by updating Katello, but if that's not possible, see the changes here, it's quite small.
https://github.com/Katello/katello/commit/d3541c40379d9dab7f4511199c0f9a0b1228d183
Hope this works :)
Updated by Marek Hulán over 7 years ago
- Related to Bug #17903: Unattended template doesn't call 'built' added
Updated by Marek Hulán over 7 years ago
- Category changed from TFTP to Templates
Based on the name, this template does not come directly from Katello but is some custom version. Therefore it was not updated. Anyway, I agree, foreman_url needs to be changed to foreman_url('built'). Please let us know whether it helped.
Updated by Anonymous over 7 years ago
I see we have a 'Katello Kickstart Default' template as well, there it is already foreman_url('built'). So the template with the '00-' prefix must be our customized copy, you're right.
I modified our template appropriately and the provisioning works as it should. Thank you.
Is this new for the Katello version 3.4?
We have recently updated Katello to 3.4.0.2.
Updated by Daniel Lobato Garcia over 7 years ago
- Status changed from New to Closed
Yes, this changed on Foreman 1.15, and Katello 3.4 adapted to it. Glad to hear it's solved!