Revision history [back]

click to hide/show revision 1
initial version

Hello Sam,

When a new port is created (new instance will create a new for most case), the schedule_network in agentschedulers_db is called, and since this network may already hosted (already launch instance on that network), it will directly return None in dhcp_agent_scheduler, which cause the agentschedulers_db.schedule_network treats it as a problem and log a warning message.

Actually it is a bug because it treats a normal situation same as a real problem

BR, Peter

Hello Sam,

When a new port is created (new instance will create a new for most case), the schedule_network in agentschedulers_db is called, and since this network may already hosted (already launch instance on that network), it will directly return None in dhcp_agent_scheduler, which cause the agentschedulers_db.schedule_network treats it as a problem and log a warning message.

Actually it is a bug because it treats a normal situation same as a real problem

BR, Peter