Bug 828055
Summary: | scalable app gear down after created on stage | ||
---|---|---|---|
Product: | OKD | Reporter: | Meng Bo <bmeng> |
Component: | Containers | Assignee: | Rob Millner <rmillner> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 2.x | CC: | mfisher |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-08 17:59:11 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
Meng Bo
2012-06-04 07:11:02 UTC
$ grep libra_server ~/.openshift/express.conf libra_server=stg.openshift.redhat.com $ rhc app create -p [hidden] -a scalejboss -t jbossas-7 -s Creating application: scalejboss in rmstg Now your new domain name is being propagated worldwide (this might take a minute)... retry # 4 - Waiting for DNS: scalejboss-rmstg.stg.rhcloud.com Warning: Permanently added 'scalejboss-rmstg.stg.rhcloud.com,107.21.77.136' (RSA) to the list of known hosts. Confirming application 'scalejboss' is available: Success! scalejboss published: http://scalejboss-rmstg.stg.rhcloud.com/ git url: ssh://1110d509273349e6ba12dfa7d6bac7e3.rhcloud.com/~/git/scalejboss.git/ Successfully created application: scalejboss Accessing haproxy shows the gear is up: http://scalejboss-rmstg.stg.rhcloud.com/haproxy-status/ Accessing the app shows the welcome page: http://scalejboss-rmstg.stg.rhcloud.com/ Suspect this is due to hitting one of the numerous timeouts we have baked into the system while stg was under a heavy load. Still unable to reproduce this problem. An issue related to scalable applications that only affected stg and prod was resolved as part of bugzilla ticket 828038. I believe it also resolved the underlying cause for this problem. Passing back to Q/A to see if it can still be reproduced or if it was fixed as a result of fixing 828038. verified on today's stage, issus has been fixed. |