Public bug reported:
This is found at Kilo and Mitaka releases.
--admin-state-down argument should be --admin-state-up
I think this is not lbaas issue, but neutron CLI.
$ neutron help lbaas-member-update
usage: neutron lbaas-member-update [-h] [--request-format {json}]
Public bug reported:
Internal server error when query neutron network resources using --tags and
tags-any combination.
This is found at Mitaka release.
stack@falcon-devstack ~
$ net-list -c id -c name --tenant-id f900b2f993234d31b450ca58d0cae025 -c tags
+--+-
Public bug reported:
This is found at stable/mitaka release
According to networking API v2.0 extensions:
http://developer.openstack.org/api-ref/networking/v2-ext/index.html?expanded=add-a-tag-detail,confirm-a-tag-detail,remove-all-tags-detail,replace-all-tags-detail,remove-a-tag-detail#tag-extens
** Changed in: neutron
Status: New => Invalid
** Changed in: neutron-lbaas (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1594419
Title:
lb
comment at ovs_integration_bridge was inserted to lbaas config as it is,
and not removed by lbaas agent which causing problems.
ovs_integration_bridge = test-switch # nix-managed
after remove the comment, packets are forwarded.
Please close the bug.
** Changed in: neutron
Status: New =>
Public bug reported:
The latest neutron-lbaas stable/liberty repo, the loadbalancer VIP will
not forward http packets to its pool members.
http to pool members are OK, but http to loadbalancer VIP failed.
Look at the VIP's port security-group, and it is correctly wired to the
security-group-id.
same is true at policy creation time:
nicira@newton-devstack:~$ neutron qos-policy-create --description="3k
bw-limiter" --shared bw-limiter
Created a new policy:
+-+--+
| Field | Value|
+-+--
Public bug reported:
update policy 3k-bm-limiter as shared policy.
update policy 3k-bm-limiter with only name field, causing default field
shared=False being used.
Here is the console log:
nicira@newton-devstack:~$ neutron qos-policy-show 3k-bm-limiter
+-+---
Public bug reported:
problem is in Kilo neutron-lbaas branch.
monitor is attached a pool.
When pool and listener were deleted, not error reported that there is a
health-monitor associated to pool.
If all lbaas resoruces except health-monitor were deleted, health
monitor can not be deleted.
See
Public bug reported:
OS is Kilo.
A VM assigned multiple interfaces.
After successfully booted. The server_show command result (attached)
will show each interface's add, version and mac on the addresses
attributes.
However, the security_groups show a list of security_groups being
applied to the
Public bug reported:
neutron ext-list
show extra route (Neutron Extra Route) is configured.
But the Horizon dashboard network >> Routers >>
present no elements to add/del extra-route from a router.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug no
11 matches
Mail list logo
