Description of problem: The customer is using an environment where multiple versions (or in other means multiple installations) of the same cartridge is available on the broker (as displayed with oo-admin-ctl-cartridge -c list). In order to activate/deactivate the correct cartridges, the --ids options will have be used, but there is no easy way to obtain the IDs (OIDs) from the cartridges when using oo-admin-ctl-cartridge -c list). A couple of workaround exists, but these are not ideal from a system admin perspective (e.g.: use the --raw option or -q option and manually map IDs with names). Version-Release number of selected component (if applicable): OSE 2.2.4 How reproducible: See description above Steps to Reproduce: See description above Actual results: No easy way to map OIDs with the list of cartridges produced by "-c list". Expected results: An easy and reliable way of obtaining the OIDs from the "-c list" command. Additional info: A proposed code change has been made and a PR will be submitted soon.
PR created: https://github.com/openshift/origin-server/pull/6115
Check on puddle [2.2.5/2015-05.05.2] 1.run command with --all #oo-admin-ctl-cartridge -c list --all * cron-1.4 plugin Cron 1.4 2015/05/06 02:41:59 UTC 55497f7782611dc7a3000012 * jenkins-client-1 plugin Jenkins Client 2015/05/06 02:41:59 UTC 55497f7782611dc7a300000c * mongodb-2.4 service MongoDB 2.4 2015/05/06 02:41:58 UTC 55497f7682611dc7a3000004 * mysql-5.1 service MySQL 5.1 2015/05/06 02:41:59 UTC 55497f7782611dc7a300000b * mysql-5.5 service MySQL 5.5 2015/05/06 02:41:58 UTC 55497f7782611dc7a300000a * postgresql-8.4 service PostgreSQL 8.4 2015/05/06 02:41:59 UTC 55497f7782611dc7a3000010 <--snip--> list all cartridges with OIDs 2. list specified cartridges # oo-admin-ctl-cartridge -c list -n cron-1.4,mysql-5.1 --all * cron-1.4 plugin Cron 1.4 2015/05/06 02:41:59 UTC 55497f7782611dc7a3000012 * mysql-5.1 service MySQL 5.1 2015/05/06 02:41:59 UTC 55497f7782611dc7a300000b list specified cartridges with OIDs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1463.html