Back to bug 1304038
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jeremy Eder | 2016-02-02 17:54:39 UTC | Comment 0 is private | 1 | 0 |
| Priority | unspecified | urgent | ||
| Lokesh Mandvekar | 2016-02-02 17:58:23 UTC | Keywords | Extras, ZStream | |
| Status | NEW | ASSIGNED | ||
| Assignee | dwalsh | lsm5 | ||
| Lokesh Mandvekar | 2016-02-02 17:58:42 UTC | Blocks | 1287902 | |
| Lokesh Mandvekar | 2016-02-02 18:00:29 UTC | Version | 7.3 | 7.2 |
| Lokesh Mandvekar | 2016-02-02 18:41:39 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | docker-1.9.1-16.el7 | |||
| Lokesh Mandvekar | 2016-02-02 19:08:48 UTC | CC | lfriedma, sghosh | |
| Laurie Friedman | 2016-02-10 00:27:05 UTC | Blocks | 1287902 | 1298318 |
| Lokesh Mandvekar | 2016-03-08 15:53:41 UTC | CC | sdodson | |
| Lokesh Mandvekar | 2016-03-08 19:04:18 UTC | Fixed In Version | docker-1.9.1-16.el7 | docker-1.9.1-17.el7 |
| errata-xmlrpc | 2016-03-08 20:26:34 UTC | Status | MODIFIED | ON_QA |
| Luwen Su | 2016-03-17 15:32:12 UTC | Status | ON_QA | VERIFIED |
| CC | lsu | |||
| Lokesh Mandvekar | 2016-03-22 19:40:08 UTC | Blocks | 1298318 | |
| Lokesh Mandvekar | 2016-03-30 14:40:34 UTC | Doc Text | Cause: We have 2 channels with different release schedules. 1) 'RHEL Extras', on the RHEL schedule and includes docker. This is set to release a new version of docker-1.9. 2) 'OpenShift', on their own schedule, but they rely on docker. However, docker 1.9 has issues with OpenShift 3.1. Consequence: If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it will cause stability issues. We want customers to wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. Fix: Docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. Result: OpenShift customers doing a 'yum update' will get the docker-1.9 package *only if* they have atomic-openshift 3.2 or newer / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. |
|
| Yoana Ruseva | 2016-03-30 15:37:36 UTC | CC | yruseva | |
| Doc Text | Cause: We have 2 channels with different release schedules. 1) 'RHEL Extras', on the RHEL schedule and includes docker. This is set to release a new version of docker-1.9. 2) 'OpenShift', on their own schedule, but they rely on docker. However, docker 1.9 has issues with OpenShift 3.1. Consequence: If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it will cause stability issues. We want customers to wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. Fix: Docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. Result: OpenShift customers doing a 'yum update' will get the docker-1.9 package *only if* they have atomic-openshift 3.2 or newer / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. | docker 1.9 is unstable when used with OpenShift 3.1 If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it will cause stability issues. Customers should wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. To ensure this, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. OpenShift customers doing a "yum update" will get the docker-1.9 package *only if* they have atomic-openshift 3.2 or newer / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Yoana Ruseva | 2016-03-30 15:39:35 UTC | Doc Text | docker 1.9 is unstable when used with OpenShift 3.1 If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it will cause stability issues. Customers should wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. To ensure this, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. OpenShift customers doing a "yum update" will get the docker-1.9 package *only if* they have atomic-openshift 3.2 or newer / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. | docker 1.9 is unstable when used with OpenShift 3.1 If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it causes stability issues. Customers should wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. To ensure this, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. OpenShift customers doing a "yum update" will get the docker-1.9 package *only if* they have atomic-openshift 3.2 or newer / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. |
| Lokesh Mandvekar | 2016-03-30 15:47:08 UTC | Doc Text | docker 1.9 is unstable when used with OpenShift 3.1 If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it causes stability issues. Customers should wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. To ensure this, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. OpenShift customers doing a "yum update" will get the docker-1.9 package *only if* they have atomic-openshift 3.2 or newer / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. | docker 1.9 is unstable when used with OpenShift 3.1 If docker 1.9 and atomic-openshift 3.1 / origin 1.1 are installed simultaneously, it causes stability issues. Customers should wait until atomic-openshift 3.2 / origin 1.2 are released before upgrading to docker 1.9. To ensure this, docker 1.9 has been packaged to conflict with atomic-openshift versions older than 3.2 and origin versions older than 1.2. OpenShift customers doing a "yum update" will get the docker-1.9 package *only if* they have atomic-openshift 3.2 / origin 1.2 or newer installed. Simultaneous installation of docker 1.9 with older versions of atomic-openshift or origin will not be allowed. |
| errata-xmlrpc | 2016-03-31 00:26:11 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-03-31 23:23:50 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-03-31 19:23:50 UTC | |||
| Yoana Ruseva | 2016-05-12 10:06:58 UTC | Docs Contact | yruseva | |
| Alasdair Kergon | 2019-03-06 02:45:46 UTC | Pool ID | 220 | 238 |
Back to bug 1304038