Obsolete packages left behind when upgrading rpm packages from JBoss EAP 7.3.6 to 7.4
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7
- rpm
Issue
When upgrading JBoss EAP 7.3.6 to 7.4.8 as the latest update, the following obsolete packages left in the system. The following two packages are not installed if we install a new JBoss EAP 7.4.8.
eap7-hibernate-entitymanager-5.3.28-1.Final_redhat_00001.1.el8eap.noarch
eap7-netty-all-4.1.77-3.Final_redhat_00001.1.el8eap.noarch
Resolution
It is harmless if left. If necessary, these packages can be removed safely by the following commands:
# yum remove eap7-hibernate-entitymanager-5.3.28-1.Final_redhat_00001.1.el8eap.noarch eap7-netty-all-4.1.77-3.Final_redhat_00001.1.el8eap.noarch
Failed to set locale, defaulting to C.UTF-8
Updating Subscription Management repositories.
Dependencies resolved.
=============================================================================================================================================================================
Package Architecture Version Repository Size
=============================================================================================================================================================================
Removing:
eap7-hibernate-entitymanager noarch 5.3.28-1.Final_redhat_00001.1.el8eap @jb-eap-7.4-for-rhel-8-x86_64-rpms 1.4 k
eap7-netty-all noarch 4.1.77-3.Final_redhat_00001.1.el8eap @jb-eap-7.4-for-rhel-8-x86_64-rpms 28 k
Transaction Summary
=============================================================================================================================================================================
Remove 2 Packages
Freed space: 30 k
Is this ok [y/N]:
For eap7-netty-all package, we are working on This content is not included.JBEAP-24499 to be automatically removed on upgrade, and it will be fixed in the future release.
Root Cause
Until JBoss EAP 7.3, eap7-hibernate-entitymanager was a dependent eap7-hibernate-envers package.
# rpm -qR eap7-hibernate-envers-5.3.20-1.Final_redhat_00001.1.el8eap.noarch
eap7-hibernate-core = 0:5.3.20-1.Final_redhat_00001.1.el8eap
eap7-hibernate-entitymanager = 0:5.3.20-1.Final_redhat_00001.1.el8eap <<<===
eap7-runtime
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
Since JBoss EAP 7.4.0, eap7-hibernate-envers does not dependent eap7-hibernate-entitymanager, we can safely remove eap7-hibernate-entitymanager, which is not referenced by any packages.
# rpm -qR eap7-hibernate-envers-5.3.28-1.Final_redhat_00001.1.el8eap.noarch
eap7-runtime
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(PayloadIsXz) <= 5.2-1
For netty-all package, this package was split into several packages such as eap7-netty-codec, eap7-netty-codec and eap7-netty-tcnative in JBoss EAP 7.4.5 and netty-all is not referenced as a JBoss EAP module.
eap7-wildfly package has eap7-netty-all = 0:4.1.63 as an obsolete in the spec file. eap7-netty-all-4.1.63 is included in JBoss EAP 7.3.10. But if we upgrade from JBoss EAP 7.3.6, netty-all package version of JBoss EAP 7.3.6 is eap7-netty-all-4.1.48-1.Final_redhat_00001.1.el8eap.noarch. Hence netty-all package is not automatically removed when upgrading to JBoss EAP 7.4.8.
# rpm -q --obsoletes eap7-wildfly-7.4.8-4.GA_redhat_00002.1.el8eap.noarch | grep eap7-netty-all
eap7-netty-all = 0:4.1.63
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.