Bug #1812449 “Containers: config_controller replaces custom name...” : Bugs : StarlingX

Revision history for this message

Erich Cordoba (ericho) wrote on 2019-01-18:

#1

The replacement of the configuration occurs when nameserver 192.168.204.2 is set.
On nameserver 8.8.8.8 the present configuration remains.

Ghada Khalil (gkhalil) on 2019-01-21

tags:	added: stx.containers
summary:	- config_controller replaces custom nameserver on /etc/resolv.conf + Containers: config_controller replaces custom nameserver on + /etc/resolv.conf
Changed in starlingx:
assignee:	nobody → Bart Wensley (bartwensley)

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2019-01-21:

#2

This is under discussion with the containers sub-team; will wait for their readout before deciding whether this is release gating or not.

Revision history for this message

Frank Miller (sensfan22) wrote on 2019-01-22:

#3

Since some community members require their own DNS server, we will need to provide this ability as part of config_controller at least in the short term. Issue assigned to Bart to implement.

Revision history for this message

Ghada Khalil (gkhalil) wrote on 2019-01-23:

#4

Marking as release gating based on comment above

tags:	added: stx.2019.05
Changed in starlingx:
status:	New → Triaged
importance:	Undecided → High
importance:	High → Medium

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2019-01-24: Fix proposed to stx-config (master)

#5

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

Changed in starlingx:
status:	Triaged → In Progress

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2019-01-24: Fix merged to stx-config (master)

#6

Reviewed: https://review.openstack.org/633002
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=d96ce5291c78c371e132813a514a1fb6e0994850
Submitter: Zuul
Branch: master

commit d96ce5291c78c371e132813a514a1fb6e0994850
Author: Bart Wensley <email address hidden>
Date: Thu Jan 24 07:22:05 2019 -0600

Allow DNS server configuration for kubernetes

    In kubernetes deployments, a DNS server is required to locate
    the registry servers used to download the kubernetes images.
    Currently, when config_controller is run, the 8.8.8.8
    nameserver is used, with no way to change it. Some users
    need to specify their own name server to be used during
    the execution of config_controller.

    This change allows the user to specify up to three DNS
    servers when running config_controller interactively or with
    a config file. If using a config file, add the following
    section to the config file (only one nameserver is required,
    but up to three are allowed):

    [DNS]
    NAMESERVER_1=8.8.8.8
    NAMESERVER_2=8.8.4.4
    NAMESERVER_3=9.9.9.9

    Change-Id: I59556138a11c6f627f45886a2da6b8a1ad9d89e1
    Closes-bug: 1812449
    Signed-off-by: Bart Wensley <email address hidden>

Changed in starlingx:
status:	In Progress → Fix Released

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2019-01-28: Related fix proposed to stx-config (master)

#7

Related fix proposed to branch: master
Review: https://review.openstack.org/633587

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2019-01-28: Related fix merged to stx-config (master)

#8

Reviewed: https://review.openstack.org/633587
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=c4f63232dc88bd8eae5698b104011cbc7d7f98ea
Submitter: Zuul
Branch: master

commit c4f63232dc88bd8eae5698b104011cbc7d7f98ea
Author: Bart Wensley <email address hidden>
Date: Mon Jan 28 13:17:00 2019 -0600

Ensure puppet dns config done after networking config

    In some labs, the puppet manifest application during
    config_controller results in the ::platform::network class
    being applied after the ::platform::dns class. This causes the
    /etc/resolv.conf file to be wiped (when the
    apply_network_config.sh is run by the ::platform::network
    class).

The fix is to introduce a dependency to ensure that the
networking config is completed before the dns config is done.

    Change-Id: Ie4a8b67e5eb3594f5c21e22f8014d2b8162a0758
    Related-bug: 1812449
    Signed-off-by: Bart Wensley <email address hidden>

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2019-01-29: Related fix proposed to stx-config (f/stein)

#9

Related fix proposed to branch: f/stein
Review: https://review.openstack.org/633788

Revision history for this message

OpenStack Infra (hudson-openstack) wrote on 2019-01-29: Related fix merged to stx-config (f/stein)

#10

Download full text (7.9 KiB)

Reviewed: https://review.openstack.org/633788
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=23f303132c9e69a16f2e0b1b63483c49fcfd11a1
Submitter: Zuul
Branch: f/stein

commit 3cc2f5e1fb70159473eefe4e5141db4eab8c92b0
Author: Al Bailey <email address hidden>
Date: Mon Jan 28 09:50:25 2019 -0600

Change version of python-ldap to work with new setuptools

setuptools 40.7.0 does not work with python-ldap 2.5.2

Added unit tests to verify the code calling the python-ldap
functions.

    Closes-Bug: 1813668
    Change-Id: I1e5c0bb7ec603d4d2e03032282e268cb2189775d
    Signed-off-by: Al Bailey <email address hidden>

commit c4f63232dc88bd8eae5698b104011cbc7d7f98ea
Author: Bart Wensley <email address hidden>
Date: Mon Jan 28 13:17:00 2019 -0600

Ensure puppet dns config done after networking config

    In some labs, the puppet manifest application during
    config_controller results in the ::platform::network class
    being applied after the ::platform::dns class. This causes the
    /etc/resolv.conf file to be wiped (when the
    apply_network_config.sh is run by the ::platform::network
    class).

The fix is to introduce a dependency to ensure that the
networking config is completed before the dns config is done.

    Change-Id: Ie4a8b67e5eb3594f5c21e22f8014d2b8162a0758
    Related-bug: 1812449
    Signed-off-by: Bart Wensley <email address hidden>

commit de474bc41c2691ba86b60bb6e1088ddc382deaa3
Author: Bart Wensley <email address hidden>
Date: Thu Jan 24 16:33:41 2019 +0000

Revert "Add docker proxy configuration for kubernetes".

This change broke the installation of kubernetes system (config_controller --kubernetes) when no docker proxy was specified.

This reverts commit e4086a073b7f661d4014061f25525120c27ea679.

Change-Id: I8343741a50fa0857fde9dfe0ee8f81de80a0ff13

commit d96ce5291c78c371e132813a514a1fb6e0994850
Author: Bart Wensley <email address hidden>
Date: Thu Jan 24 07:22:05 2019 -0600

Allow DNS server configuration for kubernetes

    In kubernetes deployments, a DNS server is required to locate
    the registry servers used to download the kubernetes images.
    Currently, when config_controller is run, the 8.8.8.8
    nameserver is used, with no way to change it. Some users
    need to specify their own name server to be used during
    the execution of config_controller.

    This change allows the user to specify up to three DNS
    servers when running config_controller interactively or with
    a config file. If using a config file, add the following
    section to the config file (only one nameserver is required,
    but up to three are allowed):

    [DNS]
    NAMESERVER_1=8.8.8.8
    NAMESERVER_2=8.8.4.4
    NAMESERVER_3=9.9.9.9

    Change-Id: I59556138a11c6f627f45886a2da6b8a1ad9d89e1
    Closes-bug: 1812449
    Signed-off-by: Bart Wensley <email address hidden>

commit f0b393f30952aa226976c33b9ff9241283fab207
Author: Kevin Smith <email address hidden>
Date: Thu Jan 17 07:09:35 2019 -0500

Kubernetes Neutron VIM Host Management Ref...

Reviewed:  https://review.openstack.org/633788
Committed: https://git.openstack.org/cgit/openstack/stx-config/commit/?id=23f303132c9e69a16f2e0b1b63483c49fcfd11a1
Submitter: Zuul
Branch:    f/stein

commit 3cc2f5e1fb70159473eefe4e5141db4eab8c92b0
Author: Al Bailey <Al.Bailey@windriver.com>
Date:   Mon Jan 28 09:50:25 2019 -0600

Change version of python-ldap to work with new setuptools
    
    setuptools 40.7.0 does not work with python-ldap 2.5.2
    
    Added unit tests to verify the code calling the python-ldap
    functions.
    
    Closes-Bug: 1813668
    Change-Id: I1e5c0bb7ec603d4d2e03032282e268cb2189775d
    Signed-off-by: Al Bailey <Al.Bailey@windriver.com>

commit c4f63232dc88bd8eae5698b104011cbc7d7f98ea
Author: Bart Wensley <barton.wensley@windriver.com>
Date:   Mon Jan 28 13:17:00 2019 -0600

Ensure puppet dns config done after networking config
    
    In some labs, the puppet manifest application during
    config_controller results in the ::platform::network class
    being applied after the ::platform::dns class. This causes the
    /etc/resolv.conf file to be wiped (when the
    apply_network_config.sh is run by the ::platform::network
    class).
    
    The fix is to introduce a dependency to ensure that the
    networking config is completed before the dns config is done.
    
    Change-Id: Ie4a8b67e5eb3594f5c21e22f8014d2b8162a0758
    Related-bug: 1812449
    Signed-off-by: Bart Wensley <barton.wensley@windriver.com>

commit de474bc41c2691ba86b60bb6e1088ddc382deaa3
Author: Bart Wensley <barton.wensley@windriver.com>
Date:   Thu Jan 24 16:33:41 2019 +0000

Revert "Add docker proxy configuration for kubernetes".
    
    This change broke the installation of kubernetes system (config_controller --kubernetes) when no docker proxy was specified.
    
    This reverts commit e4086a073b7f661d4014061f25525120c27ea679.
    
    Change-Id: I8343741a50fa0857fde9dfe0ee8f81de80a0ff13

commit d96ce5291c78c371e132813a514a1fb6e0994850
Author: Bart Wensley <barton.wensley@windriver.com>
Date:   Thu Jan 24 07:22:05 2019 -0600

Allow DNS server configuration for kubernetes
    
    In kubernetes deployments, a DNS server is required to locate
    the registry servers used to download the kubernetes images.
    Currently, when config_controller is run, the 8.8.8.8
    nameserver is used, with no way to change it. Some users
    need to specify their own name server to be used during
    the execution of config_controller.
    
    This change allows the user to specify up to three DNS
    servers when running config_controller interactively or with
    a config file. If using a config file, add the following
    section to the config file (only one nameserver is required,
    but up to three are allowed):
    
    [DNS]
    NAMESERVER_1=8.8.8.8
    NAMESERVER_2=8.8.4.4
    NAMESERVER_3=9.9.9.9
    
    Change-Id: I59556138a11c6f627f45886a2da6b8a1ad9d89e1
    Closes-bug: 1812449
    Signed-off-by: Bart Wensley <barton.wensley@windriver.com>

commit f0b393f30952aa226976c33b9ff9241283fab207
Author: Kevin Smith <kevin.smith@windriver.com>
Date:   Thu Jan 17 07:09:35 2019 -0500

Kubernetes Neutron VIM Host Management Refactoring
    
    Rework neutron system host management to operate on agent states
    rather than an extended host entity, as it was agreed with the
    neutron team that a new host level entity was not desired in the
    neutron core.
    
    This commit modifies the neutron override values to accommodate
    the above.
    
    Story: 2003857
    Task: 26669
    Depends-On: I441fcf3c186f68d17abafe337af71d0caf9c40da
    
    Change-Id: I85943d5b6f421f4ef379694f21ad2d758bb5f38a
    Signed-off-by: Kevin Smith <kevin.smith@windriver.com>

commit 386750136ccdb9d2b8240ccf68fc0f0258824939
Author: Sun Austin <austin.sun@intel.com>
Date:   Thu Jan 24 10:10:05 2019 +0800

[Devstack] remove etc/sysinv/crushmap.bin install in devstack
    
    https://review.openstack.org/#/c/629512/ removed crushamp.bin
    so remove this bin file in devstack accordingly.
    
    Depends-on: https://review.openstack.org/632897
    Change-Id: I743dd6de2c5351a2b3a6a5fb114360361429e664
    Signed-off-by: Sun Austin <austin.sun@intel.com>

