Bug 1467553

Summary:	[WALA] Remove FIPS from default config in WALA-2.2.14
Product:	Red Hat Enterprise Linux 7	Reporter:	Yuxin Sun <yuxisun>
Component:	WALinuxAgent	Assignee:	Vitaly Kuznetsov <vkuznets>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.4	CC:	borisb, brendand, danis, hkrijger, jherrman, jopoulso, leiwang, mrezanin, mtessun, stephen.zarkos, vkuznets, wshi, yujiang, yuxisun
Target Milestone:	rc	Keywords:	Extras
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	WALinuxAgent-2.2.14-1.el7	Doc Type:	If docs needed, set a value
Doc Text:	The upstream FIPS feature is currently not working properly, and is therefore not a part of this update. Note that the functional FIPS feature will be a part of the future update.	Story Points:	---
Clone Of:
Clones:	1467559 (view as bug list)		Environment:
Last Closed:	2017-07-13 13:46:35 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:	1451172

Description Yuxin Sun 2017-07-04 08:00:10 UTC

Description of problem:
MSFT wishes us to ship the WALA-2.2.14. But currently the FIPS feature in WALA cannot work well (BZ#1460671).
So shell we remove the FIPS configuration from the waagent.conf and then ship this package?

The FIPS configurations in waagent.conf are:
# Is FIPS enabled
OS.EnableFIPS=n

Comment 2 Miroslav Rezanina 2017-07-04 09:50:57 UTC

Fix included in WALinuxAgent-2.2.14-1.el7

Comment 4 Yuxin Sun 2017-07-05 10:18:43 UTC

Verify in WALinuxAgent-2.2.14-1.el7. Result: PASS
Steps:
1. Prepare a RHEL-7.4 VM in Azure
2. Install the WALinuxAgent-2.2.14-1.el7
3. Check /etc/waagent.conf
Actual result:
There's no line with "FIPS" string.

Comment 6 errata-xmlrpc 2017-07-13 13:46:35 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-2017:1749