Bug 1098544
| Summary: | On fresh OpenShift Enterprise 2.1 installation, rhc cartridges does not list any cartridges | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jan Pazdziora (Red Hat) <jpazdziora> |
| Component: | Documentation | Assignee: | Alex Dellapenta <adellape> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ecs-bugs |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.1.0 | CC: | adellape, baulakh, bleanhar, jeff.mccormick, jokerman, jpazdziora, juwu, libra-onpremise-devel, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-06-11 01:20:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jan Pazdziora (Red Hat)
2014-05-16 14:09:35 UTC
It's going to depend how you install 2.1. If you use oo-install from install.openshift.com it should run the necessary commands. If you are using openshift.sh directly the following will need to be done: oo-admin-ctl-cartridge -c import-node --activate --obsolete In addition, for gears to be created a node must be added to a district. If you simply need to do this for a test environment this command is useful: oo-admin-ctl-district -p small -n default-small -c add-node --available Let me know if this works around your problem. The "Kickstart and Bash Installation Scripts" section[1] of the Deployment Guide can be updated to discuss / link to the following sections, which should hopefully clear this up: * https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Importing_Cartridges * https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-Districts [1] https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#Kickstart_and_Bash_Scripts (In reply to Brenton Leanhardt from comment #2) > It's going to depend how you install 2.1. If you use oo-install from > install.openshift.com it should run the necessary commands. If you are > using openshift.sh directly the following will need to be done: > > oo-admin-ctl-cartridge -c import-node --activate --obsolete > > In addition, for gears to be created a node must be added to a district. If > you simply need to do this for a test environment this command is useful: > > oo-admin-ctl-district -p small -n default-small -c add-node --available > > Let me know if this works around your problem. Adding oo-admin-ctl-cartridge -c import-node --activate --obsolete after creating the district and adding nodes to it (I do -c add-node -n small_district -i $node in a loop instead of --available) makes things pass. I wonder if add-node could have done that import-node as well, to avoid that extra steps in 2.1. Thank you. (In reply to Jan Pazdziora from comment #7) > Adding oo-admin-ctl-cartridge -c import-node --activate --obsolete after > creating the district and adding nodes to it (I do -c add-node -n > small_district -i $node in a loop instead of --available) makes things pass. > I wonder if add-node could have done that import-node as well, to avoid that > extra steps in 2.1. set CONF_ACTIONS=do_all_actions,post_deploy post_deploy does what you need. It is not part of the standard actions because it runs on the broker after you have your nodes up and running, and openshift.sh has no way to coordinate that. But if all you are doing is an all-in-one then that should work fine. For anything more interesting, you may want to look into oo-install. *** Bug 1098639 has been marked as a duplicate of this bug. *** |