** Also affects: kuryr
Importance: Undecided
Status: New
** Changed in: kuryr
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
** Changed in: kuryr
Status: New => In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineerin
** Also affects: kuryr-libnetwork
Importance: Undecided
Status: New
** Changed in: kuryr-libnetwork
Status: New => In Progress
** Changed in: kuryr-libnetwork
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
--
You received this bug notification because you
** Also affects: networking-ovn
Importance: Undecided
Status: New
** Changed in: networking-ovn
Status: New => In Progress
** Changed in: networking-ovn
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
--
You received this bug notification because you are a mem
** Also affects: tacker
Importance: Undecided
Status: New
** Changed in: tacker
Status: New => In Progress
** Changed in: tacker
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
--
You received this bug notification because you are a member of Yahoo!
Engineerin
** Also affects: shade
Importance: Undecided
Status: New
** Changed in: shade
Status: New => In Progress
** Changed in: shade
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
** No longer affects: shade
--
You received this bug notification because you are a
** Also affects: karbor
Importance: Undecided
Status: New
** Changed in: karbor
Status: New => In Progress
** Changed in: karbor
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
--
You received this bug notification because you are a member of Yahoo!
Engineerin
** Also affects: gnocchi
Importance: Undecided
Status: New
** Changed in: gnocchi
Status: New => In Progress
** Changed in: gnocchi
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
--
You received this bug notification because you are a member of Yahoo!
Engin
dHost or UnsupportedPolicyException,
there's nothing to do about Migration .
** Affects: nova
Importance: Undecided
Assignee: bailin.zhang (bailin-zhang)
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subsc
Public bug reported:
In version mitaka
for example:
1. a VM has two ports.
2. create two new ports
3. attach new ports to VM as soon as possible
4. the two new ports were attached to the VM,but there are only three ports in
the "network_info" of table "instance_info_caches"
Detail infomation:
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1578520
Title:
attache many port as soon as possible, some ports was los
Public bug reported:
When delete VM ,or detach port. the dns_name of port should be retained
,when it was assigned by the user
At this fix: https://bugs.launchpad.net/nova/mitaka/+bug/1572593. reset
dns_name directly.
** Affects: neutron
Importance: Undecided
Status: New
--
You r
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1553889
Title:
When an VM was deleted which a port belong to, T
Public bug reported:
1. Create a VM
2. attache many interface once,
3. look at the result, only one interface was attached.
for example
1. nova interface-list vmtest
++--+--+--+---+
|
ot;dns_name" is not
equal .
** Affects: neutron
Importance: Undecided
Assignee: bailin.zhang (bailin-zhang)
Status: New
** Changed in: neutron
Assignee: (unassigned) => bailin.zhang (bailin-zhang)
--
You received this bug notification because you are a member of
** Project changed: neutron => nova-project
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1553889
Title:
When an VM was deleted which a port belong to, The port can not be
assigned t
Public bug reported:
when neutron-openvswitch-agent is offline. we can migrate VM to this node
successfully.
but the port status is Down. and the binding:vif_type change into
"binding_failed"
for example:
1. we have two compute nodes. named tecs110, tecs164
2. create a VM with ovs por
Public bug reported:
When VM create failed (such as "_create_domain" execute failed), do
not unplug-ports. This bug hit all release/branch.
When create VM, it will update network_info at table "instance_info_caches".
But it will be delayed for some time.
when "_shutdown_instance", we can
** Project changed: nova-project => nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1553889
Title:
When an VM was deleted which a port belong to, The port can not b
18 matches
Mail list logo