Bug 1451275

Summary:

Minor upgrades giving error on yum update

Product:

Red Hat OpenStack

Reporter:

Yolanda Robla <yroblamo>

Component:

openstack-tripleo-heat-templates

Assignee:

Lukas Bezdicka <lbezdick>

Status:

CLOSED ERRATA

QA Contact:

Yurii Prokulevych <yprokule>

Severity:

high

Docs Contact:

Priority:

high

Version:

8.0 (Liberty)

CC:

aguetta, augol, brault, emacchi, fzdarsky, jjoyce, kobi.ginon, lbezdick, mbultel, mburns, mcornea, mlopes, rhel-osp-director-maint, sathlang, yroblamo

Target Milestone:

zstream

Keywords:

Triaged, ZStream

Target Release:

8.0 (Liberty)

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

openstack-tripleo-heat-templates-0.8.14-31.el7ost

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2017-10-25 17:00:15 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:

1458841, 1469518, 1469526

Bug Blocks:

Attachments:

Description	Flags
yum repolist	none
yum.log	none

Description Yolanda Robla 2017-05-16 09:48:15 UTC

Description of problem:

Following the documentation on https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/8/html/upgrading_red_hat_openstack_platform/sect-updating_the_environment, for minor upgrades.

I am subscribed to the rhel system, and have enabled the right repos. When executing an openstack undercloud upgrade, i'm hitting that error:

  Cleanup    : icoutils-0.31.0-3.el7.x86_64                             297/297

/usr/bin/python: symbol lookup error: /lib64/libnsssysinit.so: undefined symbol: PR_GetEnvSecure
Command '['sudo', 'yum', 'update', '-y']' returned non-zero exit status 127

And the upgrade task stops.

Comment 1 Amit Ugol 2017-05-18 09:28:24 UTC

Hi,
Is this related?
https://access.redhat.com/solutions/2998171

Comment 2 Yolanda Robla 2017-05-18 13:03:52 UTC

Our base system is RHEL 7.3 . How shall we have the wrong .so file and which one is the correct?
 md5sum /usr/lib64/libnsssysinit.so
6eede6f5e3ef95e8ed45ff97a2a7aa90  /usr/lib64/libnsssysinit.so

Which other details do you need to clarify the problem?

Comment 7 Yolanda Robla 2017-06-05 12:22:35 UTC

Sorry but i don't have the system to test now, as i'm using for another purposes. I can send you that information during the week

Comment 8 Sofer Athlan-Guyot 2017-06-06 09:46:35 UTC

hi Jiri,

so as Lukas noticed this is a RHEL issue, thanks for creating the new bz.  I'm going to add 1458841 as a blocker for this one so we can track its resolution for RHOS as well.

Thanks,

Comment 9 Yolanda Robla 2017-06-20 18:27:35 UTC

So I can reproduce the problem on the controller/compute nodes, not on the undercloud.
Attaching some info:

 sudo ldd /usr/lib64/libnsssysinit.so
	linux-vdso.so.1 =>  (0x00007ffe81959000)
	libnssutil3.so => /lib64/libnssutil3.so (0x00007f140ccc9000)
	libplc4.so => /lib64/libplc4.so (0x00007f140cac4000)
	libplds4.so => /lib64/libplds4.so (0x00007f140c8bf000)
	libnspr4.so => /lib64/libnspr4.so (0x00007f140c681000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f140c465000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f140c260000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f140be9f000)
	librt.so.1 => /lib64/librt.so.1 (0x00007f140bc97000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f140d106000)

 md5sum /usr/lib64/libnspr*.so
bb04f6ae99dc60cfffaa805ebaa72709  /usr/lib64/libnspr4.so

Comment 10 Yolanda Robla 2017-06-20 18:29:04 UTC

Created attachment 1289781 [details]
yum repolist

Comment 11 Yolanda Robla 2017-06-20 18:30:18 UTC

Created attachment 1289782 [details]
yum.log

Comment 20 Yurii Prokulevych 2017-10-16 08:17:32 UTC

Update of RHOS-8 on RHEL-7.3 to RHOS-8 on RHEL-7.4 succeeded.
Verified with openstack-tripleo-heat-templates-0.8.14-30.el7ost.noarch

Comment 22 errata-xmlrpc 2017-10-25 17:00:15 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:3065