Not being able to resolve localhost cause OpenShift component connection issues.

Solution Verified - Updated -

Issue

  • We are doing a fresh install, and see the following when running oo-diagnostics -v.
FAIL: run_script
oo-accept-broker had errors:
--BEGIN OUTPUT--
NOTICE: SELinux is Enforcing
NOTICE: SELinux is  Enforcing
FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/api
FAIL: Did not get expected HTTP 200 response from https://localhost/broker/rest/cartridges
2 ERRORS
  • I also see the following in my production.log for the broker
[Fri Feb 21 13:41:30 2014] [notice] Apache/2.2.15 (Unix) Phusion_Passenger/3.0.21 configured -- resuming normal operations
[ pid=1705 thr=7481480 file=utils.rb:176 time=2014-02-21 13:41:46.289 ]: *** Exception PhusionPassenger::UnknownError in PhusionPassenger::Rack::ApplicationSpawner (Could not connect to a primary node for replica set <Moped::Cluster nodes=[<Moped::Node resolved_address=nil>]> (Moped::Errors::ConnectionFailure)) (process 1705, thread #<Thread:0x00000000e45110>):

Environment

  • OpenShift Enterprise

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.