Bug 864921
| Summary: | Exception is seen upon creating domain when no cartridge is installed in node. | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
| Component: | Node | Assignee: | Luke Meyer <lmeyer> |
| Status: | CLOSED ERRATA | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 1.1.0 | CC: | bleanhar, jkeck, xjia |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-31 20:31:57 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: | |||
| Bug Depends On: | 888550 | ||
| Bug Blocks: | |||
|
Description
Johnny Liu
2012-10-10 11:53:09 UTC
We're investigating this sprint how to have rhc properly handle 500 errors from the server. The actual problem reported has gone away at some point. When the node has an empty cart list (or none), that's what's reported via the API. You can still get an error in the same way, though, by having no nodes, or none that respond. The error bubbles up when doing a domain operation, including rhc setup (because a cartridge list is requested for reporting to the user; I don't think that's a problem). rhc is being modified to improve its handling, but I still think it's improper for the broker to give a 500 error just because it can't reach nodes. Particularly during the early stages of an install, before the user has tried to do anything requiring a node. Working on the fix. The exception is now caught and just logged, with an empty cartridge list returned. The empty list isn't cached, so once any node shows up, the user should get a fresh cartridge list. So to test: 1. Set up a new broker & node 2. service mcollective stop on the node 3. (clear broker cache if it has been populated) 4. rhc setup a user (it shouldn't get any errors but have empty cartridge list) 5. service mcollective start on the node 6. rhc setup a user again (it should report the correct list of cartridges) Fix is in rubygem-openshift-origin-controller-1.0.9-1.el6op [jason@jasontest ~]$ rhc setup
OpenShift Client Tools (RHC) Setup Wizard
This wizard will help you upload your SSH keys, set your application namespace, and check that other programs like Git are properly installed.
Login to broker.example.com: |jia|
Password: ***
Configuration file /home/jason/.openshift/express.conf already exists, backing up to /home/jason/.openshift/express.conf.bak
Created local config file: /home/jason/.openshift/express.conf
The express.conf file contains user configuration, and can be transferred to different computers.
We will now check to see if you have the necessary client tools installed.
Checking for git ... found
Checking for your namespace ... found namespace:
jia
Checking for applications ... none found
Run 'rhc app create' to create your first application.
Below is a list of the types of application you can create:
Thank you for setting up your system. You can rerun this at any time by calling 'rhc setup'.
[jason@jasontest ~]$
Version:
OpenShiftEnterprise/1.1.x/2012-12-18.1
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. http://rhn.redhat.com/errata/RHSA-2013-0220.html |