/+/944194
Severity is high. No functional issues but lots of alerts firing .
Logs
Neutron server error (last heartbeat is time of upgrade):
Agent healthcheck: found 1 dead agents out of 4:
Type Last heartbeat host
Metadata agent 2025-06-09 13:29:05 alex-aio-epoxy
Public bug reported:
We run OpenStack 2023.1 deployed via kolla.
After upgrading from Zed -> 2023.1 we are not able to migrate various instances
which have pci devices attached to it (Nvidia T4 GPU).
Nova-scheduler throws this Exception during pci filtering:
Exception during message handling:
** Project changed: horizon => ubuntu-ubuntu-server
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/2076216
Title:
Ubuntu 24.04 LTS kernel 6.8.0-35 fails to boot up
Public bug reported:
>From our observation this issue is specific to certain server platform on
>which we found 6.8.0-35/36 exhibits the same failure symptom, seems like
>6.8.0-39 works. On other server platforms 6.8.0-35/36/39 all boot up fine.
We'd like to understand the root cause so we can
Public bug reported:
As a openstack horizon user, when I upload a file to object store,
horizon does not show file upload progress bar. This matters when
uploading large file since users have no idea whether it is backend
issue or whether upload is in progress.
** Affects: horizon
Importance
Hello,
It's hard to say what project should be patched - but sudo rules on the
tripleowallaby / openstack-neutron-server has to be patched
Image itself is using neutron user and it doesn't seem to be able to run the
necessary commands to apply correct iptable rules
This in turn prevents deployme
** Also 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/2033683
Title:
openvswitch.agent.ovs_neutron_agent fails to Cmd: ['ipt
** Also affects: charm-keystone
Importance: Undecided
Status: New
** Changed in: keystone
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.l
Re-assigning to the keystone identity package.
** Also affects: keystone
Importance: Undecided
Status: New
** Changed in: keystone (Juju Charms Collection)
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is
Public bug reported:
Description
===
When deleting an instance that is shelved, delete action is not added to
instance action list.
Steps to reproduce
==
$ nova shelve
$ nova delete
$ nova instance-action-list
Expected result
===
delete action should show
** Changed in: charm-neutron-openvswitch
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1931696
Title:
ovs offload broken from neutron 16.3.0
Public bug reported:
On AWS EC2 (ECS-Optimized image), I have the following write_files
section:
write_files:
- path: "/home/ec2-user/cloud-provision-host.sh"
permissions: "0755"
owner: "ec2-user:ec2-user"
content: |
#!/usr/bin/env bash
I'm using the default AWS EC2 instance
Not a charm bug now.
** Changed in: charm-hacluster
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1118815
Title:
Remove python-oauth from the archive
** Changed in: charm-nova-cloud-controller
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/1259760
Title:
Spice console isn't working when s
Public bug reported:
We are using auto-install to PXE boot a number of ubuntu 20.04 hosts.
These hosts are physical servers. The hostname is set via DHCP, however
in the auto-install configuration file we set the identity to
"localhost".
We are also trying to boot strap these servers with chef. F
Public bug reported:
When the chef_license attribute is specified, the cloud-init run fails
to complete as the attribute is interpreted as a path. The suggested fix
for this is to move the attribute from CHEF_RB_TPL_PATH_KEYS to
CHEF_RB_TPL_DEFAULTS
CHEF_RB_TPL_DEFAULTS = {
# These are ruby
** Changed in: charm-keystone
Status: Fix Committed => Fix Released
** Changed in: charm-nova-cloud-controller
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (
** Changed in: charm-ovn-chassis
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1893656
Title:
[ovn] Limit the number of metadata workers
St
Public bug reported:
If the l3 agent is down on the new master node of keepalived all the
interfaces remain down so no packets can pass through the new router.
The replication scenario is the following:
1. Shut down all the l3 agents
2. Kill the keepalived process on the master node
3. Try to ac
Public bug reported:
Description
===
Using recent Ubuntu Stein Cloud Packages, we are observing random live-
migration crashes on the target host. Libvirt is having a SEGFAULT on
the qemu driver. Transferring block devices usually works without
issues. However, the following memory transf
.
Thank you!
** Affects: nova
Importance: Undecided
Assignee: Alex Deiter (deiter)
Status: New
** Changed in: nova
Assignee: (unassigned) => Alex Deiter (deiter)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
This was assigned CVE-2019-19687 and was fixed via
https://usn.ubuntu.com/4262-1/ in Ubuntu.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-19687
** Changed in: keystone (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
Public bug reported:
MaaS server used to wait for cloud-init on target reporting status.
It works well on Bionic desktop but failed on Focal desktop.
It might be caused by the ordering of systemd service because the network
service always is started after the cloud-init service.
Journalctl:
三
https://review.opendev.org/#/c/674133/
** Project changed: glance => python-glanceclient
** Changed in: python-glanceclient
Assignee: (unassigned) => Alex Schultz (alex-schultz)
** Changed in: python-glanceclient
Status: New => In Progress
--
You received this bug not
Public bug reported:
If a session object is not provided to the glance client, the HTTPClient
defined in glanceclient.common.http will create a session object. This
session object leaks open connections because it is not properly closed
when the object is no longer needed. This leads to a Resourc
On further debugging, it appears that there is an issue in horizon
(caused due to a change in keystone) with the use of a scoped tokens for
the admin user when multi-domain is enabled.
The scenario is as follows:
1. Multi domain is enabled.
2. The admin user is logged in with credentials using an
Public bug reported:
The vgpu is allocated by this method
https://github.com/openstack/nova/blob/8260979b71b29ce2666d37b3adc7c256482aa16d/nova/virt/libvirt/driver.py#L3235
That method list the assigned mdev by listing the libvirt domain.
But if there are two concurrent request come to this metho
fects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Alex Xu (xuhj)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compu
Public bug reported:
The glance-replicator is not usable in newer OpenStack Releases (using
Rocky here).
glance-replicator size controller:9292 --debug
2019-05-22 12:51:42.174 32480 DEBUG glance.cmd.replicator [-] Request: GET
http://controller:9292/v1/images/detail?is_public=None with headers
Adding tripleo because this is affecting our fedora28 containers when
deployed via an undercloud with ssl enabled.
** Also affects: tripleo
Importance: Undecided
Status: New
** Changed in: tripleo
Status: New => Incomplete
** Changed in: tripleo
Status: Incomplete => Tria
Public bug reported:
Similar to this bug https://bugs.launchpad.net/nova/+bug/1805767
Currently, the resize API doesn't parse the new flavor. It means if the
new flavor include different PCI request, it won't be processed.
** Affects: nova
Importance: Undecided
Status: New
--
You
ssaging.rpc.server
ComputeResourcesUnavailable: Insufficient compute resources: Requested instance
NUMA topology cannot fit the given host NUMA topology.
The host only has two numa nodes, but the request resizing to three
instance numa node still schedule to the host. And the move claim
re
>From a tripleo standpoint, it's a packaging issue in RDO. Additionally
newton is basically EOL so closing that out as won't fix.
** Changed in: tripleo
Status: New => Won't Fix
** Changed in: tripleo
Importance: Undecided => Medium
** Changed in: tripleo
Milestone: None => rocky-1
Public bug reported:
Queen
Assiging FIP when there is nor router between the external and internal
networks show " unknown error" instead of
"External network b6093932-a55d-4f9a-8af0-f6f953c3a443 is not reachable from
subnet 535a9a47-6797-454f-a1dc-eeda6ace87d8. Therefore, cannot associate Po
Public bug reported:
please assist i'm trying to verify glance installation on centos openstack pike
but it states...
as below
[root@controller ~]# openstack image create "cirros" --file
cirros-0.3.5-x86_64-disk.img --disk-format qcow2 --container-format bare
--public
401 Unauthorized: This ser
This is a really old bug and I don't think it applies to tripleo anymore
(if ever). Setting to invalid for tripleo.
** Changed in: tripleo
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Com
Public bug reported:
The allocations records aren't removed from the destination host which
failed to boot up the instance, after the instance are rescheduled in
another host, the allocation records for the failed host still exists.
** Affects: nova
Importance: Undecided
Status: New
can not reproduce this bug
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1703340
Title:
Login twice after 'se
(computenode1, sharedstorage1), (computenode2, sharedstorage1),
(computenode3) and (computenode3), a duplicated (computenodes) returned.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Tags: placement
** Changed in: nova
Assignee: (unassigned
associations with CUSTOM_TRAIT_A.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Changed in: nova
Assignee: (unassigned) => Alex Xu (xuhj)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscri
ss2
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: In Progress
** Tags: placement
** Changed in: nova
Assignee: (unassigned) => Alex Xu (xuhj)
** Tags added: placement
--
You received this bug notification because you are a member of Ya
Public bug reported:
The trait MISC_SHARES_VIA_AGGREGATE still may not found in the
functional test, even after the fix https://review.openstack.org/478564.
One of case:
http://logs.openstack.org/85/330285/83/check/gate-nova-tox-functional-py35-ubuntu-xenial/94a3627/testr_results.html.gz
29 hits
/openstack/nova/blob/3863eca0ac5a9437354288de673c831d5dc20f2e/nova/objects/resource_provider.py#L2364
in the code
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: In Progress
** Tags: placement
** Changed in: nova
Assignee: (unassigned) => Alex
/blob/68bbddd8aea8f8b2d671e0d675524a1e568eb773/nova/api/openstack/compute/server_groups.py#L166
Those should be fixed to cover the legacy v2 request, and back-port the
fix.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Changed in: nova
Ass
Public bug reported:
The network related quotas are deprecated in the quota-set API since
2.36.
(https://github.com/openstack/nova/blob/master/nova/api/openstack/compute/schemas/quota_sets.py#L49)
But still existed in the quota-class API.
https://github.com/openstack/nova/blob/master/nova/api/ope
This sounds a configuration mistake. ""Access denied for user 'nova'@'%'
to database 'nova_api_cell0'"
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
h
This needs to change the API response, so we need bump a new
microversion. And we need a nova-spec for this kind of API change. But
this is very low priority
** Changed in: nova
Status: In Progress => Confirmed
** Changed in: nova
Importance: Low => Wishlist
** Changed in: nova
As
Public bug reported:
We believe that each test should not depend on other tests.
python -m testtools.run neutron.tests.tempest.scenario.test_floatingip
Ran 4 tests in 139.164s
OK
python -m testtools.run
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSameNetwork.test_east_west
==
** Changed in: nova
Status: Triaged => Opinion
** Changed in: nova
Importance: Low => Wishlist
--
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/1579876
Title:
o
This already fixed by this feature patch
https://review.openstack.org/#/c/415142/
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bug
Seeing the issue again on ocata
** Changed in: neutron
Status: Expired => 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/1469498
Title:
LbaasV2 session persistence- Create an
Public bug reported:
Description of problem:
We need to documents that while create sub-port it should be created with
--mac-address PARENT_PORT_MAC_ADDERSS.
This is the correct networking config- on VM subIF and IF should have the same
mac and it is the default option. We need to match neutr
Public bug reported:
When I run the test (python -m testtools.run)
neutron.tests.tempest.scenario.test_trunk.TrunkTest.test_subport_connectivity
with rhel image and "cloud_user" user the test fails due to following :
Traceback (most recent call last):
File
"/home/centos/tempest-upstream/neutr
Importance: Undecided
Assignee: Alex Stafeyev (astafeye)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Alex Stafeyev (astafeye)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
ht
Public bug reported:
Description of problem:
While attempting to achieve even distribution of tiny instances across 31
compute nodes (Some with 64GiB and some with 128GiB of memory) I tried to use
the NumInstancesFilter to limit the number of instance per each compute to 2
instances. (Total lim
(evacuate.evacuate, "2.1", "2.12")
@validation.schema(evacuate.evacuate_v214, "2.14")
def _evacuate(self, req, id, body):
...
The is a gap between two validation.schema decorator.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
St
I think I understand that wrong after some testing. Probably _() return
unicode also, so that shouldn't be a problem.
Maybe exc.format_message() is really a old thing.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engi
Public bug reported:
In most of placement API code, we just put the exception into the error message
like this
https://github.com/openstack/nova/blob/d57ce1dda839865c8060458760fa27dbbd7e2aee/nova/api/openstack/placement/handlers/resource_class.py#L108
This is equal to str(exc). This won't works
** Changed in: tripleo
Status: Fix Released => In Progress
--
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/1649341
Title:
Undercloud upgrade fails with "Cell mappi
Public bug reported:
We have a lot of filters are pattern match.
There is list for exact match
https://github.com/openstack/nova/blob/df2fd4a252cecc1e1ef471c071e57526ddf65499/nova/db/sqlalchemy/api.py#L2221
Out of that list will be pattern match
https://github.com/openstack/nova/blob/df2fd4a252c
Public bug reported:
On attempting to execute nova boot, I get an sqalchemy error. For
example, the following command:
nova boot --image ebc4576e-aebd-4852-a8ea-47eb238d06f5 --flavor
m1.medium --availability-zone nova "Cirros1"
Get this error: ERROR (ClientException): Unexpected API Error. Pl
I input empty string, the nova api return 500.
The affected APIs are:
1. create_backup
2. server create with multiple create
3. networks
4. tenant_networks
** Affects: nova
Importance: Medium
Assignee: Alex Xu (xuhj)
Status: In Progress
** Project changed: ironic => nova
**
Public bug reported:
The Keystone token flush job can get into a state where it will never
complete because the transaction size exceeds the mysql galara
transaction size - wsrep_max_ws_size (1073741824).
Steps to Reproduce:
1. Authenticate many times
2. Observe that keystone token flush job run
tent-Type: application/json; charset=UTF-8
Content-Length: 123
X-Compute-Request-Id: req-1d511dd3-6882-443f-979b-e0812bd84f57
Date: Thu, 01 Dec 2016 05:59:58 GMT
That looks like strange. We can remove that header when 406 returned.
** Affects: nova
Importance: Low
Assignee: Alex Xu
Public bug reported:
The filtering of ip and ip6 is done in the python.
https://github.com/openstack/nova/blob/3cd2005523dc83b1cadc956c4f86385766aaf679/nova/compute/api.py#L2434
So all the instances dump from the db without paging
https://github.com/openstack/nova/blob/3cd2005523dc83b1cadc956c4f8
Public bug reported:
[stack@undercloud-0 ~]$ openstack network trunk delete trunk1
Failed to delete trunk with name or ID 'trunk1': Trunk
3b5c8493-7832-4501-a93f-65c5131512bb is currently disabled.
Neutron server returns request_ids: ['req-2ee037a3-6d2f-49fe-babb-cc9a4b2ce9dd']
1 of 1 trunks fail
Public bug reported:
Newton,
openstack-neutron-ml2-9.1.0-6.el7ost.noarch
openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
openstack-neutron-openvswitch-9.1.0-6.el7ost.noarch
openstack-neutron-common-9.1.0-6.el7ost.noarch
openstack-neutron-9.1.0-6.el7ost.noarch
[stack@undercloud-0 ~]$ o
Public bug reported:
Newton,
[root@controller-0 ~]# rpm -qa | grep neutron
python-neutron-lib-0.4.0-1.el7ost.noarch
puppet-neutron-9.4.2-1.el7ost.noarch
python-neutron-9.1.0-6.el7ost.noarch
openstack-neutron-ml2-9.1.0-6.el7ost.noarch
openstack-neutron-bigswitch-agent-9.40.0-1.1.el7ost.noarch
ope
Public bug reported:
Newton(ospd10)-
[stack@undercloud-0 ~]$ openstack network create int_net_parent
+---+--+
| Field | Value|
+---+
*** This bug is a duplicate of bug 1636485 ***
https://bugs.launchpad.net/bugs/1636485
** Changed in: python-neutronclient
Status: New => Invalid
** Project changed: python-neutronclient => neutron
** This bug has been marked a duplicate of bug 1636485
VLAN aware VM - VM can be boo
*** This bug is a duplicate of bug 1636484 ***
https://bugs.launchpad.net/bugs/1636484
** Changed in: python-neutronclient
Status: New => Invalid
** Project changed: python-neutronclient => neutron
** This bug has been marked a duplicate of bug 1636484
Vlan aware VM - assign FIP to
Public bug reported:
OSP10
We created 2 internal networks, net1 and net2, created port from each network,
port1 and port2.
The port1 one was created as trunnk and port2 one as subport with vlan tag.
We can boot VM with port2 - we should not allow that.
BR
** Affects: neutron
Importance: U
Public bug reported:
osp10
We crated:
External network.
2 internal networks- net1 and net2.
Port from each network - port1 and port2.
Trunk, configured with port1.
Trunk sub-port configured with port2.
Floating ip.
We booted a VM with port1 port and configured on the VM eth0 with
eth0.VLAN sub in
name is 'floatingip'. There is no '_'.
Due to this different name for the resource, there is no event send out
when floating ip updated.
** Affects: neutron
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Changed in: neutron
Assignee: (unassig
er of
volume snapshot and the number of image metadata, so there have a chance
to failed on quota. But the code won't rollbacked already created volume
snapshot.
** Affects: nova
Importance: Medium
Assignee: Alex Xu (xuhj)
Status: Confirmed
** Description changed:
- In t
Public bug reported:
Ran tempest, hit this error. I can't get to the system right now to get
additional info. If i can, i will add more info.
19:42:37
19:42:37 ==
19:42:37 Failed 1 tests - output below:
19:42:37 ==
19:42:37
19:42:37
tempest
return start_response(status, headers, exc_info)
TypeError: expected byte string object, value of type unicode found
This is due to the we have unicode in the response headers, in this case
the allow headers is unicode.
This is same as
https://groups.google.com/forum/?fromgroups=#!topic/
Public bug reported:
Tested ovs 2.5 OVS FW driver.
Could not run sctp traffic between VMs in the same tenant and network
after allowing ip protocol 132 (sctp) ingress and egress traffic in the
security group.
With iptables driver worked well.
Tested on rhel7.3
OSP10- Newton
2016-09-20 11:20:3
.
We should start again (or resume) the interrupted process at nova start
instead of set to error state the related instances.
** Affects: nova
Importance: Undecided
Assignee: Alex Szarka (xavvior)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Alex Sza
Public bug reported:
During our Puppet Openstack CI testing with tempest, we received an
error indicating a DB deadlock in the nova api.
http://logs.openstack.org/78/370178/1/check/gate-puppet-openstack-
integration-3-scenario001-tempest-ubuntu-
xenial/8c9eb76/console.html#_2016-09-16_19_28_57_52
allocation record won't be cleanup.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: Invalid
** Changed in: nova
Assignee: (unassigned) => Alex Xu (xuhj)
** Changed in: nova
Status: New => Invalid
--
You received this bug notificat
Public bug reported:
In the current RT, the migration case was consider as resource
consuming. But we didn't update any allocation record to Placement API.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Tags: placement
** Changed in:
the end of available
resource update.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: In Progress
** Changed in: nova
Assignee: (unassigned) => Alex Xu (xuhj)
--
You received this bug notification because you are a member of Yahoo!
Engineering T
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:
The image API already was deprecated after 2.35, due to it is proxy API
to glance. But the sub-resource image-metadata of image was forgotten to
deprecate.
** Affects: nova
Importance: Undecided
Assignee: Alex Xu (xuhj)
Status: New
** Changed in: nova
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:
The network work quota is configurable
https://github.com/openstack/nova/blob/master/nova/conf/api.py#L307 But
we forget enable network quota in the quota's update json-schema.
** Affects: nova
Importance: High
Assignee: Alex Xu (xuhj)
Status
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
+-+---
an the deleted
tenant objects without a user to feel anything ( The manual option should stay
available off-course )
BR
Alex
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
=
All instances should be still existed in the kvm.
Actual result
=
All instances are destroyed by nova-compute unfortunately.
** Affects: nova
Importance: Undecided
Assignee: alex (chinabjalex)
Status: New
** Changed in: nova
Assignee: (unassigned) =>
Public bug reported:
We created external network with admin user for tenantA.
$ neutron net-create admin-ext --provider:network_type=vxlan --router:external
--tenant_id=TENANTA_ID
The rbac policy was created with "*" in target_tenant attribute.
When creatin an external network for specific t
Ms on
this network. If the network was attached as internal interface on a
router and becomes external , there is a contrast between the network
role ( external) to network usage ( attached as internal )
BR
Alex
** Affects: neutron
Importance: Undecided
Status: New
--
You receive
Public bug reported:
When the internal network have ports in use, a rbac "access_as_external"
policy should not be allowed. We should have an error message explaining
that.
When we execute such an action, the "router:external" for the internal network
becomes "true"
neutron net-show 10567136-ed
Public bug reported:
If we have 50 tenants and we will want to expose the external network to 49 of
them, we will have to create 49 rbac rules.
IMHO it can be not so comfortable.
I believe we should make an option to exclude specific tenant/tenants
from being targeted by the rbac rule.
May be
Public bug reported:
If we have an external network, with default rbac policy, and even 1 tenant is
using this network, we can not delete the default rbac policy in order to
decide to which tenants this network will be exposed.
In this situation the network will be exposed to all tenants unless
1 - 100 of 261 matches
Mail list logo
