[IBP] wrong resolv.conf settings

Bug #1416399 reported by Alexander Gordeev
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Critical
Alexander Gordeev
6.0.x
Fix Committed
Critical
Alexander Gordeev
6.1.x
Fix Released
Critical
Alexander Gordeev

Bug Description

IBP definately uses wrong data source for dns settings.

Resolv.conf contains hard coded:

nameserver 172.18.16.10
search msk.mirantis.net vm.mirantis.net mirantis.net

compared to classic:
domain <DOMAIN from fuelmenu settings>
nameserver <master node IP>

Changed in fuel:
assignee: Aleksandr Gordeev (a-gordeev) → Vladimir Kozhukalov (kozhukalov)
status: Confirmed → In Progress
Changed in fuel:
assignee: Vladimir Kozhukalov (kozhukalov) → Aleksandr Gordeev (a-gordeev)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/152560
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=8286437ef2b76c7b2cb24b3eb588bb14178caf9e
Submitter: Jenkins
Branch: master

commit 8286437ef2b76c7b2cb24b3eb588bb14178caf9e
Author: Vladimir Kozhukalov <email address hidden>
Date: Tue Feb 3 17:59:15 2015 +0300

    IBP: ubuntu: moved resolv.conf stuff to boothook

    The issue is that cloudinit/cc_resolv_conf.py is not working at all.
    For both centos and ubuntu resolv.conf editing was moved to
    cloud-init boothook stage. cloud-init will recreate resolv.conf on
    every boot.

    Closes-Bug: 1416399
    Change-Id: I3d6fdd15ea279928d39f5e6ce4136372db3172c5

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (stable/6.0)

Fix proposed to branch: stable/6.0
Review: https://review.openstack.org/153603

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (stable/6.0)

Reviewed: https://review.openstack.org/153603
Committed: https://git.openstack.org/cgit/stackforge/fuel-web/commit/?id=2ef819732a3ee7acf7b610e7d1c1a6da0434c1a0
Submitter: Jenkins
Branch: stable/6.0

commit 2ef819732a3ee7acf7b610e7d1c1a6da0434c1a0
Author: Vladimir Kozhukalov <email address hidden>
Date: Tue Feb 3 17:59:15 2015 +0300

    IBP: ubuntu: moved resolv.conf stuff to boothook

    The issue is that cloudinit/cc_resolv_conf.py is not working at all.
    For both centos and ubuntu resolv.conf editing was moved to
    cloud-init boothook stage. cloud-init will recreate resolv.conf on
    every boot.

    Closes-Bug: 1416399
    Change-Id: I3d6fdd15ea279928d39f5e6ce4136372db3172c5
    (cherry picked from commit 8286437ef2b76c7b2cb24b3eb588bb14178caf9e)

Revision history for this message
Anastasia Palkina (apalkina) wrote :

Verified on ISO #105

"build_id": "2015-02-07_22-55-01", "ostf_sha": "6c046b69d29021524906109f18092363505ee222", "build_number": "105", "release_versions": {"2014.2-6.1": {"VERSION": {"build_id": "2015-02-07_22-55-01", "ostf_sha": "6c046b69d29021524906109f18092363505ee222", "build_number": "105", "api": "1.0", "nailgun_sha": "6d1769b21819f8fb4195f1bd9c44c038721ae3d4", "production": "docker", "python-fuelclient_sha": "521c2491f7f04f31d8c85db68499cd193d4904e3", "astute_sha": "7e6e6f9188bd69c603853b10d4a55149363323cc", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "", "fuellib_sha": "769af7fe30225cd15638ea2e6dffaa286bc06da1"}}}, "auth_required": true, "api": "1.0", "nailgun_sha": "6d1769b21819f8fb4195f1bd9c44c038721ae3d4", "production": "docker", "python-fuelclient_sha": "521c2491f7f04f31d8c85db68499cd193d4904e3", "astute_sha": "7e6e6f9188bd69c603853b10d4a55149363323cc", "feature_groups": ["mirantis"], "release": "6.1", "fuelmain_sha": "", "fuellib_sha": "769af7fe30225cd15638ea2e6dffaa286bc06da1"

# re-generated by cloud-init boothook on every boot;
search domain.tld
domain domain.tld
nameserver 10.20.0.2

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.