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

Starting of CDK 3 Server Adapter with Minishift Home that differs from ~/.minishift prevents OS tooling to create proper connection and links it to default project

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.5.1.AM1
    • 4.5.0.Final
    • cdk, openshift
    • None
    • Hide

      Case 1
      1. EXEC: Have downloaded stable CDK (latest-weekly 3.1.0-1) and called 'minishift setup-cdk' -> ~/.minishift
      2. EXEC: Run IDE, add CDK3 server adapter (via runtime or manually)
      3. EXEC: Open CDK3 Server adapter and change Minishift Home to anything else than ~/.minishift
      4. ASSERT: CDK3 is started, OS connection created (developer https://192.... and My-Project is attached)
      FAILS: OS connection created has default value: openshift-dev https://192.168... and no project is connected)

      Case 2
      1. EXEC: Have downloaded stable CDK (latest-weekly 3.1.0-1), set MINISHIFT_HOME (~/minishift_home) and called 'minishift setup-cdk' -> ~/minishift_home
      2. EXEC: Run IDE, add CDK3 server adapter (via runtime or manually)
      3. ASSERT: Open CDK3 Server adapter and check presence of correct MINISHIFT_HOME path
      4. ASSERT: CDK3 is started, OS connection created (developer https://192.... and My-Project is attached)
      FAILS: OS connection created has default value: openshift-dev https://192.168... and no project is connected)

      Show
      Case 1 1. EXEC: Have downloaded stable CDK (latest-weekly 3.1.0-1) and called 'minishift setup-cdk' -> ~/.minishift 2. EXEC: Run IDE, add CDK3 server adapter (via runtime or manually) 3. EXEC: Open CDK3 Server adapter and change Minishift Home to anything else than ~/.minishift 4. ASSERT: CDK3 is started, OS connection created (developer https://192 .... and My-Project is attached) FAILS: OS connection created has default value: openshift-dev https://192.168 ... and no project is connected) Case 2 1. EXEC: Have downloaded stable CDK (latest-weekly 3.1.0-1), set MINISHIFT_HOME (~/minishift_home) and called 'minishift setup-cdk' -> ~/minishift_home 2. EXEC: Run IDE, add CDK3 server adapter (via runtime or manually) 3. ASSERT: Open CDK3 Server adapter and check presence of correct MINISHIFT_HOME path 4. ASSERT: CDK3 is started, OS connection created (developer https://192 .... and My-Project is attached) FAILS: OS connection created has default value: openshift-dev https://192.168 ... and no project is connected)

      In the first case I would understand that if you change you minishift home (in server editor) and then you start server adapter, you will get some mess... Although, I would like to see a validation of minishift home here. We are checking minishit binary, why not to check minishift home (in this case for existence of the folder). See

      In the second case comes the bug. Even if I have set MINISHIFT_HOME folder, called setup-cdk that configured everything in that folder and put this folder as Minishift Home, CDK3 Server Adapter is not respecting that location. Or it is maybe OS tooling, not sure here. Solution here would be a check that verifies minishift's home set in CDK server editor corresponds with the one that minishift binary uses, if it is possible (from the side of binary) - but that seems not to be an option here as minishift/cdk stored everything in config that resides in MINISHIFT_HOME or ~/.minishift folder. See

      Cc: adietish@redhat.com rob.stryker.

        1. cdk3_sa-manual_correct-mhome.png
          cdk3_sa-manual_correct-mhome.png
          257 kB
        2. cdk3_sa-manual_wrong-mhome2.png
          cdk3_sa-manual_wrong-mhome2.png
          188 kB

              rob.stryker Rob Stryker (Inactive)
              odockal@redhat.com Ondrej Dockal
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: