Bug 1442185 - [3.5] OpenShift logging pods not deploying using correct image version
Summary: [3.5] OpenShift logging pods not deploying using correct image version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.5.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.5.z
Assignee: Scott Dodson
QA Contact: Gaoyun Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-13 18:01 UTC by Chris Callegari
Modified: 2017-04-25 17:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The installer previously incorrectly set the default logging and metrics image versions. Because the installer is unique per OCP minor release we've hardcoded the default of '3.5.0' instead. These defaults can still be overridden by setting openshift_hosted_logging_deployer_version or openshift_hosted_metrics_deployer_version for logging and metrics respectively.
Clone Of:
Environment:
Last Closed: 2017-04-25 17:43:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1140 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-04-25 21:41:12 UTC

Description Chris Callegari 2017-04-13 18:01:48 UTC 
Description of problem:
Upon initial OpenShift installation logging not deploying pods.  Pods try to pull bad image id

Version-Release number of selected component (if applicable):
3.5

How reproducible:
Always

Steps to Reproduce:
1.  My OpenShift hosts file - http://pastebin.test.redhat.com/475315
2.  oc client output for logging project - http://pastebin.test.redhat.com/475316
3.

Actual results:
Logging stack is not deployed

Expected results:
Logging stack is deployed successfully

Additional info:
Comment 2 Scott Dodson 2017-04-13 19:05:43 UTC 
https://github.com/openshift/openshift-ansible/pull/3925
Comment 3 Gaoyun Pei 2017-04-14 07:12:45 UTC 
QE could reproduce this bug with openshift-ansible-3.5.53-1.git.0.8ade9f2.el7.noarch.rpm

When openshift_release=v3.5 specified in ansible inventory file, for logging deployment, installer will use 3.5 as openshift_logging_image_version instead of 3.5.0.

Wait for new openshift-ansible package which contains the fix to verify this bug.
Comment 4 Gaoyun Pei 2017-04-19 03:31:03 UTC 
Verify this bug with openshift-ansible-3.5.55-1.git.0.29802ee.el7.noarch.rpm

With the following options set in ansible inventory, logging pod were deployed.
openshift_hosted_logging_deploy=true
openshift_release=v3.5

[root@qe-gpei-35-bug-2-master-1 ~]# oc get pod -n logging
NAME                          READY     STATUS    RESTARTS   AGE
logging-curator-1-r8qrf       1/1       Running   1          33m
logging-es-be2lr4zy-1-brczd   1/1       Running   0          32m
logging-fluentd-65nls         1/1       Running   0          32m
logging-fluentd-8g3gf         1/1       Running   0          32m
logging-kibana-1-p6d6c        2/2       Running   0          32m

The images pulled are registry.access.redhat.com/openshift3/logging-*:3.5.0
Comment 6 errata-xmlrpc 2017-04-25 17:43:12 UTC 
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:1140
Note You need to log in before you can comment on or make changes to this bug.