Bug 964269
| Summary: | migrate.rb#validate_gear sometimes yields inaccurate response code | ||
|---|---|---|---|
| Product: | OpenShift Online | Reporter: | Paul Morie <pmorie> |
| Component: | Containers | Assignee: | Dan McPherson <dmcphers> |
| Status: | CLOSED WONTFIX | QA Contact: | libra bugs <libra-bugs> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.x | CC: | bmeng, dmace, dmcphers |
| 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-05-30 03:33:01 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
Paul Morie
2013-05-17 17:12:51 UTC
Resolved by https://github.com/openshift/li/pull/1413 (In reply to comment #1) > Resolved by https://github.com/openshift/li/pull/1413 Risregard; commented on the wrong issue. This issue still can be reproduced on devenv_3247 for nodejs app. Migrating cartridge nodejs Marking step nodejs_create_directory complete Marking step nodejs_setup complete Marking step nodejs_erb complete applying nodejs-0.6 migration post-process Marking step nodejs_hook complete Marking step nodejs_ownership complete Marking step nodejs_connect_frontend complete Pre-migration state: started Post-migration response code: 503 Marking step validate_gear complete Cleaning up after migration***time_migrate_on_node_measured_from_node=111486*** ***time_redeploy_httpd_proxy=0*** ***time_restart=0*** ***time_total_migrate_gear_measured_from_broker=113560*** And the nodejs app can be accessed after migration. This issue is also present for Jboss apps. That said, there's been a retry added already for this check - we're going to stick with the single retry. |