Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Description of problem:
We need to change docker-sotrage-setup systemd unit file to create following
dependency.
-After=cloud-final.service
+After=cloud-init.service
This is the change introduced by upstream commit.
commit 308c5e37223e54072a6b4be1dd8998aad7e91e65
Author: Colin Walters <walters>
Date: Mon Oct 24 11:52:31 2016 -0400
systemd: Order After=cloud-init.service, not cloud-final
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Hi
I am not able to install docker from cloud-init with this change, because of circular dependency,:
cloud init is installing and launching docker, which wants docker-storage which should be launched after cloud init
I am using these packages
[root@ansible-runner ~]# yum list installed | grep docker
docker.x86_64 1.10.3-46.el7.14 @rhel7-extras
docker-common.x86_64 1.10.3-46.el7.14 @rhel7-extras
docker-rhel-push-plugin.x86_64 1.10.3-46.el7.14 @rhel7-extras
docker-selinux.x86_64 1.10.3-46.el7.14 @rhel7-extras
root@ansible-runner ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)
[root@ansi
We have no plans to ship another version of Docker at this time. RHEL7 is in final support stages where only security fixes will get released. Customers should move to use Podman which is available starting in RHEL 7.6.
Description of problem: We need to change docker-sotrage-setup systemd unit file to create following dependency. -After=cloud-final.service +After=cloud-init.service This is the change introduced by upstream commit. commit 308c5e37223e54072a6b4be1dd8998aad7e91e65 Author: Colin Walters <walters> Date: Mon Oct 24 11:52:31 2016 -0400 systemd: Order After=cloud-init.service, not cloud-final Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: