Fuel for OpenStack

[Vbox] Scripts didn't change DNS setings in astyte.yaml and inside the cobbler container (dnsmasq)

Bug #1544241 reported by Serhii Ovsianikov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
High
Maksim Malchuk
Fuel for OpenStack 9.0
8.0.x
Fix Released
High
Maksim Malchuk
Fuel for OpenStack 8.0

Bug Description

1. After deploying the Fuel master node we have difference DNS settings on master node and inside cobbler container

[root@fuel ~]# cat /etc/dnsmasq.upstream
nameserver 172.18.208.44

[root@fuel ~]# grep DNS_UPSTREAM /etc/fuel/astute.yaml
"DNS_UPSTREAM": "8.8.8.8"

[root@fuel ~]# dockerctl shell cobbler cat /etc/dnsmasq.upstream
domain domain.tld
search domain.tld
nameserver 8.8.8.8

2. Restarting the network for the first time after installation gives the following error
[root@fuel ~]# service network restart
Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.
                                                           [FAILED]
Thereafter, restart of the network goes successful

[root@fuel ~]# cat /etc/fuel/version.yaml
VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "529"
  build_id: "529"
  fuel-nailgun_sha: "baec8643ca624e52b37873f2dbd511c135d236d9"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "e2d79330d5d708796330fac67722c21f85569b87"
  fuel-ostf_sha: "3bc76a63a9e7d195ff34eadc29552f4235fa6c52"
  fuel-mirror_sha: "fb45b80d7bee5899d931f926e5c9512e2b442749"
  fuelmenu_sha: "e071216cb214e34b4d861478033425ee6a54a3be"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "a365f05b903368225da3fea9aa42afc1d50dc9b4"

Serhii Ovsianikov (sovsianikov)
summary: - [Vbox] Scripts didn't change DNS setings in astyte.yaml and insine the
+ [Vbox] Scripts didn't change DNS setings in astyte.yaml and inside the
cobbler container (dnsmasq)
Maksim Malchuk (mmalchuk)
Changed in fuel:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Maksim Malchuk (mmalchuk)
milestone: none → 9.0
status: Confirmed → In Progress
tags: added: team-bugfix vbox-scripts
tags: added: area-library
Revision history for this message
Eugene Bogdanov (ebogdanov) wrote :

This bug doesn't affect the codebase, yet it must be fixed prior to release.

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

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

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

Reviewed: https://review.openstack.org/279203
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=92a0e0b978cdcf60c593824a4c5ad7144fe401bb
Submitter: Jenkins
Branch: master

commit 92a0e0b978cdcf60c593824a4c5ad7144fe401bb
Author: Maksim Malchuk <email address hidden>
Date: Mon Feb 8 17:36:43 2016 +0300

    VirtualBox network fixes and the dockerless mode support

    This commit include changes:

     * using the VirtualBox scripts the Fuel master node now always
       booted with kernel option 'wait_for_external_config=yes' to
       provide the same deployment functionality as in the 'fuel-qa'.

     * settings for the kernel command line moved to the top config
       file, because the settings wich could be edited should be placed
       there.

     * because of configuration task moved to the correct place there
       is no need to parse 'bootstrap_admin_node.log' and always follow
       the changes in the 'fuel-library', so all parsing logic removed
       from the scripts. This also simplifies networking changes and
       there is no need to patch the files on the fly and restart
       docker containers if they used.

     * variable 'vm_master_nat_gateway' removed from the 'config.sh'
       and from the 'enable_outbound_network_for_product_vm' because
       gateway should be set from the DHCP lease.

     * the sysconfig configuration files on the fuel master node now
       configured the right way. the backup files for configuration
       files are created. also added some comments for changes in the
       scripts.

     * now the default routing on the fuel master node correctly
       configured without creating the second default route. also
       ZeroConf route creation and NetworkManager now switched off
       to correct work of the network service.

     * the 'resolv.conf', 'dnsmasq.upstream' and 'astute.yaml' now
       correctly modified and could contain up to three DNS nameservers.

     * added support for the new dockerless 9.0 Fuel.

    Implements blueprint: get-rid-docker-containers

    Change-Id: I8f32fb8105d0781938757fa13d5dcbbacbf9c845
    Closes-Bug: #1544241
    Partial-Bug: #1323365

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

