-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
None
-
False
-
-
-
-
-
-
-
Related to JBEAP-26274 - so need to unzip the zip first
Side note, it probably should default to the server installation is in the directory relative to where the jboss-eap-installation-manager.sh is executed:
./jboss-eap-8.0/bin/jboss-eap-installation-manager.sh update perform --offline --repositories=patch::file:./zips/jbeap-123-dir/maven-repository/ ERROR: Path `/home/quickcluster/.` does not contain a server installation provisioned by the jboss-eap-installation-manager. Maybe you forgot to specify path to the installation (--dir)?
Use this:
cd jboss-eap-8.0 ./bin/jboss-eap-installation-manager.sh update perform --offline --repositories=patch::file:../zips/jbeap-123-dir/maven-repository/ -y Updating server: /home/quickcluster/jboss-eap-8.0/.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 Feature-packs resolved. Packages installed. Downloaded artifacts. JBoss modules installed. Configurations generated. JBoss examples installed. Build update complete! Applying updates Update complete! Operation completed in 24.90 seconds.
Jars have been updated:
./modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-5.0.5.Final-redhat-00001-jbeap-123.jar ./modules/system/layers/base/org/jboss/remoting/main/jboss-remoting-5.0.27.Final-redhat-00001-jbeap-123.jar
Try to revert:
./bin/jboss-eap-installation-manager.sh history [819fc02d] 2023-12-13T15:06:23Z - 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]
It wants a maven repo:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d
Reverting server /home/quickcluster/jboss-eap-8.0/. to state 819fc02d
ERROR: Unable to resolve required channel metadata:
* org.jboss.eap.channels:eap-8.0:manifest:yaml
Attempted repositories:
*mrrc::https://maven.repository.redhat.com/ga/
It needs an ID for the temp repo:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d --repositories=../zips/jboss-eap-8.0.0.GA-CR1-maven-repository.zip ERROR: Repository definition [../zips/jboss-eap-8.0.0.GA-CR1-maven-repository.zip] is invalid. The definition format should be [id::url]
JBEAP-26274 it needs it unzipped:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d --repositories=file::file://../zips/jboss-eap-8.0.0.GA-CR1-maven-repository.zip Reverting server /home/quickcluster/jboss-eap-8.0/. to state 819fc02d ERROR: Unable to resolve required channel metadata: * org.jboss.eap.channels:eap-8.0:manifest:yaml Attempted repositories: *file::file://../zips/jboss-eap-8.0.0.GA-CR1-maven-repository.zip
It says it cannot find the manifest though it is in there:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d --repositories=file::file://../zips/jboss-eap-8.0.0.GA-maven-repository/maven-repository/ Reverting server /home/quickcluster/jboss-eap-8.0/. to state 819fc02dERROR: Unable to resolve required channel metadata: * org.jboss.eap.channels:eap-8.0:manifest:yaml Attempted repositories: *file::file://../zips/jboss-eap-8.0.0.GA-maven-repository/maven-repository/ ../zips/jboss-eap-8.0.0.GA-maven-repository/maven-repository/org/jboss/eap/channels/eap-8.0/1.0.1.GA-redhat-00001/eap-8.0-1.0.1.GA-redhat-00001-manifest.yaml
Try with the initial repo and the jbeap-123 repo:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d --repositories=file::file://../zips/jboss-eap-8.0.0.GA-maven-repository/maven-repository/,patch::file://../zips/jbeap-123-dir/maven-repository/ Reverting server /home/quickcluster/jboss-eap-8.0/. to state 819fc02d ERROR: Unable to resolve required channel metadata: * org.jboss.eap.channels:eap-8.0:manifest:yaml Attempted repositories: *patch::file://../zips/jbeap-123-dir/maven-repository/ *file::file://../zips/jboss-eap-8.0.0.GA-maven-repository/maven-repository/
Try moving the directories to see if it is a relative path issue:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d --repositories=file::file://8.0-maven-repository Reverting server /home/quickcluster/jboss-eap-8.0/. to state 819fc02d Feature-packs resolved. Packages installed. Downloading artifacts ERROR: Unable to resolve artifacts: * org.jboss:jboss-ejb-client:jar:5.0.5.Final-redhat-00001-jbeap-123 [missing] * org.jboss.remoting:jboss-remoting:jar:5.0.27.Final-redhat-00001-jbeap-123 [missing] Attempted repositories: *file::file://8.0-maven-repository
It seems it is related to the relative path:
./bin/jboss-eap-installation-manager.sh revert perform --revision=819fc02d --repositories=file::file://8.0-maven-repository,patch::file://jbeap-123-maven-repository
Reverting server /home/quickcluster/jboss-eap-8.0/. to state 819fc02d
Feature-packs resolved.
Packages installed.
Downloaded artifacts.
JBoss modules installed.
Configurations generated.
But the jars are not reverted:
find modules/ -name \*jbeap\*.jar modules/system/layers/base/org/jboss/ejb-client/main/jboss-ejb-client-5.0.5.Final-redhat-00001-jbeap-123.jar modules/system/layers/base/org/jboss/remoting/main/jboss-remoting-5.0.27.Final-redhat-00001-jbeap-123.jar
./bin/jboss-eap-installation-manager.sh revert perform --revision=ccf48821 --repositories=patch::file://jbeap-123-maven-repository,file::file:/8.0-maven-repository Reverting server /home/quickcluster/jboss-eap-8.0/. to state ccf48821 Feature-packs resolved. Packages installed. Downloading artifacts ERROR: Unable to resolve artifacts: * org.jboss:jboss-ejb-client:jar:5.0.5.Final-redhat-00001 [missing] * org.jboss.remoting:jboss-remoting:jar:5.0.27.Final-redhat-00001 [missing] Attempted repositories: *file::file:/8.0-maven-repository *patch::file://jbeap-123-maven-repository
Finally got it to revert:
./bin/jboss-eap-installation-manager.sh revert perform --revision=ccf48821 --repositories=file::file://8.0-maven-repository
Findings:
- revert revision - is confusing because it is not revert revision, it is revert to-revision
- If one tries to revert revision (where you are telling it to revert what you just did), you can get it to do something where it shows in the history it did something and you get in to some weird state where it will then not actually revert back to the original, so we should not allow a revert to current state, ie there is nothing to do , yet we are doing something.
- using relative path in the --repositories looks to have issues
JBEAP-26274- it does not handle zip file- It is unclear what the id::repo is needed for since it is a temporary repository and I do not see the id being stored anywhere (which makes sense as it is not intended to be kept around).
- is related to
-
JBEAP-26307 Better naming for the revert command revision parameter
-
- New
-
-
-
- New
-
-
-
- New
-
- relates to
-
-
- Closed
-
