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:
Since we are now shipping container-storage-setup rpm and the docker-latest daemon is now calling c-s-s to setup storage, I don't see the real need to still have /bin/docker-latest-storage-setup in the docker-latest package. It seems like just going to confuse customers and generate support calls.
Version-Release number of selected component (if applicable):
docker-latest-1.13.1-5.1.git3a17ad5.el7.x86_64
container-storage-setup-0.3.0-1.git8276a1e.el7.noarch
How reproducible:
always
Not sure what this command is going to do with container-storage-setup since it is a link it will not cause container-storage-setup to do the correct thing.
It is a symlink to container-storage-setup. The only suggest I might have is to have both docker and docker-latest daemons depends on c-s-s daemon which does not exist right now. Currently, docker depends on docker-storage-setup unit file and docker-latest depends on docker-latest-storage-setup unit file where both unit files are the same to run c-s-s.
I thought we had decided that -latest is not coming back. But here it is....
Anyway, I think we will need container-latest-storage-setup which works on /etc/sysconfig/docker-latest-storage-setup file and generates /etc/sysconfig/docker-latest-storage
So that probably means we will need a container-latest-storage-setup package as well to support docker-latest?
I think the best solution to this is to just ship docker-latest-storage-setup with docker-latest until we sunset it. We should have a goal to make it go away as soon as we are comfortable with system containers and running OpenShift on system containers rather then on latest docker. then the docker version can be the latest version. We would ship the Openshift/Kubernetes version in a system container.
I am fine with shipping -latest with old docker-latest-storage-setup stuff. That means we will have separate storage setup code in docker and docker-latest and docker-latest will actually be old code. But I can live with that, I guess. We will not be able to provide new functionality of storage setup in docker-latest. Consider it frozen.
Lokesh can you just revert the changes in docker-latest to use container-storage-setup and continue using docker-latest-storage-setup for the foreseeable future.
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:2345