Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10720

not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • 7.1.0.ER1
    • 7.1.0.DR17
    • Management
    • None
    • Regression
    • Hide

      Setup mixed domain, I used EAP 7.1.0.DR17 master and EAP 6.3.0.GA slave, used default profile copied from EAP6 and renamed to eap6-default
      follow instructions in documentation

      1. start master
        jboss-eap-7.1/bin/domain.sh --host-config=host-master.xml
      2. start slave - one server in group eap6-main-server-group
        jboss-eap-6.3/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999

      connect to DC with CLI

      1. deploy war
        deploy ~/Downloads/simple-servlet.war --server-groups=eap6-main-server-group
      2. add deployment overlay
        deployment-overlay add --name=overlay-test --content=WEB-INF/web.xml=/tmp/web.xml --server-groups=eap6-main-server-group --deployments=simple-servlet.war
      3. redeploy affected (optional, there is the same error without redeploy)
        deployment-overlay redeploy-affected --name=overlay-test
      4. try to remove deployment-overlay
        deployment-overlay remove --name=overlay-test
      Show
      Setup mixed domain, I used EAP 7.1.0.DR17 master and EAP 6.3.0.GA slave, used default profile copied from EAP6 and renamed to eap6-default follow instructions in documentation start master jboss-eap-7.1/bin/domain.sh --host-config=host-master.xml start slave - one server in group eap6-main-server-group jboss-eap-6.3/bin/domain.sh --host-config=host-slave.xml -Djboss.domain.master.address=127.0.0.1 -Djboss.management.native.port=19999 connect to DC with CLI deploy war deploy ~/Downloads/simple-servlet.war --server-groups=eap6-main-server-group add deployment overlay deployment-overlay add --name=overlay-test --content=WEB-INF/web.xml=/tmp/web.xml --server-groups=eap6-main-server-group --deployments=simple-servlet.war redeploy affected (optional, there is the same error without redeploy) deployment-overlay redeploy-affected --name=overlay-test try to remove deployment-overlay deployment-overlay remove --name=overlay-test

    Description

      It's not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older. The error is:

      {"WFLYDC0074: Operation failed or was rolled back on all servers. Server failures:" => {"server-group" => {"eap6-server-group" => {"host" => {"msimka-t450.brq.redhat.com" => {"server-one" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014762: Removing services has lead to unsatisfied dependencies:
Service jboss.deploymentOverlayIndexService.deploymentOverlayService.overlay-test was depended upon by service jboss.deploymentOverlayIndexService.deploymentOverlayService.contentService.overlay-test.\"WEB-INF/web.xml\", service jboss.deploymentOverlayIndexService.deploymentOverlayLinkService.overlay-test.\"simple-servlet.war\""}}}}}}}}

      It works when slave is EAP 6.4.0.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-2899 not possible to remove deployment-overlay in mixed domain when slave host is EAP 6.3. or older

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11137 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta26

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              msimka@redhat.com Martin Simka
              Martin Simka Martin Simka
              Martin Simka Martin Simka
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: