Uploaded image for project: 'HAL'
  1. HAL
  2. HAL-1180

Failed to create security context for subsystem=naming/service=*

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 2.9.0.Alpha2
    • 2.9.0.Alpha1
    • None
    • None
    • Hide

      1. Configuration tab -> Subsystems -> Naming - View
      2. Select service in the left orientation pane
      3. Select remote-naming in the Singleton Child Resources table
      4. Click Remove button
      5. Click service -> * in the left orientation pane

      Show
      1. Configuration tab -> Subsystems -> Naming - View 2. Select service in the left orientation pane 3. Select remote-naming in the Singleton Child Resources table 4. Click Remove button 5. Click service -> * in the left orientation pane

    Description

      After removing the remote-naming service in naming subsystem, a service -> * will appear in the left orientation pane. After clicking it, the following error message is produced:

      Failed to create security context for subsystem=naming/service=*

Unexpected response format at address: subsystem=naming/service=*

      Is there any point to showing the service -> * in the left orientation pane? It seems rather pointless and confusing at this point.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4953 Failed to create security context for subsystem=naming/service=*

          • 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 duplicated by

          Bug - A problem that impairs or prevents the functions of the product. HAL-647 Singleton resource should not display wildcard in model browser navigation

          • 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

              mpetrov@redhat.com Michal Petrov
              mpetrov@redhat.com Michal Petrov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: