+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1613105 +++ ====================================================================== Description of problem: RHV Administration Portal fails with 404 error after updating to RHV 4.2.5 from 4.1.11. According to the setup logs, engine-setup completes successfully. ~~~ 2018-08-02 10:12:09,851-0400 INFO otopi.plugins.ovirt_engine_common.base.core.misc misc._terminate:170 Execution of setup completed successfully ~~~ Reviewing the setup logs, it appears the jb-eap-7.0-for-rhel-7-server-rpms repository was enabled. ~~~ 2018-08-02 10:10:23,913-0400 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 (0%) 2018-08-02 10:10:23,914-0400 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 2.3 k(100%) 2018-08-02 10:10:28,799-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages packages.verbose:203 Yum Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 (0%) 2018-08-02 10:10:28,801-0400 DEBUG otopi.plugins.ovirt_engine_setup.ovirt_engine_common.distro-rpm.packages packages.verbose:203 Yum Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 2.3 k(100%) 2018-08-02 10:10:36,918-0400 DEBUG otopi.plugins.ovirt_engine_setup.rhvm_setup_plugins.distro-rhel.setup_reinstallable setup_reinstallable.verbose:52 Yum: Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 (0%) 2018-08-02 10:10:36,920-0400 DEBUG otopi.plugins.ovirt_engine_setup.rhvm_setup_plugins.distro-rhel.setup_reinstallable setup_reinstallable.verbose:52 Yum: Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 2.3 k(100%) 2018-08-02 10:11:13,225-0400 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 (0%) 2018-08-02 10:11:13,227-0400 DEBUG otopi.plugins.otopi.packagers.yumpackager yumpackager.verbose:76 Yum Downloading: jb-eap-7.0-for-rhel-7-server-rpms/7Server/x86_64 2.3 k(100%) ~~~ Failure seen in the server.log file. ~~~ 2018-08-02 10:36:39,781-04 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "engine.ear")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.comp.engine.bll.Backend.env.infinispan.config.timeout-base is missing [jboss.naming.context.java.jboss.infinispan.configuration.ovirt-engine.timeout-base]"]} ... 2018-08-02 10:36:40,271-04 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report WFLYCTL0184: New missing/unsatisfied dependencies: service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.CREATE (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.JndiBindingsService (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".jndiDependencyService] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".moduleDeploymentRuntimeInformationStart, service jboss.deployment.subunit."engine.ear"."bll.jar".deploymentCompleteService, service jboss.deployment.subunit."engine.ear"."bll.jar".component.InitBackendServicesOnStartupBean.START] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.VIEW."org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler".LOCAL (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.VIEW."org.ovirt.engine.core.bll.interfaces.BackendInternal".LOCAL (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.VIEW."org.ovirt.engine.core.common.interfaces.BackendLocal".LOCAL (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.WeldInstantiator (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.WeldInterceptorBindingsService (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.WeldInstantiator] service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.ejb.non-functional-timerservice (missing) dependents: [service jboss.deployment.subunit."engine.ear"."bll.jar".component.Backend.START] ~~~ According to the documentation, jb-eap-7-for-rhel-7-server-rpms is required repository (NOTE jb-eap-7.0.. on the failure). https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/installation_guide/chap-red_hat_virtualization_manager#Enabling_the_Red_Hat_Virtualization_Manager_Repositories_standalone_install ~~~ Enable the required repositories: # subscription-manager repos --enable=rhel-7-server-rpms # subscription-manager repos --enable=rhel-7-server-supplementary-rpms # subscription-manager repos --enable=rhel-7-server-rhv-4.2-manager-rpms # subscription-manager repos --enable=rhel-7-server-rhv-4-manager-tools-rpms # subscription-manager repos --enable=rhel-7-server-ansible-2-rpms # subscription-manager repos --enable=jb-eap-7-for-rhel-7-server-rpms ~~~ engine-setup completed successfully with the incorrect jb-eap-7.0-for-rhel-7-server-rpms repository instead of the jb-eap-7-for-rhel-7-server-rpms. Version-Release number of selected component (if applicable): ovirt-engine-4.2.5.2-0.1.el7ev.noarch How reproducible: 100% Steps to Reproduce: 1. Enable the jb-eap-7.0-for-rhel-7-server-rpms repository 2. Upgrade to 4.2.5 3. Login to Admin portal fails with 404. Actual results: engine-setup completed successfully with the incorrect jb-eap-7.0-for-rhel-7-server-rpms repository instead of the jb-eap-7-for-rhel-7-server-rpms. Expected results: engine-setup should fail with the incorrect jb-eap-7.0-for-rhel-7-server-rpms repository. Additional info: (Originally by Bimal Chollera)
I got the same issue in my lab setup while upgrading the RHV-M from 4.2.3 to 4.2.5. I think it's not only because of the incorrect repo. I was having jb-eap-7-for-rhel-7-server-rpms enabled in my server. === yum repolist Loaded plugins: search-disabled-repos, subscription-manager, versionlock repo id repo name status jb-eap-7-for-rhel-7-server-rpms/7Server/x86_64 JBoss Enterprise Application Platform 7 (RHEL 7 Server) (RPMs) 1,502 rhel-7-server-ansible-2-rpms/x86_64 Red Hat Ansible Engine 2 RPMs for Red Hat Enterprise Linux 7 Server 32 rhel-7-server-rhv-4-manager-tools-rpms/x86_64 Red Hat Virtualization Manager 4 Tools (RHEL 7 Server) (RPMs) 42 rhel-7-server-rhv-4.2-manager-rpms/x86_64 Red Hat Virtualization Manager v4.2 (RHEL 7 Server) (RPMs) 411 rhel-7-server-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server (RPMs) 20,705 rhel-7-server-supplementary-rpms/7Server/x86_64 Red Hat Enterprise Linux 7 Server - Supplementary (RPMs) 267 repolist: 22,959 ==== However, after doing the engine-setup, the RHV-M portal is showing 404 with the same error in server.log. 2018-08-09 12:57:05,883-04 ERROR [org.jboss.as.logging] (Controller Boot Thread) WFLYLOG0087: Failed to process logging directory /var/log/ovirt-engine. Log files cannot be listed. I have to manually run "yum update eap7-*" to fix this. Not sure which package upgrade has fixed the issue. I think every customer who doesn't do "yum update" after engine-setup will face the same issue after upgrading to 4.2.5. I am attaching the package version list before and after the engine-setup and the setup log. (Originally by Nijin Ashok)
> > Steps to Reproduce: > 1. Enable the jb-eap-7.0-for-rhel-7-server-rpms repository > 2. Upgrade to 4.2.5 > 3. Login to Admin portal fails with 404. > > Actual results: > > engine-setup completed successfully with the incorrect > jb-eap-7.0-for-rhel-7-server-rpms repository instead of the > jb-eap-7-for-rhel-7-server-rpms. > > > Expected results: > > engine-setup should fail with the incorrect > jb-eap-7.0-for-rhel-7-server-rpms repository. > > Additional info: I really don't know where jb-eap-7.0-for-rhel-7-server-rpms channel came from, I've just checked 4.0,4.1 and 4.2 installation guides and I can see everywhere correct channel jb-eap-7-for-rhel-7-server-rpms. Bu OK, we will need to force bumping EAP versions for each RHV release, because we always test and support only latest EAP version for latest RHV version. (Originally by Martin Perina)
(In reply to nijin ashok from comment #4) > I got the same issue in my lab setup while upgrading the RHV-M from 4.2.3 to > 4.2.5. I think it's not only because of the incorrect repo. I was having > jb-eap-7-for-rhel-7-server-rpms enabled in my server. > Nijin, I think this is the same issue, I can see in package list before upgrade you also were on EAP 7.0 (eap7-wildfly-7.0.5-3.GA_redhat_2.1.ep7.el7.noarch) while you should already have EAP 7.1 (eap7-wildfly-7.1.2-1.GA_redhat_1.1.ep7.el7.noarch.rpm or newer) (Originally by Martin Perina)
4.2.5 2nd async has already been built on Friday. This not a serious bug, this is just a fail safe for customers, who don't read documentation. I don't agree with moving from 4.2.6, this is not serious enough to justify yet another async. (Originally by Martin Perina)
To verify, please check that JBoss with the lower version than 7.1.3 is blocked by spec file and brings yum package conflict by upgrading from 4.1 to 4.2 RHV (with JBoss <7.1.3 (7.0))
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-2018:2541
sync2jira