Bug 1769258

Summary: ICA HW token missing after the package update [rhel-7.7.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: opencryptokiAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Karel Srot <ksrot>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.7CC: bugproxy, dhorak, fkrska, hannsj_uhl, jkachuck, jomiller, ksrot, ovasik, plautrba, than, tumeya, wchadwic
Target Milestone: rcKeywords: Patch, Regression, ZStream
Target Release: ---   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: opencryptoki-3.11.0-5.el7_7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1756956 Environment:
Last Closed: 2019-11-26 13:58:50 UTC Type: ---
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: 1756956    
Bug Blocks: 1736840    

Description RAD team bot copy to z-stream 2019-11-06 10:05:46 UTC
This bug has been copied from bug #1756956 and has been proposed to be backported to 7.7 z-stream (EUS).

Comment 6 Than Ngo 2019-11-06 14:48:39 UTC
it's fixed in opencryptoki-3.11.0-5.el7_7

Comment 9 IBM Bug Proxy 2019-11-08 07:20:28 UTC
------- Comment From tstaudt.com 2019-11-08 02:12 EDT-------
Verified by IBM with test package provided by Red Hat:

"
Verified by downloading the RPM files
opencryptoki-3.11.0-5.el7_7.s390x.rpm
opencryptoki-ccatok-3.11.0-5.el7_7.s390x.rpm
opencryptoki-ep11tok-3.11.0-5.el7_7.s390x.rpm
opencryptoki-libs-3.11.0-5.el7_7.s390x.rpm
opencryptoki-swtok-3.11.0-5.el7_7.s390x.rpm
to a RHEL7.7 instance showing the missing ICA token when libica-devel package is _not_ installed.

Then upgraded all production packages (i.e. did not have opencrytoki-devel installed) from opencryptoki-3.11.0-3 to 3.11.0-5. After the fixes had been applied, the ICA token displayed successfully.
"

Comment 11 errata-xmlrpc 2019-11-26 13:58:50 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-2019:3980