Hide Forgot
We need the Katello Kickstart User Data template to work with atomic. The current template does things like running yum commands which do not work on atomic.
Created from redmine issue http://projects.theforeman.org/issues/14579
Upstream bug assigned to paji
Moving to POST since upstream bug http://projects.theforeman.org/issues/14579 has been closed
Verified with sat6.2.3. I tried to provision atomic host with following steps: 1. added atomic-host-image from 6.3 under selected libvirt CR 2. associated "Satellite Kickstart Default User Data" template with "Red Hat atomic host 7 OS" 3. created a new host with image-based provisioning Host was provisioned successfully and I can see that it got registered with satellite. But I can't login on atomic host with default user "cloud-user". Am I missing something here ?
Also, I don't see the fixes in "Satellite Kickstart Default User Data" template as shown in the PR attached to upstream issue. like: --- groups: - admin users: - default - name: admin primary-group: admin groups: users shell: /bin/bash sudo: ['ALL=(ALL) ALL'] lock-passwd: false passwd: <%= @host.root_pass %> --- I see these changes in "UserData default" template
Please note that if I use "Userdata default" template then I can login with admin user, however not with cloud-user. And in case of "Satellite Kickstart Default User Data" template, I was not able to login with cloud-user as well as admin. Moving this back to assigned state to get more info.
Verified in Satellite 6.2.3 Snap 4 The Satellite Kickstart Default User Data template has been update with the appropriate content. Can now login to atomic host as admin user. See attached screenshot.
Created attachment 1214046 [details] verification screenshot
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:2108
This bug was fixed in 6.2.3 and was moved to MODIFIED accidentally, re-closing as it was prior.