Bug 964269 - migrate.rb#validate_gear sometimes yields inaccurate response code
Summary: migrate.rb#validate_gear sometimes yields inaccurate response code
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Containers
Version: 2.x
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: ---
Assignee: Dan McPherson
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-17 17:12 UTC by Paul Morie
Modified: 2015-05-14 23:18 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-30 03:33:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Paul Morie 2013-05-17 17:12:51 UTC
migrate.rb#validate_gear sometimes yields inaccurate response code - after I migrate a nodejs app, the response code logged is 503, but I can hit the migrated app in the browser.

Comment 1 Dan Mace 2013-05-17 19:30:11 UTC
Resolved by https://github.com/openshift/li/pull/1413

Comment 2 Dan Mace 2013-05-17 19:31:03 UTC
(In reply to comment #1)
> Resolved by https://github.com/openshift/li/pull/1413

Risregard; commented on the wrong issue.

Comment 3 Dan McPherson 2013-05-17 21:54:56 UTC
https://github.com/openshift/li/pull/1415

Comment 4 Meng Bo 2013-05-20 08:31:07 UTC
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.

Comment 5 Paul Morie 2013-05-30 03:33:01 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.