[ https://issues.jboss.org/browse/JBIDE-13569?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-13569 at 2/15/13 9:57 AM: ------------------------------------------------------------------- I tried rhc cmd-line tooling and I dont see them requesting some health-path any more, they seem to only wait for DNS resolution: {code} [adietish@adietish-thinkpad jbosstools-openshift]$ rhc app create --app "freaky" jbossas-7 Invalid gemspec in [/usr/lib/ruby/gems/1.8/specifications/json_pure-1.6.1.gemspec]: invalid date format in specification: "2011-09-18 00:00:00.000000000Z" Password: ********* Application Options ------------------- Namespace: myops Cartridges: jbossas-7 Gear Size: default Scaling: no Creating application 'freaky' ... done Waiting for your DNS name to be available ... done Your public SSH key must be uploaded to the OpenShift server to access code. Upload now? (yes|no) no {code} In terms of code, I also only see them waiting for successful DNS resolution - there's apparently no request to a health-url any more: {code:title=https://github.com/openshift/rhc/blob/master/lib/rhc/commands/app.rb#L120} say "Waiting for your DNS name to be available ... " if dns_propagated? rest_app.host success "done" else warn "failure" add_issue("We were unable to lookup your hostname (#{rest_app.host}) in a reasonable amount of time and can not clone your application.", "Clone your git repo", "rhc git-clone #{rest_app.name}") output_issues(rest_app) return 0 end {code} {code:title=https://github.com/openshift/rhc/blob/master/lib/rhc/commands/app.rb#L408} def dns_propagated?(host, sleep_time=2) # # Confirm that the host exists in DNS # debug "Start checking for application dns @ '#{host}'" found = false # Allow DNS to propagate Kernel.sleep 5 # Now start checking for DNS host_found = hosts_file_contains?(host) or 1.upto(MAX_RETRIES) { |i| host_found = host_exists?(host) break found if host_found say " retry # #{i} - Waiting for DNS: #{host}" Kernel.sleep sleep_time.to_i sleep_time *= DEFAULT_DELAY_THROTTLE } debug "End checking for application dns @ '#{host} - found=#{found}'" host_found end {code} was (Author: adietish): I tried rhc cmd-line tooling and I dont see them requesting some health-path any more, they seem to only wait for DNS resolution: {code} [adietish@adietish-thinkpad jbosstools-openshift]$ rhc app create --app "freaky" jbossas-7 Invalid gemspec in [/usr/lib/ruby/gems/1.8/specifications/json_pure-1.6.1.gemspec]: invalid date format in specification: "2011-09-18 00:00:00.000000000Z" Password: ********* Application Options ------------------- Namespace: myops Cartridges: jbossas-7 Gear Size: default Scaling: no Creating application 'freaky' ... done Waiting for your DNS name to be available ... done Your public SSH key must be uploaded to the OpenShift server to access code. Upload now? (yes|no) no {code} In terms of code, I also only see them waiting for successful DNS resolution - there's apparently no request to a health-url any more: {code:title=https://github.com/openshift/rhc/blob/master/lib/rhc/commands/app.rb#L120} say "Waiting for your DNS name to be available ... " if dns_propagated? rest_app.host success "done" else warn "failure" add_issue("We were unable to lookup your hostname (#{rest_app.host}) in a reasonable amount of time and can not clone your application.", "Clone your git repo", "rhc git-clone #{rest_app.name}") output_issues(rest_app) return 0 end {code} {code:title=https://github.com/openshift/rhc/blob/master/lib/rhc/commands/app.rb#L408} def dns_propagated?(host, sleep_time=2) # # Confirm that the host exists in DNS # debug "Start checking for application dns @ '#{host}'" found = false # Allow DNS to propagate Kernel.sleep 5 # Now start checking for DNS host_found = hosts_file_contains?(host) or 1.upto(MAX_RETRIES) { |i| host_found = host_exists?(host) break found if host_found say " retry # #{i} - Waiting for DNS: #{host}" Kernel.sleep sleep_time.to_i sleep_time *= DEFAULT_DELAY_THROTTLE } debug "End checking for application dns @ '#{host} - found=#{found}'" host_found end {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira