[library] Deployment fails: DNS resolving is broken on nodes with Mongo role

Bug #1438591 reported by Artem Panchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
High
Oleksiy Molchanov

Bug Description

Fuel version info (6.1 build # 234): http://paste.openstack.org/show/197658/

Environment deployment fails on Ubuntu if 'Ceilometer' is enabled, because after deployment (dns-client.pp) of nodes with 'mongo' role, they can't resolve DNS names:

http://paste.openstack.org/show/197660/

Steps to reproduce:

1. Create new environment: Ubuntu, Neutron+Vlan, Ceph for all, Ceilometer
2. Add 3 controller+mongo nodes and 1+ compute+ceph nodes
3. Enable 'Classic' provision method on settings tab
4. Start deployment

Expected result:

- cluster successfully deployed and passes health checks

Actual:

- cluster deployment failed

Here is a content of '/etc/resolv.conf/' file on controller+mongo node after deployment failed:

http://paste.openstack.org/show/197661/

and tasks deployment sequence:

http://paste.openstack.org/show/197664/

As you can see node was configured to use management VIP as DNS resolver before controller roles were deployed.

Tags: puppet
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Oleksiy Molchanov (omolchanov)
Revision history for this message
Artem Panchenko (apanchenko-8) wrote :

Seems that image based provisioning on Ubuntu isn't affected, because resolvconf is unable to update '/etc/resolf.conf':

root@node-1:~# cat /etc/resolv.conf
# re-generated by cloud-init boothook only at the first boot;
search mirantis.com
domain mirantis.com
nameserver 172.16.39.130
root@node-1:~# resolvconf -u
/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
root@node-1:~# ls -1l /etc/resolv.conf
-rw-r--r-- 1 root root 127 Mar 31 11:54 /etc/resolv.conf

but I think this breaks 'external dns' feature (see blueprint external-dns-ntp-support)

Changed in fuel:
status: New → In Progress
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Artem,

We are waiting for patch to fix the issue you described in last comment
https://bugs.launchpad.net/fuel/+bug/1434232

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/169321

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/169321
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=71d9b80942b8096e2510644e403bbaf6e08cb3c1
Submitter: Jenkins
Branch: master

commit 71d9b80942b8096e2510644e403bbaf6e08cb3c1
Author: Oleksiy Molchanov <email address hidden>
Date: Tue Mar 31 17:04:29 2015 +0300

    Configure resolv.conf in post-deploy

    Configure resolv.conf to run in post-deploy stage

    Change-Id: I4600cfa97466fad4fc70dd2e6b03b1d7a02b2509
    Closes-Bug: 1438591

Changed in fuel:
status: In Progress → Fix Committed
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.