Fix proposed to branch: stable/8.0
Review: https://review.openstack.org/280256

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

Reviewed: https://review.openstack.org/280256
Committed: https://git.openstack.org/cgit/openstack/fuel-main/commit/?id=643a1ef27c7dccc1c2a2ad26b85c09226b35a67d
Submitter: Jenkins
Branch: stable/8.0

commit 643a1ef27c7dccc1c2a2ad26b85c09226b35a67d
Author: Maksim Malchuk <email address hidden>
Date: Mon Feb 8 17:36:43 2016 +0300

    VirtualBox network fixes and the dockerless mode support

    This commit include changes:

     * using the VirtualBox scripts the Fuel master node now always
       booted with kernel option 'wait_for_external_config=yes' to
       provide the same deployment functionality as in the 'fuel-qa'.

     * settings for the kernel command line moved to the top config
       file, because the settings wich could be edited should be placed
       there.

     * because of configuration task moved to the correct place there
       is no need to parse 'bootstrap_admin_node.log' and always follow
       the changes in the 'fuel-library', so all parsing logic removed
       from the scripts. This also simplifies networking changes and
       there is no need to patch the files on the fly and restart
       docker containers if they used.

     * variable 'vm_master_nat_gateway' removed from the 'config.sh'
       and from the 'enable_outbound_network_for_product_vm' because
       gateway should be set from the DHCP lease.

     * the sysconfig configuration files on the fuel master node now
       configured the right way. the backup files for configuration
       files are created. also added some comments for changes in the
       scripts.

     * now the default routing on the fuel master node correctly
       configured without creating the second default route. also
       ZeroConf route creation and NetworkManager now switched off
       to correct work of the network service.

     * the 'resolv.conf', 'dnsmasq.upstream' and 'astute.yaml' now
       correctly modified and could contain up to three DNS nameservers.

     * added support for the new dockerless 9.0 Fuel.

    Implements blueprint: get-rid-docker-containers

    Change-Id: I8f32fb8105d0781938757fa13d5dcbbacbf9c845
    Closes-Bug: #1544241
    Partial-Bug: #1323365
    (cherry picked from commit 92a0e0b978cdcf60c593824a4c5ad7144fe401bb)

ElenaRossokhina (esolomina)
tags: added: on-verification
Revision history for this message
Anastasia Palkina (apalkina) wrote :
Download full text (3.3 KiB)

Verified on ISO #529

VERSION:
  feature_groups:
    - mirantis
  production: "docker"
  release: "8.0"
  api: "1.0"
  build_number: "529"
  build_id: "529"
  fuel-nailgun_sha: "baec8643ca624e52b37873f2dbd511c135d236d9"
  python-fuelclient_sha: "4f234669cfe88a9406f4e438b1e1f74f1ef484a5"
  fuel-agent_sha: "658be72c4b42d3e1436b86ac4567ab914bfb451b"
  fuel-nailgun-agent_sha: "b2bb466fd5bd92da614cdbd819d6999c510ebfb1"
  astute_sha: "b81577a5b7857c4be8748492bae1dec2fa89b446"
  fuel-library_sha: "e2d79330d5d708796330fac67722c21f85569b87"
  fuel-ostf_sha: "3bc76a63a9e7d195ff34eadc29552f4235fa6c52"
  fuel-mirror_sha: "fb45b80d7bee5899d931f926e5c9512e2b442749"
  fuelmenu_sha: "e071216cb214e34b4d861478033425ee6a54a3be"
  shotgun_sha: "63645dea384a37dde5c01d4f8905566978e5d906"
  network-checker_sha: "a43cf96cd9532f10794dce736350bf5bed350e9d"
  fuel-upgrade_sha: "616a7490ec7199f69759e97e42f9b97dfc87e85b"
  fuelmain_sha: "a365f05b903368225da3fea9aa42afc1d50dc9b4"

