You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have had a situation where the function of migrating servers from sat5 to sat6 or even registering without migration is automated in ansible, wrapper scripts or using puppet. Would like to use encrypted password for this situation when the password is a permanent part of the ansible or wrapper script or passed to puppet via parameters or hard coded. Is this possible, knowing there will be a issue of getting a key on the server too. Maybe use the existing sat5 cert on the server to allow legacy removal and sat6 cert to register.
The text was updated successfully, but these errors were encountered:
My memory tells me that in recent versions of Spacewalk / Satellite 5 (starting with 5.6 or something), you can actually delete the system using its own certificate. However, we (or rather rhn-migrate-classic-to-rhsm, which we use) need more than just the delete action, and that is only available with an user account, not a system account.
Katello / Satellite 6
It is actually possible to use bootstrap.py against Satellite 6 without providing credentials. You just have to use --skip foreman as this will skip all the API requests that need authentication, and just subscribe the machine. Obviously, you won't get Puppet integration etc in this case.
There are a couple of RFEs against Foreman, to implement API tokens:
I have had a situation where the function of migrating servers from sat5 to sat6 or even registering without migration is automated in ansible, wrapper scripts or using puppet. Would like to use encrypted password for this situation when the password is a permanent part of the ansible or wrapper script or passed to puppet via parameters or hard coded. Is this possible, knowing there will be a issue of getting a key on the server too. Maybe use the existing sat5 cert on the server to allow legacy removal and sat6 cert to register.
The text was updated successfully, but these errors were encountered: