DNS on deployed cluster doesn't respect DNS_UPSTREAM from astute.yaml

Bug #1442675 reported by Dennis Dmitriev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Dennis Dmitriev

Bug Description

Reproduced on CI: http://jenkins-product.srt.mirantis.net:8080/job/6.1.system_test.ubuntu.classic_provisioning/1/ , here is the exception: http://paste.openstack.org/show/202072/

When cluster deployed, DNS on controllers are configured without respecting the 'DNS_UPSTREAM' setting provided from /etc/fuel/astute.yaml:

=== controller:
root@node-1:~# cat /etc/resolv.dnsmasq.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

===== admin node:
[root@nailgun ~]# cat /etc/fuel/astute.yaml
HOSTNAME: nailgun
DNS_DOMAIN: test.domain.local
DNS_SEARCH: test.domain.local
DNS_UPSTREAM: 10.109.15.1 8.8.8.8
....

As the result: it is impossible to access the intranet resources from the cloud using host names of the resources.

Changed in fuel:
importance: Undecided → High
status: New → Confirmed
assignee: Fuel Library Team (fuel-library) → Oleksiy Molchanov (omolchanov)
Revision history for this message
Vladimir Kuklin (vkuklin) wrote :

I suppose this is because you have not specified this server as DNS server for the particular cluster - nailgun does not inherit such settings from settings.yaml, unfortunately.

Changed in fuel:
assignee: Oleksiy Molchanov (omolchanov) → Fuel QA Team (fuel-qa)
Changed in fuel:
assignee: Fuel QA Team (fuel-qa) → Dennis Dmitriev (ddmitriev)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-qa (master)

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

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

Reviewed: https://review.openstack.org/173267
Committed: https://git.openstack.org/cgit/stackforge/fuel-qa/commit/?id=f2f18f4e195f522deba34ea5d7f1509af7c400ca
Submitter: Jenkins
Branch: master

commit f2f18f4e195f522deba34ea5d7f1509af7c400ca
Author: Dennis Dmitriev <email address hidden>
Date: Tue Apr 14 13:54:11 2015 +0300

    Use admin node as DNS in system tests

    When a cluster is deployed, it's DNS settings contain only external
    servers. It makes impossible to access intranet resources from
    cluster nodes.

    - replase DNS list for cluster with admin node IP (only if dns_list
    was not customized from a test case)

    - in 'revert_snapshot', place sync_time() before access to nailgun

    Change-Id: Idf3621a94ae109d93a9235c83c08d8fb2d792826
    Closes-Bug: #1442675

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Dennis Dmitriev (ddmitriev) wrote :

ISO version: {u'build_id': u'2015-04-15_23-18-33', u'ostf_sha': u'90f232a25d10f98db9d5531a3b133319529f57aa', u'build_number': u'314', u'auth_required': True, u'nailgun_sha': u'24b56283fb4caaba6b6414056dad30e503a7c30f', u'openstack_version': u'2014.2-6.1', u'production': u'docker', u'api': u'1.0', u'python-fuelclient_sha': u'ff186de358cbda489a320723de47a9e61ae23364', u'astute_sha': u'36a3d54baf86480326866279778b867086aa4b05', u'fuelmain_sha': u'd3aa72d814c3f18799b566363004a22591161cef', u'feature_groups': [u'mirantis'], u'release': u'6.1', u'release_versions': {u'2014.2-6.1': {u'VERSION': {u'build_id': u'2015-04-15_23-18-33', u'ostf_sha': u'90f232a25d10f98db9d5531a3b133319529f57aa', u'openstack_version': u'2014.2-6.1', u'nailgun_sha': u'24b56283fb4caaba6b6414056dad30e503a7c30f', u'production': u'docker', u'api': u'1.0', u'python-fuelclient_sha': u'ff186de358cbda489a320723de47a9e61ae23364', u'astute_sha': u'36a3d54baf86480326866279778b867086aa4b05', u'fuelmain_sha': u'd3aa72d814c3f18799b566363004a22591161cef', u'feature_groups': [u'mirantis'], u'release': u'6.1', u'build_number': u'314', u'fuellib_sha': u'ab6dbba825a5e54f3183ed8582921a0328b211c7'}}}, u'fuellib_sha': u'ab6dbba825a5e54f3183ed8582921a0328b211c7'}

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