Description of problem: While creating an app with rhc, it throws an exception. NOTE: the application is created fine and is usable. The DNS _is_ setup correctly. I have no idea why this is throwing an exception. NOTE: it doesn't seem to go through the retry period checking for the DNS to have been propagated. Here is the debug output from rhc: DEBUG: rhc app create -k -a 'd1304091611php' -t 'php-5.3' -d DEBUG: Connecting to https://localhost/broker/rest/api DEBUG: Getting all cartridges DEBUG: Request GET https://localhost/broker/rest/api DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 49 ms DEBUG: Request GET https://localhost/broker/rest/cartridges DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 105 ms DEBUG: Getting all domains DEBUG: Request GET https://localhost/broker/rest/domains DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 200 2322 ms DEBUG: Getting all domains DEBUG: Finding domain nagiosmonitor DEBUG: Getting all domains DEBUG: Getting all domains Application Options ------------------- Namespace: nagiosmonitor Cartridges: php-5.3 Gear Size: default Scaling: no Creating application 'd1304091611php' ... DEBUG: Creating application 'd1304091611php' with these options - {:cartridges=>["php-5.3"]} DEBUG: Adding application d1304091611php to domain nagiosmonitor DEBUG: Request POST https://localhost/broker/rest/domains/nagiosmonitor/applications DEBUG: SSL Verification failed -- Using self signed cert DEBUG: code 201 30389 ms DEBUG: 'd1304091611php' created done Waiting for your DNS name to be available ... DEBUG: Start checking for application dns @ 'd1304091611php-nagiosmonitor.int.rhcloud.com' DEBUG: Error while resolving with Resolv::Hosts: /etc/hosts has no name: d1304091611php-nagiosmonitor.int.rhcloud.com(Resolv::ResolvError) /usr/lib/ruby/1.8/resolv.rb:220:in `getaddress' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/helpers.rb:492:in `hosts_file_contains?' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/helpers.rb:508:in `with_tolerant_encoding' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/helpers.rb:489:in `hosts_file_contains?' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/commands/app.rb:429:in `dns_propagated?' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/commands/app.rb:127:in `create' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/helpers.rb:436:in `call' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/helpers.rb:436:in `section' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/helpers.rb:450:in `paragraph' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/commands/app.rb:125:in `create' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/commands.rb:228:in `send' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/commands.rb:228:in `execute' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/commands.rb:219:in `to_commander' /usr/lib/ruby/gems/1.8/gems/commander-4.0.3/lib/commander/command.rb:180:in `call' /usr/lib/ruby/gems/1.8/gems/commander-4.0.3/lib/commander/command.rb:180:in `call' /usr/lib/ruby/gems/1.8/gems/commander-4.0.3/lib/commander/command.rb:155:in `run' /usr/lib/ruby/gems/1.8/gems/commander-4.0.3/lib/commander/runner.rb:385:in `run_active_command' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/command_runner.rb:70:in `run!' /usr/lib/ruby/gems/1.8/gems/commander-4.0.3/lib/commander/delegates.rb:7:in `run!' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/lib/rhc/cli.rb:42:in `start' /usr/lib/ruby/gems/1.8/gems/rhc-1.7.2/bin/rhc:18 /usr/bin/rhc:19:in `load' /usr/bin/rhc:19 DEBUG: End checking for application dns @ 'd1304091611php-nagiosmonitor.int.rhcloud.com - found=false' Version-Release number of selected component (if applicable): rhc-1.7.2-1.el6oso.noarch How reproducible: Happens every time with this version of rhc. This hasn't been a problem in the past. Steps to Reproduce: 1. On a RHEL 6.4 box, run: rhc app create -k -a 'd1304091611php' -t 'php-5.3' -d 2. Notice the error as above Actual results: Error above Expected results: No DNS error
QE can reproduce this bug on RHEL-6.4, it works well on other platforms like RHEL-6.3, Fedora17. Thanks.
That's a print out of the exception in debug logs, it's not a real error. We just want to be absolutely sure that DNS isn't failing for some other unexpected reason so we print the stack trace.