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

Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 4.5.1.Final
    • 4.5.1.AM3
    • cdk
    • None
    • devex #139 October 2017
    • Hide

      1. EXEC: Have cdk 3.2.x binary downloaded
      2. EXEC: Create CDK 3.2+ adapter with no profile set
      3. EXEC: Prepare cdk: call setup-cdk on cli
      4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)'
      5. EXEC: Start CDK 3.2+ server adapter
      6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)'
      7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test'
      8. EXEC: call 'minishift setup-cdk --profile test'
      9. EXEC: Start CDK 3.2+ test server adapter -> this should set profile 'test' as active
      10. ASSERT: CDK 3.2+ test SA is started
      11. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active
      12. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set)
      13. ASSERT: CDK 3.2+ adapter is stopped - This shows adapter's state as stopped, which is false positive information
      14. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL
      Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.

      Show
      1. EXEC: Have cdk 3.2.x binary downloaded 2. EXEC: Create CDK 3.2+ adapter with no profile set 3. EXEC: Prepare cdk: call setup-cdk on cli 4. ASSERT: calling 'minishift profile list' returns '- minishift Does Not Exist (active)' 5. EXEC: Start CDK 3.2+ server adapter 6. ASSERT: Adapter is started, 'minishift profile list' returns '- minishift Running (active)' 7. EXEC: Add new CDK 3.2+ called test and set profile to ie. 'test' 8. EXEC: call 'minishift setup-cdk --profile test' 9. EXEC: Start CDK 3.2+ test server adapter -> this should set profile 'test' as active 10. ASSERT: CDK 3.2+ test SA is started 11. ASSERT: 'minishift profile list' shows two running profiles and 'test' is active 12. EXEC: Stop CDK 3.2+ default server adapter (the one without profile set) 13. ASSERT: CDK 3.2+ adapter is stopped - This shows adapter's state as stopped, which is false positive information 14. ASSERT: 'minishift profile list' shows that default 'minishift' profile is stopped - FAIL Instead, active profile 'test' was stopped, because stop operation was not passed with --profile ProfileName flag, which should be in this case 'minishift' to stop proper adapter/profile.

      I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile.

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

              Created:
              Updated:
              Resolved: