Red Hat Bugzilla – Bug 1257833
Disabling token_duration disables ks template substitution
Last modified: 2016-10-07 13:24:32 EDT
Description of problem: When using capsules, setting the token_duration to "0" stops the ks=<capsule> in the PXE template being set and reverts to ks=<satellite server>
Version-Release number of selected component (if applicable):6.1.1
Steps to Reproduce:
1. Create a capsule and set subnet, domain and location. Capsule requires "Templates" option.
2. Create a new host using the subnet associated to the capsule & subnet
3. Check /var/lib/tftboot/pxelinux.cfg/<mac addr> on the capsule
append initrd=boot/RedHat-7.1-x86_64-initrd.img ks=http://<satellite Server>:80/unattended/provision network ks.sendmac
append initrd=boot/RedHat-7.1-x86_64-initrd.img ks=http://<capsule servre>:8000/unattended/provision?token=42e3c2e3-3841-44ab-a65a-c2dddfdff16f network ks.sendmac
Triage notes: Template proxying cannot work without tokens. Instead silently falling back to direct connection, we could raise an error.
Created redmine issue http://projects.theforeman.org/issues/11602 from this bug
I would not like to support token less installation in general, and in particular on capsules. the token is a unique way of identifying the host, regardless of ip address / mac address (e.g. which NIC used to boot it) etc. all the other alternative/legacy options have their own quirks.
the token duration is configurable (e.g. if the use wish to create a nearly fixed tokens that is possible) however its usually hidden from the user, and I would like to understand the root cause of why disabling tokens.
however, afaiu, in https://github.com/theforeman/smart-proxy/commit/38a0935152a0cc6f04c3843b8258866b2b96e0ad lukas added a way to proxy the additional information required to identify the requesting host, in which case, this might be already solved in 6.2
adding needinfo for lzap to confirm, and needinfo or reported to explain more of what is the usage case for turning off tokens.
Yes, that should fix the issue (Satellite 6.2).
Can you provide some verification steps for QE based upon the changes referenced in comment 5? Thanks!
so the process is simple, setup provisioning with Capsule templating (without direct connection to Satellite - make sure to block all the communication) and also set token_duration to zero in global settings. Then provision a bare-metal or VM host which installs via Anaconda (e.g. not image-based provisioning).
Based on Comment 8, I am marking this as closed for 6.2 If you are seeing issues with this, please feel free to re-open with additional information.