Bug 1837136 - FIPs library issues will prevent metering operator from a successful installation
Summary: FIPs library issues will prevent metering operator from a successful installa...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Metering Operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.5.0
Assignee: tflannag
QA Contact: Peter Ruan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-18 22:12 UTC by Peter Ruan
Modified: 2020-07-13 17:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-13 17:39:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:2409 0 None None None 2020-07-13 17:40:17 UTC

Description Peter Ruan 2020-05-18 22:12:57 UTC
Description of problem:
with OCP 4.5 clusters that has FIPs enabled, the metering-operator will fail

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

How reproducible:
always

Steps to Reproduce:
1. Install from metering via OLM from the Operator Hub
2. watch the ansible pod log
3.

Actual results:
TASK [meteringconfig : Update the MeteringConfig status] ***********************
task path: /opt/ansible/roles/meteringconfig/tasks/update_meteringconfig_status.yml:3
Monday 18 May 2020  20:00:45 +0000 (0:00:00.170)       0:00:03.984 ************ 
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/.ansible-/tmp/ansible-tmp-1589832046.11-1568-14035460109084/AnsiballZ_k8s_status.py\", line 102, in <module>\n    _ansiballz_main()\n  File \"/tmp/.ansible-/tmp/ansible-tmp-1589832046.11-1568-14035460109084/AnsiballZ_k8s_status.py\", line 94, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/tmp/.ansible-/tmp/ansible-tmp-1589832046.11-1568-14035460109084/AnsiballZ_k8s_status.py\", line 40, in invoke_module\n    runpy.run_module(mod_name='ansible.modules.k8s_status', init_globals=None, run_name='__main__', alter_sys=True)\n  File \"/usr/lib64/python2.7/runpy.py\", line 176, in run_module\n    fname, loader, pkg_name)\n  File \"/usr/lib64/python2.7/runpy.py\", line 82, in _run_module_code\n    mod_name, mod_fname, mod_loader, pkg_name)\n  File \"/usr/lib64/python2.7/runpy.py\", line 72, in _run_code\n    exec code in run_globals\n  File \"/tmp/ansible_k8s_status_payload_dcmrBJ/ansible_k8s_status_payload.zip/ansible/modules/k8s_status.py\", line 381, in <module>\n  File \"/tmp/ansible_k8s_status_payload_dcmrBJ/ansible_k8s_status_payload.zip/ansible/modules/k8s_status.py\", line 248, in main\n  File \"/tmp/ansible_k8s_status_payload_dcmrBJ/ansible_k8s_status_payload.zip/ansible/modules/k8s_status.py\", line 275, in execute_module\n  File \"/tmp/ansible_k8s_status_payload_dcmrBJ/ansible_k8s_status_payload.zip/ansible/module_utils/k8s/common.py\", line 200, in get_api_client\n  File \"/usr/lib/python2.7/site-packages/openshift/dynamic/client.py\", line 107, in __init__\n    default_cachefile_name = 'osrcp-{0}.json'.format(hashlib.md5(default_cache_id).hexdigest())\nValueError: error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled for fips\n", "module_stdout": "", "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error", "rc": 1}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ValueError: error:060800A3:digital envelope routines:EVP_DigestInit_ex:disabled for fips

Expected results:


Additional info:

Comment 1 Peter Ruan 2020-05-18 22:14:12 UTC
potential fix?  https://access.redhat.com/solutions/176633

Comment 6 Peter Ruan 2020-05-22 17:14:41 UTC
verified with 4.5.0-0.nightly-2020-05-22-111153

sh-4.2$ rpm -qa python2-openshift
python2-openshift-0.8.11-1.el7.noarch

Comment 8 errata-xmlrpc 2020-07-13 17:39:55 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.