Bug 2271009 - [RHOSP 17.1] Autoscaling on Telemetry failing with FIPS enabled
Summary: [RHOSP 17.1] Autoscaling on Telemetry failing with FIPS enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-aodh
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z4
: 17.1
Assignee: Yadnesh Kulkarni
QA Contact: myadla
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-03-22 11:33 UTC by Yadnesh Kulkarni
Modified: 2024-11-21 09:39 UTC (History)
5 users (show)

Fixed In Version: openstack-aodh-12.0.1-17.1.20240404150820.9ac090b.el9ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-11-21 09:39:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-31696 0 None None None 2024-03-22 11:33:50 UTC
Red Hat Product Errata RHBA-2024:9974 0 None None None 2024-11-21 09:39:57 UTC

Description Yadnesh Kulkarni 2024-03-22 11:33:06 UTC
Description of problem:
Alarm is not being triggered on the setup with autoscaling with FIPS enabled
 
The issue with the Alarm not being triggered is resolved by disabling FIPS in the deployment
 
Here is the error with FIPS enabled
>>> hashlib.md5(str('e08aebab-8e19-43d5-89f6-ff127ccaa833').encode())
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ValueError: [digital envelope routines] unsupported


How reproducible:
Create autoscaling stack on FIPS enabled environment.

Comment 14 errata-xmlrpc 2024-11-21 09:39:56 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 (RHOSP 17.1.4 bug fix and enhancement 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-2024:9974


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