** Also affects: openstack-ansible
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/1432873
Title:
Add FDB bridge entry fails if old entry not
Public bug reported:
[Thu Mar 19 18:57:12.158459 2015] [:error] [pid 4777:tid 139987244758784]
[Thu Mar 19 18:57:12.184901 2015] [:error] [pid 4777:tid 139987244758784] REQ:
curl -i --insecure
'http://1.2.3.4:8774/v2/b41a90047bef4e7d9031cc72d692a5c5/limits' -X GET -H
Accept: application/json
** Also affects: openstack-ansible
Importance: Undecided
Status: New
--
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/1451860
Title:
Attached volume migration
Public bug reported:
Currently it is possible to delete the glance images, even if instances are
still referencing it.
This is in particular an issue once you deleted the image and tried to
resize/migrate instances to a new host.
The new host can't download the image from glance and the
** Also affects: openstack-ansible
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/1293540
Title:
nova should make sure the bridge exists
Public bug reported:
Sporadically the neutron metadata agent seems to return 401 wrapped up in a 404.
For still unknown reasons, the metadata agents creates sporadically invalid v3
token requests
2016-02-26 13:34:46.486 33371 TRACE neutron.agent.metadata.agent
Unauthorized: {"error":
Marking neutron as affected since correcting the auth_url did not seem to fix
this reliable enough.
We observed still issues, especially growing metadata response with a 404
wrapped into a 401. The interesting part is that this error goes aways after
the neutron-metadata-agent restart but
Public bug reported:
Currently I suspect a race condition when creating neutron HA enabled
router and attaching router interfaces.
All of my router ports are stuck in build state but passing traffic.
If I pick one port from this router is shows it is still in BUILD state:
Back ports to liberty not necessary anymore due to the v2 fallback
issues we found at https://review.openstack.org/#/c/327960/
Setting liberty to invalid state.
** Changed in: openstack-ansible/liberty
Status: In Progress => Invalid
--
You received this bug notification because you are
** Changed in: openstack-ansible
Status: In Progress => Fix Committed
** Changed in: openstack-ansible
Status: Fix Committed => Fix Released
** Changed in: glance
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering
Assignee: Bjoern Teipel (bjoern-teipel)
Status: New
** Changed in: glance
Assignee: (unassigned) => Bjoern Teipel (bjoern-teipel)
** Summary changed:
- Ulimit settings missign for memcached_server role
+ Ulimit settings missing for memcached_server role
** Summary chan
where value like
'swift%5000/v2.0/glance_images%' and status='active';
After that all image downloads started working.
As a additional information, Keystone was running in a stock
configuration, Fernet with SQL identity back end.
Interestingly I did another upgrade to Liberty trying to reprodu
Public bug reported:
The SRIO functionality in Mitaka seems broken, all configuration options we
evaluated lead to
NovaException: Unexpected vif_type=binding_failed
errors, stack following.
We are currently using this code base, along with SRIOV configuration posted
here
Nova SHA
Adding Neutron since I believe the issue is the neutron-sriov-nic-agent
not building the port so that nova can allocate it for the instance.
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
Closing this out, after updating the ixgbe and ixgbevf driver I was able
"attach" VF ports on nova instances.
** Changed in: neutron
Status: Incomplete => Invalid
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
Based on commit
https://github.com/openstack/neutron/commit/9d573387f1e33ce85269d3ed9be501717eed4807,
the wsgi connection pool has been lowered to 100 threads, which is now a
problem for the neutron-ns-metadata-proxy spawned by the neutron-metadata-agent
and not passing
Public bug reported:
Description
===
Under Pike we are operating a /var/lib/nova/instances mounted on a clustered
Netapp A700 AFF. The share is mounted across the entire nova fleet of currently
29 hosts (10G networking) with ~ 720 instances.
We are mounting the share with standard NFS
Public bug reported:
Description
===
Instance flavors with Ephemeral/Swap disk configuration created under
Juno do not live migrate/migrate/resize cleanly due to a change in
Liberty as the naming scheme for these underlying disk have changed
around the file extension from
I do agree with the initial issue that this is bad design, especially if
nova and also horizon are displaying security groups for the instances
rather than neutron port.
Personally I would prefer that nova displays the security groups per
port, per instance.
** Also affects: nova
Importance:
19 matches
Mail list logo
