when a new port is created, the schedule_network in agentschedulers_db is called.
Since this network may already be hosted, it will directly return None in dhcp_agent_scheduler,
which cause the agentschedulers_db.schedule_network log a warning message.
This is really annoying and making users confused.
And, real warnings are already addressed in the real scheduler function.
which is neutron.scheduler.dhcp_agent_scheduler.ChanceScheduler.schedule by default.
Cherry-picked from 3ef877fc5a669659c2fa4bb2fc416d4a473c6ac5 in master.
Reviewed: https:/ /review. openstack. org/66586 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=a47fde6e7aa afda70a94d02595 9049b242fba36b
Committed: https:/
Submitter: Jenkins
Branch: stable/havana
commit a47fde6e7aaafda 70a94d025959049 b242fba36b
Author: chen-li <email address hidden>
Date: Tue Nov 12 09:17:17 2013 +0800
Remove the warning for Scheduling Network
when a new port is created, the schedule_network in agentschedulers_db is called. scheduler, _db.schedule_ network log a warning message.
Since this network may already be hosted, it will directly return None in dhcp_agent_
which cause the agentschedulers
This is really annoying and making users confused. scheduler. dhcp_agent_ scheduler. ChanceScheduler .schedule by default.
And, real warnings are already addressed in the real scheduler function.
which is neutron.
Cherry-picked from 3ef877fc5a66965 9c2fa4bb2fc416d 4a473c6ac5 in master.
Change-Id: I11bdbe47c2cc0f c45fb143970fb67 62678bc27e5
Closes-Bug: #1192786