Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-5852

CLI autocomplete suggests non-existent subsystems

    XMLWordPrintable

Details

    Description

      This bug occurs with an .ear file deployment that contains .war subdeployments.

      When trying to "ls -l" the subsystems in the .ear deployment, the CLI's autocomplete is suggesting subsystems under the .ear deployment that don't exist and should only be under the .war subdeployments. Doing an actual "ls -l" command on the non-existent subsystems of the .ear file gives a "not found" error, as it should:

      [standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subsystem=<TAB>
batch-jberet  datasources  ejb3  jaxrs  jpa  logging  resource-adapters  undertow  webservices

      [standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subsystem=undertow
{"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "WFLYCTL0216: Management resource '[
    (\"deployment\" => \"EnterpriseHelloWorld.ear\"),
    (\"subsystem\" => \"undertow\")
]' not found"}}

      When it comes to the subdeployments, everything works as it should:

      [standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subdeployment=HelloWorld<TAB>
HelloWorldFirst.war  HelloWorldSecond.war 

      [standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subdeployment=HelloWorldFirst.war/subsystem=<TAB>
batch-jberet  datasources  ejb3  jaxrs  jpa  logging  resource-adapters  undertow  webservices 

      [standalone@localhost:9990 /] ls -l /deployment=EnterpriseHelloWorld.ear/subdeployment=HelloWorldFirst.war/subsystem=undertow
ATTRIBUTE              VALUE            TYPE   
active-sessions        0                INT    
context-root           /HelloWorldFirst STRING 
expired-sessions       0                INT    
highest-session-count  0                INT    
max-active-sessions    -1               INT    
rejected-sessions      0                INT    
server                 default-server   STRING 
session-avg-alive-time 0                INT    
session-max-alive-time 0                INT    
sessions-created       0                INT    
virtual-host           default-host     STRING

      Attachments

        Issue Links

          clones

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBEAP-19896 [GSS](7.4.z) WFCORE-5852 - CLI autocomplete suggests non-existent subsystems

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Verified
          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. WFLY-16158 Deployment submodel should be runtime

          • 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

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-5853 Deployment SubModel for logging should be runtime only

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFCORE-4183 ReadResourceHandler returns runtime values stored in the DMR model even if include-runtime=false

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. WFCORE-3432 Correct ManagementResourceRegistration runtime-only metadata

          • 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

          Activity

            People

              ehugonne1@redhat.com Emmanuel Hugonnet
              ehugonne1@redhat.com Emmanuel Hugonnet
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: