some docker containers remain unconfigured
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Vladimir Kuklin |
Bug Description
deploy ISO, e.g.
{"build_id": "2014-05-
go into, e.g. cobbler and see:
# Cobbler generated configuration file for dnsmasq
# Sat May 3 21:14:26 2014
read-ethers
log-dhcp
log-queries
log-facility=LOCAL0
addn-hosts = /var/lib/
domain=domain.tld
dhcp-lease-max=1000
server=/domain.tld/
resolv-
dhcp-match=gpxe,175
interface=eth0
# This is one of the key options. dnsmasq tries to move out servername
# and PXE filename from special fields into DHCP options.
# Some old clients can't understand those DHCP options, so they
# will not be able to boot via PXE without this option enabled.
# For example gPXE will not work while iPXE works fine.
dhcp-no-override
dhcp-option=
dhcp-range=
dhcp-option=
pxe-service=
dhcp-boot=
dnsmasq is unconfigured for some reason
this leads to failure of PXE boot of slave nodes
Changed in fuel: | |
assignee: | Fuel Library Team (fuel-library) → Vladimir Kuklin (vkuklin) |
It seems the problem that the environment is snapshotted during system tests BEFORE all the puppet configuration of all the containers is finished, e.g. the one for cobbler.