CFM: ZTP: dhcp_server_1 container is stuck in the restarting phase
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R5.0 |
Won't Fix
|
Medium
|
Rishabh Tulsian | |||
Trunk |
In Progress
|
Medium
|
Rishabh Tulsian |
Bug Description
Contrail Version: ocata-5.0-270
Contrail-
I deployed an all-in-one contrail cluster for ZTP with the flags for dhcp and tftp containers. The provision has gone through but the dhcp container is stuck in the restarting phase.
This is the error from the docker logs:
Internet Systems Consortium DHCP Server 4.2.5
Copyright 2004-2013 Internet Systems Consortium.
All rights reserved.
For info, please visit https:/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Wrote 0 leases to leases file.
No subnet declaration for pkt0 (no IPv4 addresses).
** Ignoring requests on pkt0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface pkt0 is attached. **
No subnet declaration for docker0 (172.17.0.1).
** Ignoring requests on docker0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface docker0 is attached. **
No subnet declaration for vhost0 (10.87.69.131).
** Ignoring requests on vhost0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface vhost0 is attached. **
No subnet declaration for eth0 (no IPv4 addresses).
** Ignoring requests on eth0. If this is not what
you want, please write a subnet declaration
in your dhcpd.conf file for the network segment
to which interface eth0 is attached. **
Not configured to listen on any interfaces!
This version of ISC DHCP is based on the release available
on ftp.isc.org. Features have been added and other changes
have been made to the base software release in order to make
it work better with this distribution.
Please report for this software via the CentOS Bugs Database:
http://
exiting.
I spoke to Rishabh about this, this is because we do have dhcp subnet configured for now. He told me that the container would be restarted with the new config after the ztp process is started from the UI. We should have this detail mentioned in the release document.
tags: | added: fabric releasenote ztp |
information type: | Proprietary → Public |
This should be targeted with 5.1 fix. Where dhcp and tftp would be part ztp micro service architecture.