[jboss-jira] [JBoss JIRA] (WFLY-13390) :migrate operation on legacy messaging subsystem fails with 7.4.0.CD19 (WF19)

[Emmanuel Hugonnet (Jira)]

     [ https://issues.redhat.com/browse/WFLY-13390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Hugonnet moved JBEAP-19278 to WFLY-13390:
--------------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-13390  (was: JBEAP-19278)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JMS
                       Migration
                           (was: JMS)
                           (was: Migration)
    Affects Version/s: 19.0.0.Final
                           (was: 7.4.0.CD19)


> :migrate operation on legacy messaging subsystem fails with 7.4.0.CD19 (WF19)
> -----------------------------------------------------------------------------
>
>                 Key: WFLY-13390
>                 URL: https://issues.redhat.com/browse/WFLY-13390
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS, Migration
>    Affects Versions: 19.0.0.Final
>            Reporter: Emmanuel Hugonnet
>            Assignee: Emmanuel Hugonnet
>            Priority: Critical
>
> CD19 (WF19) introduces several failures in tests running the {{:migrate}} operation on legacy configuration files.
> See [^standalone-full-ha-migrate.xml.original] for configuration file which is subject of migration.
> {code}
> ...
>         <broadcast-groups>
>             <broadcast-group name="groupS">
>                 <socket-binding>messaging-group</socket-binding>
>             </broadcast-group>
> ...
>         </broadcast-groups>
> ...
> {code}
> See [^standalone-full-ha-migrate.xml.migrated] for configuration file after migration using 7.3.0 EAP.
> {code}
> ...
>         <broadcast-group socket-binding="messaging-group" name="groupS"/>
> ...
> {code}
> Migration outcome with 7.4.0.CD19.CR1 (WF19)
> {code}
> {
>     "outcome" : "failed",
>     "result" : {
>         "migration-warnings" : [],
>         "migration-error" : {
>             "operation" : {
>                 "socket-binding" : "messaging-group",
>                 "connectors" : null,
>                 "operation" : "add",
>                 "address" : [
>                     {
>                         "subsystem" : "messaging-activemq"
>                     },
>                     {
>                         "server" : "default"
>                     },
>                     {
>                         "broadcast-group" : "groupS"
>                     }
>                 ],
>                 "operation-headers" : {
>                     "caller-type" : "user",
>                     "access-mechanism" : "NATIVE"
>                 }
>             },
>             "result" : {
>                 "outcome" : "failed",
>                 "failure-description" : "WFLYCTL0155: 'connectors' may not be null",
>                 "rolled-back" : true
>             }
>         }
>     },
>     "failure-description" : "WFLYMSG0081: Migration failed, see results for more details.",
>     "rolled-back" : true
> }
> {code}
> Unfortunately I do not have a deeper knowledge of messaging subsystem to be able to tell what should be the best outcome of migration here.
> Could be related to https://issues.redhat.com/browse/WFLY-10339 Broadcast/discovery-group resources have ambiguous requirement specs
> *Steps to reproduce*
> {code}
> $ cp standalone-full-ha-migrate.xml.original jboss-eap-7.4/standalone/configuration/standalone.xml
> $ ./jboss-eap-7.4/bin/jboss-cli.sh 
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server --admin-only=true 
> [standalone at embedded /] /subsystem=messaging:migrate
> {
>     "outcome" => "failed",
> ...
> {code}



--
This message was sent by Atlassian Jira
(v7.13.8#713008)