Local FIP not created after central FIP creation
Bug #1691918 reported by
Zhiyuan Cai
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tricircle |
Fix Released
|
Undecided
|
Zhiyuan Cai | ||
Bug Description
After booting a VM, we associate a FIP to it via central Neutron. However, local FIP is not created as expected. Also, there is no related asynchronous job registered.
The reason may be that we don't trigger asynchronous job in "create_floatingip" method, and since VM is already there, there's no chance to trigger the job.
| Changed in tricircle: | |
| assignee: | nobody → Zhiyuan Cai (luckyvega-g) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tricircle (master) | #1 |
| Changed in tricircle: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tricircle 3.4.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 9897c65a2608bc9
Author: zhiyuan_cai <email address hidden>
Date: Thu May 18 16:38:26 2017 +0800
Local FIP not created after central FIP creation
1. What is the problem
After booting a VM, we associate a FIP to it via central Neutron.
However, local FIP is not created as expected. Also, there is no related
asynchronous job registered.
The reason may be that we don't trigger asynchronous job in
"create_
chance to trigger the job.
2. What is the solution for the problem
If "port_id" is specified in the body, trigger asynchronous job.
3. What features need to be implemented to the Tricircle to
realize the solution
Support creating FIP with "port_id" specified.
Change-Id: Iceb15f68acc23f
Closes-Bug: #1691918