MongoDB Connection refused on overcloud/controllers with ipv6

Bug #1560503 reported by Emilien Macchi
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Undecided
Emilien Macchi

Bug Description

We have an error in Puppet catalog when deploying overcloud controllers with ipv6.

http://logs.openstack.org/35/289435/5/check-tripleo/gate-tripleo-ci-f22-ha/372d303/console.html#_2016-03-22_04_10_23_649

exception: connect failed\nCould not retrieve fact='mongodb_is_master', resolution='<anonymous>': 757: unexpected token at '2016-03-22T04:04:01.141+0000 warning: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused\n2016-03-22T04:04:01.142+0000 Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed at src/mongo/shell/mongo.js:146'\nexception: connect failed\nCould not retrieve fact='mongodb_is_master', resolution='<anonymous>': 757: unexpected token at '2016-03-22T04:04:01.340+0000 warning: Failed to connect to 127.0.0.1:27017, reason: errno:111 Connection refused\n2016-03-22T04:04:01.342+0000 Error: couldn't connect to server 127.0.0.1:27017 (127.0.0.1), connection attempt failed at src/mongo/shell/mongo.js:146'\n\u001b[1;31mWarning: Scope(Class[Mongodb::Server]): Replset specified, but no replset_members or replset_config provided.

Changed in tripleo:
assignee: nobody → Emilien Macchi (emilienm)
description: updated
summary: - MongoDB Connection refused on overcloud/controllers
+ MongoDB Connection refused on overcloud/controllers with ipv6
Changed in tripleo:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.