Major Description
When using 'group' way of update/upgrade of EAP between version 7.1 and 7.2:
yum groupupdate jboss-eap7 or yum update @jboss-eap7
the dependencies are not resolved correctly. Only base group packages are marked to be updated - 'eap7-artemis-native-wildfly' and 'eap7-wildfly', nothing else:
repolist
# yum repolist Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. repo id repo name status jb-eap-7.1-for-rhel-7-server-debug-rpms jb-eap-7.1-for-rhel-7-server-debug-rpms/x86_64 3 jb-eap-7.1-for-rhel-7-server-rpms jb-eap-7.1-for-rhel-7-server-rpms/x86_64 2,011 jb-eap-7.1-for-rhel-7-server-source-rpms jb-eap-7.1-for-rhel-7-server-source-rpms/x86_64 737 jb-eap-7.2-for-rhel-7-server-rpms jb-eap-7.2-for-rhel-7-server-rpms/x86_64 423 rhel-7-server-rpms rhel-7-server-rpms/7Server/x86_64 23,446 repolist: 26,620
grouplist
# yum grouplist -v Not loading "rhnplugin" plugin, as it is disabled Loading "product-id" plugin Loading "search-disabled-repos" plugin Loading "subscription-manager" plugin Updating Subscription Management repositories. Unable to read consumer identity This system is not registered with an entitlement server. You can use subscription-manager to register. Config time: 0.114 Yum version: 3.4.3 Setting up Package Sacks pkgsack time: 0.018 group time: 0.080 Available Environment Groups: Minimal Install (minimal) Infrastructure Server (infrastructure-server-environment) File and Print Server (file-print-server-environment) Basic Web Server (web-server-environment) Virtualization Host (virtualization-host-environment) Server with GUI (graphical-server-environment) Installed Groups: JBoss EAP 7 (jboss-eap7) jbcs-httpd24 (jbcs-httpd24) Available Groups: Compatibility Libraries (compat-libraries) Console Internet Tools (console-internet) Development Tools (development) Graphical Administration Tools (graphical-admin-tools) Legacy UNIX Compatibility (legacy-unix) Scientific Support (scientific) Security Tools (security-tools) Smart Card Support (smart-card) System Administration Tools (system-admin-tools) System Management (system-management) Done
groupupdate
# yum groupupdate jboss-eap7 Loaded plugins: product-id, search-disabled-repos, subscription-manager This system is not registered with an entitlement server. You can use subscription-manager to register. Resolving Dependencies --> Running transaction check ---> Package eap7-artemis-native-wildfly.x86_64 0:1.5.0-5.redhat_1.ep7.el7 will be updated ---> Package eap7-artemis-native-wildfly.x86_64 0:2.6.3-10.redhat_00014.el7eap will be an update ---> Package eap7-wildfly.noarch 0:7.1.6-4.GA_redhat_00002.1.ep7.el7 will be updated ---> Package eap7-wildfly.noarch 0:7.2.0-31.GA_redhat_00005.1.el7eap will be an update --> Finished Dependency Resolution Dependencies Resolved =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Updating: eap7-artemis-native-wildfly x86_64 2.6.3-10.redhat_00014.el7eap jb-eap-7.2-for-rhel-7-server-rpms 14 k eap7-wildfly noarch 7.2.0-31.GA_redhat_00005.1.el7eap jb-eap-7.2-for-rhel-7-server-rpms 1.2 M Transaction Summary =================================================================================================================================================================================================================== Upgrade 2 Packages Total download size: 1.2 M Is this ok [y/d/N]:
Although, when I perform simple 'yum update', I can see that all relevant EAP7.2 packages are selected to be updated:
- Install 8 Packages (+74 Dependent packages)
- Upgrade 308 Packages
At the moment, we don't have specified exact way, how customer should update between EAP versions in our documentation but I believe we should unify behaviour of these two approaches (simple update vs groupupdate).
