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

(7.3.z) HAL-1679 - Cannot undeploy from Server Groups

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.3.2.CR1, 7.3.2.GA
    • 7.3.0.GA
    • Web Console
    • None
    • +
    • Workaround Exists
    • Hide

      Undeploy the desired deployment using the Browse By: Content Repository option.

      Show
      Undeploy the desired deployment using the Browse By: Content Repository option.
    • Hide

      1. Start the server in domain mode.
      2. Deploy a deployment to main server group
      3. Navigate to the deployments page and "Browse By: Server Groups"
      4. Click "Undeploy" on the newly created deployment
      5. Observe

      Show
      1. Start the server in domain mode. 2. Deploy a deployment to main server group 3. Navigate to the deployments page and "Browse By: Server Groups" 4. Click "Undeploy" on the newly created deployment 5. Observe

    Description

      When running in domain mode and trying to undeploy from the "Browse By: Server Groups" column, the deployment is not being undeployed. User is encountered with an alert saying: 

      {"domain-failure-description" => "WFLYCTL0216: Management resource '[(\"deployment\" => \"main-server-group\")]' not found"}

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. HAL-1679 Cannot undeploy from Server Groups

          • 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.
          • Resolved
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17892 [GSS](7.3.z) RBAC: Deployment button not available for server group scoped role.

          • 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.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-19134 (7.3.z) Upgrade HAL from 3.2.8.Final-redhat-00001 to 3.2.9.Final

          • 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.
          • Closed
          links to

          Web Link KCS

          Activity

            People

              chaowan@redhat.com Chao Wang
              rhn-engineering-spriadka Simon Priadka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: