Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1517787 - upgrade script fails for logging-es-ops
Summary: upgrade script fails for logging-es-ops
Keywords:
Status: MODIFIED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.4.z
Assignee: Ruben Romero Montes
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-27 13:14 UTC by Ruben Romero Montes
Modified: 2018-03-14 17:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: The logging-deployer upgrade script does not take into consideration the logging-ops path for performing the healt check during upgrade. Consequence: Deployer upgrade script fail when having ops cluster deployed Fix: Dynamically get the name of the logs path from the cluster-name Result: The aggregated logging stack, having ops deployed, can be upgraded using the deployer pod
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
deployer logs (deleted)
2017-11-27 13:14 UTC, Ruben Romero Montes
no flags Details


Links
System ID Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 799 None None None 2017-11-27 14:33:56 UTC

Description Ruben Romero Montes 2017-11-27 13:14:47 UTC
Created attachment 1359455 [details]
deployer logs

Description of problem:
Upgrade fails due to a hardcoded path for log while checking ES-OPS health status.

log_cmd="oc exec $pod -- cat /elasticsearch/logging-es/logs/logging-es.log"

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

How reproducible:
Always

Steps to Reproduce:
1. Install logging 3.4.1 with ops cluster
2. Run the deployer with MODE=upgrade

Actual results:
+++ eval '[[ -n $(oc exec logging-es-ops-a8rqpgtk-2-q43ws -- cat /elasticsearch/logging-es/logs/logging-es.log | grep '\''\[cluster\.service[[:space:]]*\]'\'') ]]'
+++++ oc exec logging-es-ops-a8rqpgtk-2-q43ws -- cat /elasticsearch/logging-es/logs/logging-es.log
+++++ grep '\[cluster\.service[[:space:]]*\]'
cat: /elasticsearch/logging-es/logs/logging-es.log: No such file or directory

Expected results:
Upgrade succeeds without errors.

Additional info:

Comment 7 Anping Li 2018-01-25 02:51:59 UTC
@Samuel,  the target release is v3.4. The errata is for v3.5,v3.6 and v3.9. The aos-3.7.x+ tag was added. I am puzzled Where the fix will be in?

Comment 9 Samuel Munilla 2018-03-14 17:07:35 UTC
@Anping, I'm not sure why this got added to the wrong advisory. I'll make sure it lives in the right place.


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