-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.17.0
Description of problem:
After upgrading from Satellite 6.16 to 6.17, PXE-based discovery with auto-provisioning no longer works as expected.
The issue revolves as a 404 "Requested URL was not found" error when the discovered host attempts to register facts with the external Capsule.
How reproducible:
100%
Is this issue a regression from an earlier version:
Yes.
Steps to Reproduce:
With version 6.16, I could do the following workflow:
- client pxe boot to capsule
- get grub menu for fdi and boot into fdi
- allow discovery to work with no interaction
- facts registered and status success with kexec and reboot into build
With version 6.17, the same workflow has different results:
- client pxe boot to capsule
- get grub menu for fdi and boot into fdi
- allow discovery to work with no interaction
- failure occurs with a 404 error
The interesting thing is that if we slightly change the workflow without any
modifications, it's successful:
- client pxe boot to capsule
- get grub menu for fdi and boot into fdi
- interrupt discovery
- select 'Discover with DHCP' and hit enter
- select nic and hit enter
- at credentials screen, highlight next and hit enter
- custom facts screen, select confirm and hit enter
Another slightly modified workflow without any modifications that's successful is to:
- client pxe boot to capsule
- get grub menu for fdi and boot into fdi
- interrupt discovery
- select 'Manual Network Setup'
- select nic and hit enter
- hightlight next and hit enter
- credentials screen, hightlight next and hit enter
- custom facts screen, select confirm and hit enter
Actual behavior:
PXE Discovery Auto-Provisioning with External casule fails with 404 Error
Expected behavior:
PXE Discovery Auto-Provisioning with External casule should work as expected.
Business Impact / Additional info: