Public bug reported: provisioning_blocks are mostly used for compute port to notify that Neutron has done the networking settings, so VM can go power-on now. But now, Neutron does not check the port's device owner, it adds provisioning_block to all types of ports, even it is used by neutron.
For some internal service ports, neutron does not notify anything to neutron itself, but the provisioning_block may cause some timeout for resource setup. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1930432 Title: [L2] provisioning_block should be added to Neutron internal service port? Or should not? Status in neutron: New Bug description: provisioning_blocks are mostly used for compute port to notify that Neutron has done the networking settings, so VM can go power-on now. But now, Neutron does not check the port's device owner, it adds provisioning_block to all types of ports, even it is used by neutron. For some internal service ports, neutron does not notify anything to neutron itself, but the provisioning_block may cause some timeout for resource setup. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1930432/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp