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

Application wizard, embed wizard: The obsoleted cartridges (standalone and embedded)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.3.0.Alpha1
    • 4.1.2.Final
    • openshift
    • None
    • Hide
      1. EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application
      2. EXEC: Provide your access credentials
      3. EXEC: Check the cartridge list for zend-5.6

      Result:
      You can still see the obsolete cartridge zend-5.6 (standalone-, web-cartridge)

      1. ASSERT: make sure that you have an application running on OpenShift
      2. EXEC: in OpenShift Explorer: pick "Edit Embeddable Cartridges..." from the context menu of your application
      3. ASSERT: the wizard to edit the embedded cartridges shows up and lists the available cartridges
      4. EXEC: check the list of available cartridges

      Result:
      You can still see the obsolete cartridge metrics-0.1

      ps. it's especially important to verify that the tooling still works fine if it doesnt show the obsolete standalone- and embedded cartridges (application- and embedded cartridges wizards). To achieve this have a devenv, ssh to it (you need root access) and do the following:

      1. in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: false
        service ruby193-mcollective restart
        oo-broker
        oo-admin-ctl-cartridge -c import-node --activate --obsolete
      2. EXEC: in Eclipse: create an application using the mock standalone cartridge and embed the metrics cartridge to it
      3. ASSERT: the application is created and shows up in the Explorer
      4. EXEC: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: true
        service ruby193-mcollective restart
        oo-broker
        oo-admin-ctl-cartridge -c import-node --activate --obsolete
      5. EXEC: in ssh: edit /usr/libexec/openshift/cartridges/mock/metadata/manifest.yml -> Obsolete: true
        service ruby193-mcollective restart
        oo-broker
        oo-admin-ctl-cartridge -c import-node --activate --obsolete
      6. EXEC: restart Eclipse (Eclipse caches the lists of available cartridges)
      7. EXEC: in Eclipse: the application still shows up in Explorer but:
        • mock cartridge wont show up in the "Basic Cartridges" in application wizard (File->New->OpenShift->New Application)
        • metrics cartridge wont show up in the embed cartridges wizard (Explorer: Edit Embedded Cartridges)
          and:
        • you can still import the mock-cartridge (we obsoleted it in the steps above) application to your workspace
        • you still have the metrics cartridge listed in the embedded cartridges
      Show
      EXEC: Open OpenShift New Application Wizard: File -> New -> Other... -> OpenShift Application EXEC: Provide your access credentials EXEC: Check the cartridge list for zend-5.6 Result: You can still see the obsolete cartridge zend-5.6 (standalone-, web-cartridge) ASSERT: make sure that you have an application running on OpenShift EXEC: in OpenShift Explorer: pick "Edit Embeddable Cartridges..." from the context menu of your application ASSERT: the wizard to edit the embedded cartridges shows up and lists the available cartridges EXEC: check the list of available cartridges Result: You can still see the obsolete cartridge metrics-0.1 ps. it's especially important to verify that the tooling still works fine if it doesnt show the obsolete standalone- and embedded cartridges (application- and embedded cartridges wizards). To achieve this have a devenv, ssh to it (you need root access) and do the following: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: false service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete EXEC: in Eclipse: create an application using the mock standalone cartridge and embed the metrics cartridge to it ASSERT: the application is created and shows up in the Explorer EXEC: in ssh: edit /usr/libexec/openshift/cartridges/metrics/metadata/manifest.yml -> Obsolete: true service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete EXEC: in ssh: edit /usr/libexec/openshift/cartridges/mock/metadata/manifest.yml -> Obsolete: true service ruby193-mcollective restart oo-broker oo-admin-ctl-cartridge -c import-node --activate --obsolete EXEC: restart Eclipse (Eclipse caches the lists of available cartridges) EXEC: in Eclipse: the application still shows up in Explorer but: mock cartridge wont show up in the "Basic Cartridges" in application wizard (File->New->OpenShift->New Application) metrics cartridge wont show up in the embed cartridges wizard (Explorer: Edit Embedded Cartridges) and: you can still import the mock -cartridge (we obsoleted it in the steps above) application to your workspace you still have the metrics cartridge listed in the embedded cartridges

      The obsoleted cartridges are still shown in the cartridge list, like obsoleted cartridge zend-5.6, nodejs-0.6 and metrics-0.1, they should not be shown any more in the list.
      the issue may due to java-client not using the latest 1.7 version restapi.

            adietish@redhat.com André Dietisheim
            adietish@redhat.com André Dietisheim
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: