[
https://issues.redhat.com/browse/WFWIP-359?page=com.atlassian.jira.plugin...
]
Oleksiy Lubyanskyy commented on WFWIP-359:
------------------------------------------
It's been awhile since I looked into that. Sound like we need to be able to detect the
layer id and the patch stream id for that layer and fail in case there is an attempt to
mix different streams from the same layer in the same installation. E.g. instead of
`$JBOSS_HOME/.installation/<patch-stream-name>.conf` we could have had
`$JBOSS_HOME/.installation/<layer-id>/<patch-stream-id>.conf`. Not yet sure
how difficult it would be to implement that.
A possible quick workaround could be to introduce some basic content that is incompatible
between xp1 and xp2, which would make patching fail in case a patch from the wrong stream
is applied.
Server can get to state, where XP2 manager thinks both XP1 and XP2
streams are active
-------------------------------------------------------------------------------------
Key: WFWIP-359
URL:
https://issues.redhat.com/browse/WFWIP-359
Project: WildFly WIP
Issue Type: Bug
Reporter: Martin Svehla
Assignee: Kabir Khan
Priority: Major
If I run setup first, manager activates XP2 stream. However, if I then use patch-apply to
apply XP1 patch, manager lets this action to happen and then thinks both streams are
active.
{code}
$ java -jar manager.jar status --jboss-home=jboss-eap-73
Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
The JBoss EAP XP patch stream is enabled. You may apply patches both from the JBoss EAP
and the JBoss EAP XP patch streams. While enabled the following support policy applies:
[snip]
You are currently on JBoss EAP XP 2.
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'
Available commands in this state are: [remove]
{code}
{code}
$ java -jar manager.jar patch-apply --jboss-home=jboss-eap-7.3
--patch=jboss-eap-xp-1.0.2.GA-redhat-20200911-patch.zip
{code}
{code}
$ java -jar manager.jar status --jboss-home=jboss-eap-7.3
Starting JBoss EAP XP manager (2.0.0.Final-redhat-20200911).
The JBoss EAP XP patch stream setup in the JBoss EAP server seems broken.
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.2.CP'
Available commands in this state are: [remove]
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)