Bug 1311727 - Cartridges with versions starting with 1.x are not seen by the broker
Summary: Cartridges with versions starting with 1.x are not seen by the broker
Keywords:
Status: CLOSED EOL
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: ImageStreams
Version: 2.2.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Sally
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-24 20:27 UTC by Timothy Williams
Modified: 2017-01-13 21:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-13 21:46:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Timothy Williams 2016-02-24 20:27:55 UTC
Description of problem:
After creating a cartridge with a cartridge-version of 1.anything and installing it on the node, the broker is unable to add the cartridge to its list of cartridges.

Version-Release number of selected component (if applicable):
2.2

How reproducible:
Always

Steps to Reproduce:
1. Create a cartridge on a node with a cartridge-version of '1.0.2.19.1'. The simplest way to do this would be to copy one of the redhat cartridges in /usr/libexec/openshift/cartridges and change the manifest.yml  
2. Install the cartridge with
	oo-admin-cartridge -a install -s /path/to/copied/cartridge
3. Restart the ruby193-mcollective service
4. Clear the broker's cache
	oo-admin-broker-cache --clear
5. Attempt to add the cartridge to the broker's list
	oo-admin-ctl-cartridge -c import-profile --activate

Actual results:
The new cartridge is not seen. "No changes made"

Expected results:
The new cartridge version is added.

Additional info:
This was reproduced specifically by copying the mysql cartridge redhat provides and modifying the cartridge-version in the manifest.yml.

Comment 2 Rory Thrasher 2017-01-13 21:46:56 UTC
OpenShift Enterprise v2 has officially reached EoL.  This product is no longer supported and bugs will be closed.

Please look into the replacement enterprise-grade container option, OpenShift Container Platform v3.  https://www.openshift.com/container-platform/

More information can be found here: https://access.redhat.com/support/policy/updates/openshift/


Note You need to log in before you can comment on or make changes to this bug.