Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Btw. there is https://bugzilla.redhat.com/show_bug.cgi?id=1406520, that was causing troubles setting up the cloud-inin on the virtualized box:
systemctl status cloud-init-local
● cloud-init-local.service - Initial cloud-init job (pre-networking)
Loaded: loaded (/usr/lib/systemd/system/cloud-init-local.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Tue 2017-08-29 06:16:38 EDT; 2h 22min ago
Main PID: 492 (code=exited, status=1/FAILURE)
Aug 29 06:16:38 localhost.localdomain cloud-init[492]: self.selinux.restorecon(path, recursive=self....ve)
Aug 29 06:16:38 localhost.localdomain cloud-init[492]: File "/usr/lib64/python2.7/site-packages/seli...con
Aug 29 06:16:38 localhost.localdomain cloud-init[492]: restorecon(os.path.join(root, name))
Aug 29 06:16:38 localhost.localdomain cloud-init[492]: File "/usr/lib64/python2.7/site-packages/seli...con
Aug 29 06:16:38 localhost.localdomain cloud-init[492]: status, context = matchpathcon(path, mode)
Aug 29 06:16:38 localhost.localdomain cloud-init[492]: OSError: [Errno 2] No such file or directory
Aug 29 06:16:38 localhost.localdomain systemd[1]: cloud-init-local.service: main process exited, cod...URE
Aug 29 06:16:38 localhost.localdomain systemd[1]: Failed to start Initial cloud-init job (pre-networking).
Aug 29 06:16:38 localhost.localdomain systemd[1]: Unit cloud-init-local.service entered failed state.
Aug 29 06:16:38 localhost.localdomain systemd[1]: cloud-init-local.service failed.
Hint: Some lines were ellipsized, use -l to show in full.
The fix for this issue should be delivered in RHEL 7.4 (see https://bugzilla.redhat.com/show_bug.cgi?id=1406520) for more details.
Build: Satellite 6.2.12 snap1
Verified on RHV Version 4.0.6.3-0.1.el7ev
Red Hat Enterprise Linux Server release 7.4 (Maipo)
PFA Test User data template
Partial log:
Complete!
Uploading Enabled Repositories Report
Loaded plugins: product-id
Note: Forwarding request to 'systemctl enable puppet.service'.
Created symlink from /etc/systemd/system/multi-user.target.wants/puppet.service to /usr/lib/systemd/system/puppet.service.
Redirecting to /bin/systemctl start puppet.service
2017-08-29 11:04:22,929 - util.py[WARNING]: Configuration entry 'tries' is not an integer, using 10 instead
2017-08-29 11:04:22,942 - util.py[WARNING]: /etc/ssh/ssh_host_dsa_key.pub: failed to open, can not phone home that data!
Cloud-init v. 0.7.9 finished at Tue, 29 Aug 2017 15:04:24 +0000. Datasource DataSourceConfigDrive [local,ver=2][source=/dev/sr1]. Up 176.44 seconds
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-2017:2803