Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-25046

Can't find CDK for registry discovery when 2 connections are defined for CDK

    XMLWordPrintable

Details

    • devex #138 September 2017

    Description

      EXEC: define an Openshift connection for CDK/admin
      EXEC: define an Openshift connection for CDK/developer
      EXEC: define a CDK3 server
      EXEC: start the CDK 3 server
      ASSERT: the CDK/admin OS3 connection is updated (registry not empty)
      ASSERT: the CDK/developer OS3 connection is not updated (registry empty)
      EXEC: on the CDK/developer OS3 connection, click the DIscover buttoon
      ASSERT: the registry URL is updated, not the error dialog is displayed

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-25121 Connection wizard: Image Registry URL is not decorated when not valid (and validation seems weird)

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-25120 CDK server adapter, connection: update registry url in all connections that exist (not just 1)

          • 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.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users JBIDE-24491 CDK Server adapter: allow users to look up the address of the docker registry

          • 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

          Feature Request - Feature requests from customers and/or users JBIDE-25093 IT: create tests for the Docker discovery feature

          • 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. JBIDE-25049 Connection wizard: Cannot "Discover" "Image Registry URL" as if there was no minishift nor adapter (even though both are started)

          • 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

          Activity

            People

              rob.stryker Rob Stryker (Inactive)
              jmaury@redhat.com Jeff MAURY
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: