DHCP Agent scheduled on locked host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Teresa Ho |
Bug Description
Brief Description
-----------------
STX: some Vms not reachable after DOR
The issue seems to be in the Neuton scheduling of dhcp agent.
Expected:
controller-0:~$ sudo cat /etc/neutron/
Password:
# in combination with network_
# network_
#network_
network_
in STX:
controller-1:~$ sudo cat /etc/neutron/
Password:
# in combination with network_
# network_
#network_
network_
host-based scheduler prevents scheduling on locked hosts which is missing in STX.
Severity
--------
Major
Steps to Reproduce
------------------
Install STX load
Launch an instance
Lock a host
perform DOR
Expected Behavior
------------------
All VMs become reachable after powering up all host.
Actual Behavior
----------------
Some VMs were not reachable.
Reproducibility
---------------
Only done once.
System Configuration
-------
2+4+20 ( any 2+2 should be fine)
Branch/Pull Time/Commit
-------
master as of 2018-10-10_20-18-00
The same behavior would happen in stx.2018.10 builds as well
Timestamp/Logs
--------------
Mon Oct 15 10:42:15 EDT 2018 (power on)
Mon Oct 15 14:55:28 2018 (1st VM pingable)
description: | updated |
description: | updated |
tags: |
added: stx.1.0 removed: stx.2018.10 |
It appears that some code was removed from the puppet neutron config in stx as part of the initial starlingx submission. It's not clear why that was done.
This line was changed :server: :network_ scheduler_ driver: 'neutron. scheduler. dhcp_host_ agent_scheduler .HostBasedSched uler' :server: :network_ scheduler_ driver: 'neutron. scheduler. dhcp_agent_ scheduler. WeightScheduler '
from:
neutron:
to:
neutron:
File Reference: https:/ /github. com/openstack/ stx-config/ blame/master/ puppet- manifests/ src/hieradata/ controller. yaml#L273
The plan is to put it back.
Note: The code required in stx-neutron to support this config is still there.