[ https://issues.redhat.com/browse/WFWIP-359?page=com.atlassian.jira.plugin... ] Kabir Khan edited comment on WFWIP-359 at 9/24/20 10:45 AM: ------------------------------------------------------------ Enhanced status message: {code:java} $java -jar target/jboss-eap-xp-patch-stream-manager-2.0.0.Final-SNAPSHOT.jar status --jboss-home=../xp-patching/jboss-eap-7.3 Starting JBoss EAP XP manager (2.0.0.Final-SNAPSHOT). The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken. You have more than one JBoss EAP XP patch stream set up in the JBoss EAP server. You may end up in this situation if you installed the latest XP patch stream and applied patches from an older JBoss EAP XP patch stream. To recover from this you need to run the 'remove' command, run 'setup' again and make sure you only install JBoss EAP XP patch stream patches from the current JBoss EAP XP patch stream. Enabled patch streams and their cumulative patch ids: - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base' - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base' - Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.0.CP' Available commands in this state are: [remove] {code}   [~amehendal] This might be of interest to you. Essentially the issue is that we cannot stop the user from enabling the XP 2.0 patch stream and then applying XP 1.0 patches. Once they apply the XP 1.0 patch, that is also available as a patch stream which makes the installation broken. I will try to change the XP manager to check the streams from the patch-apply command to avoid this there, but they may still get into this situation by applying patches from the CLI.   was (Author: kabirkhan): Enhanced status message: {code:java} $java -jar target/jboss-eap-xp-patch-stream-manager-2.0.0.Final-SNAPSHOT.jar status --jboss-home=../xp-patching/jboss-eap-7.3 Starting JBoss EAP XP manager (2.0.0.Final-SNAPSHOT). The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken. You have more than one JBoss EAP XP patch stream set up in the JBoss EAP server. You may end up in this situation if you installed the latest XP patch stream and applied patches from an older JBoss EAP XP patch stream. To recover from this you need to run the 'remove' command, run 'setup' again and make sure you only install JBoss EAP XP patch stream patches from the current JBoss EAP XP patch stream. Enabled patch streams and their cumulative patch ids: - Patch stream: 'JBoss EAP'; Cumulative patch id: 'base' - Patch stream: 'jboss-eap-xp-2.0'; Cumulative patch id: 'base' - Patch stream: 'jboss-eap-xp-1.0'; Cumulative patch id: 'jboss-eap-xp-1.0.0.CP' Available commands in this state are: [remove] {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)