Bug 1007730
Summary: | Ruby apps return 503 when accessing and cannot be started/restarted after migration | ||
---|---|---|---|
Product: | OpenShift Online | Reporter: | Meng Bo <bmeng> |
Component: | Containers | Assignee: | Michal Fojtik <mfojtik> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | bmeng, chunchen, jhonce, vvitek, xtian |
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: | 2013-09-19 16:51:17 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
2013-09-13 08:50:29 UTC
Seems to me like the migration didn't run the 'setup' - I mean this line: https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-ruby/bin/setup#L20 Meng, could you please confirm that this file exists on the filesystem? /var/lib/openshift/52327c15caf1de0aa3000004/ruby//etc/conf.d/passenv.conf If no, then it might be a migration problem (see Vojtech comment). According to the http://openshift.github.io/documentation/oo_cartridge_developers_guide.html#bin-setup, the setup is run only on non-backward compatible upgrade. I think we didn't mark the new cartridges incompatible in the manifest.yml, is that correct, Jhon? The above statement would be related to the following cartridges: perl php phpmyadmin python ruby Michal Fojtik, the file is not existing as Comment 2 mentioned. Michal Fojtik, the file is existing on STG as Comment 2 mentioned, and in Comment 6 it means on INT. Michal Fojtik, i think Comment 6&7 may make you confuse, sorry for that, please ignore them and refer to the following information: After checking it on STG today, found that the ruby applications can be started/restarted and accessed successfully via browser. So, this issue just occurred on INT/devenv and the passenv.conf file is not on devenv/INT's filesystem. According to above messages, lower the severity to medium. Thanks! This should have been fixed in current STG(devenv-stage_472), please move it to ON_QA when you think it's ready. Existing ruby apps work well on STG after migration. Move bug to verified. |