Description of problem: When create app, the DNS name of the app could not be available and app is inaccessible after creation Version-Release number of selected component (if applicable): devenv_4728 How reproducible: always Steps to Reproduce: 1. Create one app rhc app create r18 ruby-1.8 2. wait for the app creation to finish Actual results: The DNS name of the app could not be available and app is inaccessible as below: ---------------------------------------- Waiting for your DNS name to be available ... retry # 1 - Waiting for DNS: r18-domain1.dev.rhcloud.com retry # 2 - Waiting for DNS: r18-domain1.dev.rhcloud.com retry # 3 - Waiting for DNS: r18-domain1.dev.rhcloud.com retry # 4 - Waiting for DNS: r18-domain1.dev.rhcloud.com retry # 5 - Waiting for DNS: r18-domain1.dev.rhcloud.com retry # 6 - Waiting for DNS: r18-domain1.dev.rhcloud.com retry # 7 - Waiting for DNS: r18-domain1.dev.rhcloud.com failure !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING: Your application was created successfully but had problems during configuration. Below is a list of the issues and steps you can take to complete the configuration of your application. Application URL: http://r18-domain1.dev.rhcloud.com/ Issues: 1. We were unable to lookup your hostname (r18-domain1.dev.rhcloud.com) in a reasonable amount of time and can not clone your application. Steps to complete your configuration: 1. Clone your git repo $ rhc git-clone r18 If you continue to experience problems after completing these steps, you can try destroying and recreating the application: $ rhc app delete r18 --confirm Please contact us if you are unable to successfully create your application: Support - https://www.openshift.com/support !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ---------------------------------------- Expected results: app should be created successfully and DNS name should be available. Additional info: N/A
Created attachment 890403 [details] broker_log_during_app_creation Both ssh connect and visit the app inside the instance do not have any problem. And this should not be a DNS outage issue. The problem should exist after the gear created and before the app DNS being propagated. Add the broker log during app creation.
Now this problem doesn't exist on the latest devenv_4733.
I don't see any errors inside the attachment provided in comment 1. Please either provide more info or close if the problem no longer exists.
This problem only exist on the devenv_4728 environment, all the applications could not be accessed that day but now we can not reproduced the problem. Please got this. Thank you. -------------------------------------------- (In reply to Lili Nader from comment #3) > I don't see any errors inside the attachment provided in comment 1. Please > either provide more info or close if the problem no longer exists.