[IBP] wrong resolv.conf settings
Bug #1416399 reported by
Alexander Gordeev
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) |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/152560 /git.openstack. org/cgit/ stackforge/ fuel-web/ commit/ ?id=8286437ef2b 76c7b2cb24b3eb5 88bb14178caf9e
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8286437ef2b76c7 b2cb24b3eb588bb 14178caf9e
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 28d39f5e6ce4136 372db3172c5
Change-Id: I3d6fdd15ea2799