Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1469706

Summary:	Leftover /opt/rh/rh-nodejs8/root/usr/share/doc/rh-nodejs8-nodejs/npm after uninstallation
Product:	Red Hat Software Collections	Reporter:	Miroslav Hradílek <mhradile>
Component:	rh-nodejs8	Assignee:	Zuzana Svetlikova <zsvetlik>
Status:	CLOSED ERRATA	QA Contact:	Mirek Długosz <mzalewsk>
Severity:	low	Docs Contact:
Priority:	low
Version:	rh-nodejs8	CC:	akhaitov, jorton, mzalewsk
Target Milestone:	alpha
Target Release:	3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-24 09:56:00 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:

Description Miroslav Hradílek 2017-07-11 16:38:20 UTC

Description of problem:
When I Install rh-nodejs8-nodejs-docs the directory is created in
/opt/rh/rh-nodejs8/root/usr/share/doc/rh-nodejs8-nodejs/npm

but it does not belong to the docs package and therefore is not removed after package removal.

Version-Release number of selected component (if applicable):
Unreleased rh-nodejs8-nodejs-docs-8.1.2-7.el7.noarch.rpm

Comment 3 Mirek Długosz 2017-09-21 07:01:10 UTC

Issue at hand has been fixed in the meantime.

Test was still failing because files owned by some packages (rh-nodejs8-nodejs-bson, rh-nodejs8-nodejs-mongodb, rh-nodejs8-nodejs-mongodb-core, rh-nodejs8-nodejs-require_optional and rh-nodejs8-nodejs-resolve-from) were not treated as belonging to rh-nodejs8 collection. That issue was resolved as well. Test passes on x86_64 and s390x. See Beaker job 2058021.

However, it still fails on aarch64 and ppc64le. The reason is that rh-nodejs8-runtime package does not own directory /opt/rh/rh-nodejs8/root/usr/lib64/ on these architectures. New bugilla issue was created to track progress on that problem: Bug #1493894.

Setting as VERIFIED, since there is hardly any more work to do in this ticket.

Comment 5 errata-xmlrpc 2017-10-24 09:56:00 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/RHEA-2017:3029