Bug 1842439 - No module named 'ruamel'
Summary: No module named 'ruamel'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.0
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard: neesqa
Depends On: 1842721
Blocks: 1860793
TreeView+ depends on / blocked
 
Reported: 2020-06-01 09:26 UTC by Anping Li
Modified: 2020-08-05 14:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1842721 (view as bug list)
Environment:
Last Closed: 2020-07-13 17:42:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1911 0 None closed Bug 1842439: Vendor ruamel.yaml 2020-10-23 23:03:34 UTC
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:43:07 UTC

Description Anping Li 2020-06-01 09:26:08 UTC
Description of problem:

#oc logs curator-1591002600-2nrz8
Traceback (most recent call last):
  File "/opt/app-root/src/lib/oalconverter/convert.py", line 18, in <module>
    from ruamel import yaml
ModuleNotFoundError: No module named 'ruamel'
Usage: curator [OPTIONS] ACTION_FILE


Version-Release number of selected component (if applicable):
openshift/ose-logging-curator5:v4.5.0-202005302117


How reproducible:
Always

Steps to Reproduce:
1. Deploy clusterlogging 4.5.0
2. Check the curator pod logs

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Cantrill 2020-06-01 15:03:42 UTC
Can you provide the image that demonstrates this?

Comment 6 Anping Li 2020-06-04 02:41:59 UTC
Verified on clusterlogging.4.5.0-202006032057
$ oc get pods
NAME                                            READY   STATUS      RESTARTS   AGE
cluster-logging-operator-565c75fd55-xzf9h       1/1     Running     0          7m21s
curator-1591237800-28b5v                        0/1     Error       0          10m
curator-1591238400-sjflv                        0/1     Completed   0          22s
elasticsearch-cdm-gc0jxyca-1-68c4d68bb8-jld72   2/2     Running     0          15m
elasticsearch-cdm-gc0jxyca-2-7cfd55c65-c26s8    2/2     Running     0          15m
elasticsearch-cdm-gc0jxyca-3-7fc9858bd6-gs5tq   2/2     Running     0          11m
fluentd-7xhd8                                   1/1     Running     0          4m33s
fluentd-g42km                                   1/1     Running     0          5m22s
fluentd-ktfsn                                   1/1     Running     0          5m52s
fluentd-m2fdr                                   1/1     Running     0          6m19s
fluentd-n5t7k                                   1/1     Running     0          6m47s
fluentd-z8cmz                                   1/1     Running     0          4m59s
kibana-64444bf7b8-qsz4s                         2/2     Running     0          6m57s
$ oc get cronjob
NAME                           SCHEDULE       SUSPEND   ACTIVE   LAST SCHEDULE   AGE
curator                        */10 * * * *   False     0        56s             72m
elasticsearch-delete-app       */15 * * * *   False     0        <none>          7m21s
elasticsearch-delete-audit     */15 * * * *   False     0        <none>          7m21s
elasticsearch-delete-infra     */15 * * * *   False     0        <none>          7m21s
elasticsearch-rollover-app     */15 * * * *   False     0        <none>          7m21s
elasticsearch-rollover-audit   */15 * * * *   False     0        <none>          7m21s
elasticsearch-rollover-infra   */15 * * * *   False     0        <none>          7m21s

Comment 7 errata-xmlrpc 2020-07-13 17:42:47 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-2020:2409


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