Bug 1572419
Summary: | 3.9.27: logging-curator pod crash looping - run.sh not found | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Mike Fiedler <mifiedle> |
Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.9.0 | CC: | aos-bugs, ewolinet, jkarasek, juzhao, rmeggins, smunilla |
Target Milestone: | --- | ||
Target Release: | 3.9.z | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: Curator pod is crash-looping because it was unable to find its entrypoint script due to a bad merge from origin into downstream dist-git
Consequence: The pod was not functional and cycled crash-looping
Fix: The code was synced with upstream.
Result:
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-17 06:43:40 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: | 1564350 |
Description
Mike Fiedler
2018-04-27 01:18:59 UTC
Tested with logging-curator/images/v3.9.27-1,issue is not fixed Tested with logging-curator/images/v3.9.27-2, there is not run.sh in curator pod. The image is not right # oc get po | grep curator logging-curator-1-btvfl 1/1 Running 4 20m # oc rsh logging-curator-1-btvfl sh-4.2$ ls -al total 44 drwxrwxr-x. 2 root root 176 May 3 01:54 . drwxr-xr-x. 3 root root 17 May 2 13:59 .. -rw-------. 1 1000070000 root 47 May 3 01:56 .bash_history -rwxrwxr--. 1 root root 0 May 2 13:58 __init__.py -rwxrwxr-x. 1 root root 8093 May 2 13:58 curator_cmd.py -rw-r--r--. 1 1000070000 root 6753 May 3 01:38 curator_cmd.pyc -rwxrwxr-x. 1 root root 4235 May 2 13:58 parser.py -rw-r--r--. 1 1000070000 root 4095 May 3 01:38 parser.pyc -rwxrwxr-x. 1 root root 3427 May 2 13:58 run_cron.py -rwxrwxr-x. 1 root root 221 May 2 13:58 util.py -rw-r--r--. 1 1000070000 root 488 May 3 01:38 util.pyc There is not supposed to be a run.sh. The entrypoint was changed: http://pkgs.devel.redhat.com/cgit/rpms/logging-curator-docker/tree/Dockerfile?h=rhaos-3.9-rhel-7#n44 Per your output in c#8... not the pod is running changed to VERIFIED, tested with logging-curator/images/v3.9.27-2, the entrypoint was changed and pod could be started up Fix is back ported to logging-curator-v3.9.27-1, curator pod could be started up # oc get po -n logging | grep curator logging-curator-1-9h7g8 1/1 Running 0 12m 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:1566 |