Bug 1540437 – Logging couldn't be deployed using ose-ansible:v3.7 image

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1540437 - Logging couldn't be deployed using ose-ansible:v3.7 image

Summary:	Logging couldn't be deployed using ose-ansible:v3.7 image

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.7.1
Hardware:	Unspecified Unspecified

Priority	low Severity medium
Target Milestone:	---
Target Release:	3.7.z
Assigned To:	ewolinet
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-01-30 23:51 EST by Anping Li
Modified:	2018-04-05 05:37 EDT (History)
CC List:	4 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	Bad cherry pick performed. Corrected the ansible tasks used to be appropriate for the version of ansible used for 3.7
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-05 05:37:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
deploying logs (39.40 KB, application/x-gzip) 2018-01-31 00:18 EST, Anping Li	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0636	None	None	None	2018-04-05 05:37 EDT

Groups: None (edit)

Comment 1 Anping Li 2018-01-31 00:18 EST

Created attachment 1388722 [details]
deploying logs

Comment 2 Scott Dodson 2018-01-31 13:50:52 EST

This should be fixed by https://github.com/openshift/openshift-ansible/pull/6742

Which is in openshift-ansible-3.7.25-1 and newer.

Comment 3 Anping Li 2018-02-01 06:22:19 EST

Verified in ose-ansible:v3.7.26

Comment 9 errata-xmlrpc 2018-04-05 05:37:08 EDT

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-2018:0636

Note You need to log in before you can comment on or make changes to this bug.