Description of problem: We now have cloud init template that helps with provisioning with Vmware using userdata enabled images Version-Release number of selected component (if applicable): Satellite 6.6 snap 10 How reproducible: Always Steps to Reproduce: 1. Have a cloud init(userdata) enabled as template on Vmware 2. Add it to satellite 3. Provision using the template Actual results: The provisioned box is not subscribed to satellite As the cloud init template is missing redhat_register snippet Expected results: The provisioned box should be subscribed to Satellite Additional info: Following this guide to reproduce: https://access.redhat.com/blogs/1169563/posts/3640721
Created redmine issue https://projects.theforeman.org/issues/27276 from this bug
Upstream patch will take longer due to tests, so doing a MR since this is a simple and tested one liner.
Build: Satellite 6.6 snap 21 Using the latest changes in templates , provisioned successfully using userdata template 2019-09-26 06:05:54,400 - url_helper.py[DEBUG]: [0/11] open 'http://sat-host:8000/unattended/built?token=4ffbcd0b-3c58-44d1-bf98-0fb3ce7b69f1' with {'url': 'http://sat-host:8000/unattended/built?token=4ffbcd0b-3c58-44d1-bf98-0fb3ce7b69f1', 'headers': {'User-Agent': 'Cloud-Init/18.5'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 5.0} configuration 2019-09-26 06:05:55,228 - url_helper.py[DEBUG]: Read from http://sat-host:8000/unattended/built?token=4ffbcd0b-3c58-44d1-bf98-0fb3ce7b69f1 (200, 0b) after 1 attempts 2019-09-26 06:05:55,228 - handlers.py[DEBUG]: finish: modules-final/config-phone-home: SUCCESS: config-phone-home ran successfully 2019-09-26 06:05:55,228 - main.py[DEBUG]: Ran 5 modules with 0 failures 2019-09-26 06:05:55,230 - util.py[DEBUG]: Creating symbolic link from '/run/cloud-init/result.json' => '../../var/lib/cloud/data/result.json' 2019-09-26 06:05:55,230 - util.py[DEBUG]: Reading from /proc/uptime (quiet=False)
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/RHSA-2019:3172