Apply an update using the jboss-cli.sh installer command connected to an EAP
jboss-cli.sh -c installer update --confirm --maven-repo-files=./jbeap-123.zip Updates found: org.jboss:jboss-ejb-client 5.0.5.Final-redhat-00001 ==> 5.0.5.Final-redhat-00001-jbeap-123 org.jboss.remoting:jboss-remoting 5.0.27.Final-redhat-00001 ==> 5.0.27.Final-redhat-00001-jbeap-123 The new installation is being prepared ... The candidate server has been generated. To apply it, restart the server with 'shutdown --perform-installation' command. shutdown --perform-installation
Check the history, which shows it has been updated
installer history [c2a28f55] 2023-12-13T14:38:44Z - update [org.jboss.eap.channels:eap-8.0::1.0.1.GA-redhat-00002-01-jbeap-123] [ccf48821] 2023-09-22T13:39:32Z - install [org.jboss.eap.channels:eap-8.0::1.0.1.GA-redhat-00001]
The jar files
jboss-eap-8.0/modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-5.0.5.Final-redhat-00001-jbeap-123.jar jboss-eap-8.0/modules/system/layers/base/org/jboss/remoting/main/jboss-remoting-5.0.27.Final-redhat-00001-jbeap-123.jar
Try to revert:
installer revert --revision=c2a28f55 WFLYCTL0158: Operation handler failed: java.lang.RuntimeException: org.wildfly.prospero.api.exceptions.UnresolvedChannelMetadataException: PRSP000228: Unable to resolve artifact
Side note, the CLI message is too generic, the user would have to be going to the remote server and reading the log to figure out what this error means.
Caused by: org.wildfly.channel.ArtifactTransferException: Unable to resolve the latest version of channel metadata org.jboss.eap.channels:eap-8.0
installer revert --revision=c2a28f55 --repositories=jboss-eap-8.0.0.GA-CR1-maven-repository.zip
The new installation is being prepared ...
Invalid Repository URL. Valid values are either URLs or ID::URL
installer revert --revision=c2a28f55 --repositories=file::file://jboss-eap-8.0.0.GA-CR1-maven-repository.zip The new installation is being prepared ... WFLYCTL0158: Operation handler failed: java.lang.RuntimeException: org.wildfly.prospero.api.exceptions.UnresolvedChannelMetadataException: PRSP000228: Unable to resolve artifact
This revert will run:
installer revert --revision=c2a28f55 --maven-repo-files=./jboss-eap-8.0.0.GA-CR1-maven-repository.zip The new installation is being prepared ... The candidate server has been generated. To apply it, restart the server with 'shutdown --perform-installation' command. shutdown --perform-installation
The jars did not revert:
find jboss-eap-8.0/ -name jboss-remoting\*.jar jboss-eap-8.0/modules/system/layers/base/org/jboss/remoting/main/jboss-remoting-5.0.27.Final-redhat-00001-jbeap-123.jar find jboss-eap-8.0/ -name jboss-ejb-client\*.jar jboss-eap-8.0/modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-5.0.5.Final-redhat-00001-jbeap-123.jar
It looks like the issue is the same as JBEAP-26277, it actually is revert to , so we should not be trying to revert to the current revision as that is a no-op yet we are doing something
installer revert --revision=ccf48821 --maven-repo-files=./jboss-eap-8.0.0.GA-CR1-maven-repository.zip
- is related to
-
JBEAP-26132 Revert of update and one-off patch doesn't work offline through web-console
- New
-
JBEAP-26277 jboss-eap-installation-manager.sh issues trying to revert
- New
- relates to
-
JBEAP-26307 Better naming for the revert command revision parameter
- New
-
JBEAP-26290 (8.0.z) Reverting an update doesn't use the cache.
- Closed