commit e4086a073b7f661d4014061f25525120c27ea679
Author: Mingyuan Qi <mingyuan.qi@intel.com>
Date:   Thu Jan 17 22:42:50 2019 +0800

Add docker proxy configuration for kubernetes
    
    Current config_controller for containerization pulls kubernetes
    images from public container registry. This requires controller
    to access internet. If a host network is behind a proxy, there
    is no chance to setup docker proxy configuration during config_
    controller, therefore, kubernetes images are not accessible.
    
    Docker proxy configuration questions were added to require users
    input http/https proxy and no proxy settings. The docker proxy
    configurations are added to service_parameter table in sysinv.
    
    http-proxy.conf is the proxy info file required by docker daemon,
    generated by docker puppet manifest. It consists of the user
    input docker proxy configuration.
    
    Tests:
    AIO-SX: public k8s images accessible
    AIO-DX: public k8s images accessible
    AIO-SX without k8s config: config_controller successfully
    
    Story: 2004710
    Task: 28741
    
    Change-Id: I9d301d105f9fe5e388a29dee03957514b9b44fa7
    Signed-off-by: Mingyuan Qi <mingyuan.qi@intel.com>

commit 2b2782efb6ea2efc4816fe67287c8a0515916352
Author: sunausti <sunausti@starlingx.com>
Date:   Mon Jan 21 01:04:02 2019 +0000

Support 'True' and 'False' input for system commands
    
    add args choice 'True' and 'False' for https_enabled and sdn_enabled
    in 'system modify' and for dynamic in 'system network-add' command
    to support input 'True' and 'False'.
    
    make https_enabled and sdn_enabled to lower case in sys-api controller
    
    Closes-bug: 1812268
    
    Change-Id: If6411852edfc970ee1d749e4d4ccb8d045767bbc
    Signed-off-by: sunausti <sunausti@starlingx.com>

commit 1a502b9151fadb93ae6fdc667a72f978133ed9e5
Author: John Kung <john.kung@windriver.com>
Date:   Thu Jan 17 21:55:19 2019 -0500

Create DataNetworks modelling in System Configuration
    
    Introduce the DataNetwork api, client, model to allow modelling of the
    physical data network, with the following attributes:
       datanetwork_name
       mtu
       datanetwork_type (flat, vlan, vxlan)
       VxLAN specific attributes
          - port_number
          - multicast_group
          - ttl
          - mode ('dynamic' default, or 'static')
    
    The system data network may then be assigned to interface.
    
    This is part of the Story to "Move neutron provider network modelling
    to system configuration".
    
    The interface api is currently made compatible with current usage to
    allow specifying datanetwork (formerly providernetwork).
    
    The following new CLI commands and corresponding api are exposed:
        datanetwork-add     Add a datanetwork.
        datanetwork-delete  Delete a datanetwork.
        datanetwork-list    List datanetworks.
        datanetwork-modify  Modify a datanetwork.
        datanetwork-show    Show datanetwork details.
        interface-datanetwork-assign
                           Assign a datanetwork to an interface.
        interface-datanetwork-list
                           List datanetwork interfaces.
        interface-datanetwork-remove
                           Remove an assigned datanetwork from an interface.
        interface-datanetwork-show
                           Show interface datanetwork details.
    
    'system datanetwork-add' must be run where
        'neutron providernetwork-create'.
    
    Tests Performed:
        AIO Sanity
        Sanity 2-controller, 2-compute
        Sanity Storage lab
        Interface Profile create and apply
        Containers deployment
    
    Change-Id: I630f90768647dbb414a60978bf8f8f641496afd5
    Story: 2004455
    Task: 28324
    Signed-off-by: John Kung <john.kung@windriver.com>

tags:

added: in-f-stein

Ken Young (kenyis) on 2019-04-05

tags:

added: stx.2.0
removed: stx.2019.05

StarlingX

Containers: config_controller replaces custom nameserver on /etc/resolv.conf

Bug Description

Other bug subscribers

Remote bug watches