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.
This issue is now covered in the 7.2.4 release notes. The note says that we are not providing a migration tool to move existing container images from Docker 1.9 to Docker 1.10. Instead, customers should simply change over to Docker 1.10 and re-pull the container images as needed.
Opening this bug as it is now being targeted for 7.2.5.
Apparently they want this documented for 7.2.5. Here are a few issues:
* When docker 1.10 becomes the default, the migrator must be run before reboot to docker 1.10 on an upgrade.
* The docker 1.8 and 1.9 daemons can run with converted meta-data (because the old meta-data is still there).
* The migrator tool packaged with docker 1.10 = "docker-latest" can work with "docker" data store.
* We need to document this for 7.2.5.
When will docker = docker 1.10?
* Can't have docker be 1.10 until OSE supports it. OSE is starting testing now.
* OSE moves to docker 1.10 for 3.2.1 GA (June 23).
* 7.2.5 GA is June 21 (May 31 code freeze). Need to ask about this since it's after the 7.2.5 release date.
* Are any docker 1.9 updates planned? Yes, 1 fix needed if don't ship docker 1.10. - Lokesh - give docker 1.9 with fix to Martin ASAP so QE can test it now and we can use as a fall back if needed.
* What are the 7.2.6 docker and docker-latest versions? 7.2.6 GA: Aug-02 (docker = TBD; docker-latest= TBD)? Ben / Subhendu
Where does v1.10 migratool need to go?:
* rhel-tools: Migrator tool is a sub-package of docker-latest package that will be included in rhel-tools container (Ian)
* No plans for separate container image for migration tool.
* Not needed in OStree
* Already in Extras from 7.2.4