Bug 1479165
| Summary: | [3.6] ansible_service_broker_image_tag should be set to 3.6 by default instead of latest | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> | |
| Component: | Installer | Assignee: | ewolinet | |
| Status: | CLOSED ERRATA | QA Contact: | Johnny Liu <jialiu> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | high | |||
| Version: | 3.6.0 | CC: | aos-bugs, jokerman, mmccomas | |
| Target Milestone: | --- | |||
| Target Release: | 3.6.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
The default image tag for ansible service now defaults to 'v3.6' rather than 'latest' ensuring that the appropriate release is deployed.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1484323 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-05 17:42:58 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1484323 | |||
|
Description
Johnny Liu
2017-08-08 06:10:19 UTC
Verified this bug with openshift-ansible-3.6.173.0.7-2.git.0.340aa2c.el7.noarch, and PASS.
[root@openshift-141 ~]# oc project openshift-ansible-service-broker
Now using project "openshift-ansible-service-broker" on server
[root@openshift-141 ~]# oc get po
NAME READY STATUS RESTARTS AGE
asb-3958080670-z5mx2 1/1 Running 0 8m
etcd-1487946270-bpc71 1/1 Running 0 8m
[root@openshift-141 ~]# oc describe po asb-3958080670-z5mx2 | grep Image
Image: openshift3/ose-ansible-service-broker:v3.6
Image ID: docker-pullable://registry.access.redhat.com/openshift3/ose-ansible-service-broker@sha256:4d5b8059647bca60328f5e5b1307422497409e9ae1c77fdc83503cf911ab1e24
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:2639 |