[root@fuel ~]# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        inet 172.17.42.1 netmask 255.255.0.0 broadcast 0.0.0.0
        ether 02:42:52:e6:d0:c0 txqueuelen 0 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 10.20.0.2 netmask 255.255.255.0 broadcast 10.20.0.255
        inet6 fe80::a00:27ff:fe58:3ada prefixlen 64 scopeid 0x20<link>
        ether 08:00:27:58:3a:da txqueuelen 1000 (Ethernet)
        RX packets 184433 bytes 14970783 (14.2 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 1405862 bytes 2105630511 (1.9 GiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 172.16.0.1 netmask 255.255.255.0 broadcast 172.16.0.255
        inet6 fe80::a00:27ff:fe0c:1850 prefixlen 64 scopeid 0x20<link>
        ether 08:00:27:0c:18:50 txqueuelen 1000 (Ethernet)
        RX packets 283 bytes 96786 (94.5 KiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 12 bytes 888 (888.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.200.15 netmask 255.255.255.0 broadcast 192.168.200.255
        inet6 fe80::a00:27ff:fe15:9f10 prefixlen 64 scopeid 0x20<link>
        ether 08:00:27:15:9f:10 txqueuelen 1000 (Ethernet)
        RX packets 280334 bytes 262144241 (250.0 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 84446 bytes 5224074 (4.9 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 0 (Local Loopback)
        RX packets 34886 bytes 24182557 (23.0 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 34886 bytes 24182557 (23.0 MiB)
        TX errors 0 dropped 0 overr...

Read more...

ElenaRossokhina (esolomina)
tags: removed: on-verification
TatyanaGladysheva (tgladysheva)
tags: added: on-verification
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Verified on:
[root@fuel ~]# shotgun2 short-report
cat /etc/fuel_build_id:
 459
cat /etc/fuel_build_number:
 459
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0

Actual result:
[root@fuel ~]# cat /etc/dnsmasq.upstream
domain domain.tld
search domain.tld
nameserver 172.18.176.6
[root@fuel ~]# grep DNS_UPSTREAM /etc/fuel/astute.yaml
"DNS_UPSTREAM": "172.18.176.6"
[root@fuel ~]# service network restart
Restarting network (via systemctl): [ OK ]
[root@fuel ~]# ifconfig
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
        inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
        ether 02:42:b9:d4:a6:47 txqueuelen 0 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 10.20.0.2 netmask 255.255.255.0 broadcast 10.20.0.255
        inet6 fe80::a00:27ff:fef0:5e4b prefixlen 64 scopeid 0x20<link>
        ether 08:00:27:f0:5e:4b txqueuelen 1000 (Ethernet)
        RX packets 103088 bytes 10607578 (10.1 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 646306 bytes 958739399 (914.3 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 172.16.0.1 netmask 255.255.255.0 broadcast 172.16.0.255
        inet6 fe80::a00:27ff:fe37:c939 prefixlen 64 scopeid 0x20<link>
        ether 08:00:27:37:c9:39 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 24 bytes 1776 (1.7 KiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        inet 192.168.200.15 netmask 255.255.255.0 broadcast 192.168.200.255
        inet6 fe80::a00:27ff:fe54:7257 prefixlen 64 scopeid 0x20<link>
        ether 08:00:27:54:72:57 txqueuelen 1000 (Ethernet)
        RX packets 223002 bytes 278700179 (265.7 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 43433 bytes 2749675 (2.6 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
        inet 127.0.0.1 netmask 255.0.0.0
        inet6 ::1 prefixlen 128 scopeid 0x10<host>
        loop txqueuelen 0 (Local Loopback)
        RX packets 31979 bytes 22058523 (21.0 MiB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 31979 bytes 22058523 (21.0 MiB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

tags: removed: on-verification
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.
Subscribing...

Other bug subscribers

Remote bug watches

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