Public bug reported:
Fullstack tests use create_all() function to make db schema. This is
done based on loaded models. Neutron dropped using create_all() in Juno
and relies strictly on db migration scripts. Even though there should be
parity in create_all() and migration scripts, we possibly test
Public bug reported:
The instance delete code paths were changed to use new-world bdm objects
in commit f5071bd1ac00ed68102d37c8025d36df6777cd9e.
However, cells code still use the legacy format for local delete
operations which is clearly wrong. Code that gets called in the parent
class in
** Project changed: neutron = trove
** Changed in: trove
Status: New = Confirmed
** Tags added: low-hanging-fruit
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1486454
Title:
Public bug reported:
support was added in https://review.openstack.org/#/c/136931/ to be able
to specify and use the standard session and auth plugin helpers from
keystoneclient to standardize the options available for talking to
neutron.
However, both in Kilo nor in Master now, these config
Public bug reported:
Orchestration Stacks has no button descriptions in russian language for
Check Stack, Suspend Stack, Resume Stack, Delete Stack.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Public bug reported:
If the CSP is using manually tagging specific tenant networks to follow
specific qos profiles, a tenant could use
neutron port-update port-id --no-qos-policy
or
neutron net-update net-id --no-qos-policy
to shake it of
A possible solution, is not allowing tenants to
Public bug reported:
Creating a new router, attaching it to some tenant network and then
adding a gateway for the router doesn't create the snat resources (such
as 'snat-%s' namespace and other interfaces).
Adding a gateway first (before attaching the router to a tenant network)
creates the snat
Public bug reported:
According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html ,
this header doesn't seem to be used at Forbidden case(40X).
The Retry-After response-header field can be used with a 503 (Service
Unavailable)
response to indicate how long the service is expected to be
Public bug reported:
networking-calico will very shortly provide an ML2 mechanism driver,
DHCP agent interface driver and Devstack plugin to demonstrate the
Calico project's idea of using routing - rather than bridging - to
provide IP-level connectivity between VMs.
The existing Neutron DHCP
Public bug reported:
Fully decompose the ML2 Nuage driver to the vendor repo,
so there is no code in the Neutron repo.
** Affects: neutron
Importance: Undecided
Assignee: Vlad Gridin (vladyslav-gridin)
Status: New
** Tags: nuage
** Changed in: neutron
Assignee:
Public bug reported:
http://developer.openstack.org/api-ref-identity-v3.html
All of the HEAD calls listed in the Identity API v3 give 200 as their
normal response codes. However in practice keystone seems to return 204
No Content as a normal response code for HEAD calls, which is more
correct.
** Project changed: keystone = openstack-api-site
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1486739
Title:
Identity API v3 showing wrong normal response codes for HEAD calls
Public bug reported:
When i create an image (which is public) and submit the form. The image
list defaults back to the project image list rather than the public
image list. It should stay on the public image list
** Affects: horizon
Importance: Undecided
Status: New
--
You
Public bug reported:
Simple fix:
In nova.test.unit.compute.test_compute.py
def test_detach_unattached_volume(self):
# Ensure exception is raised when volume's idea of attached
# instance doesn't match.
fake_instance = self._fake_instance({'uuid': 'uuid1',
Public bug reported:
Problem Description
Notify L3 agent when create or update port in _dvrscheduler_db.py.
Why use notify all L3 agent rather than specify L3 agent?
Proposed Change
===
Notify specify L3 agent instead of fanout.
** Affects: neutron
+1 We don't need to track the spelling mistakes. Just create a patch
** Changed in: nova
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
the follow bug is similar with this one, so i think this time is also a bug.
https://bugs.launchpad.net/nova/+bug/1486425
** This bug is no longer a duplicate of bug 1486425
misspelling in the documentation “Compute API v2 (SUPPORTED)”
** Summary changed:
- mistake in the documentation
Public bug reported:
Problem Description
===
Now, neutron server will fanout the message to all L3 agents
when a floatingip associate to a port. Does it necessary? Every
L3 agents store their own floatingips. I think it is unnecessary to
fanout all L3 agents.
Proposed Change
Public bug reported:
Problem Description
=
1. Create an instance, fixed_ip is allocating by dhcp agent.
2. Associate a floating_ip to the instance, then ssh or ping floating_ip.
3. Delete the instance, floating_ip is disassociated.
4. Create another instance,
Public bug reported:
L2population has a check to make sure the mac address of an active port
hasn't changed.[1] However, this check occurs in post commit so any
exception it throws doesn't stop anything.
1.
Public bug reported:
download the lastest devstack, and use './stack.sh' to install the OpenStack.
Error happens as follow:
2015-08-19 06:03:51.039 | + is_service_enabled ldap
2015-08-19 06:03:51.050 | + return 1
2015-08-19 06:03:51.050 | + recreate_database keystone
2015-08-19 06:03:51.050 |
Public bug reported:
The show_multiple_locations configuration option should be included in
the sample glance-api.conf that is shipped with glance packages.
Otherwise it is not clear in which config section this option belongs.
** Affects: glance
Importance: Undecided
Status: New
Public bug reported:
when service_plugins is configured with multi same value,neutron-server cannot
be started,
service_plugins is assigned with much variable,the same variable should be
ignored instead of raise error,
for the error is not important .
** Affects: neutron
Importance:
Public bug reported:
Problem Description
===
agent needs to resync with neutron server for some kind of reasons time to time.
These syncs will consume lots of resources for neutron server, database,
message queues etc.
Proposed Change
===
add update timestamp to
Public bug reported:
Hi,
I got this weird Tempest run here:
http://logs.openstack.org/35/206935/1/gate/gate-tempest-dsvm-neutron-
full/ef5a1a9/console.html#_2015-08-18_18_20_26_980 where the server has
OS-EXT-STS:vm_state: active and OS-EXT-STS:power_state: 3.
Power_state 3 is PAUSED according
Public bug reported:
A lot of database indexes are created for mysql in db migrating file
216_havana.py (see mysql_pre_indexes), and the part of indexes are added
in 271_sqlite_postgresql_indexes.py in order to keep the consistence
between mysql and other databases, but it still exists some
Public bug reported:
hi,
Keystone doesn't work well with default setup in KILO release.
The OpenStack documentation says to use the V3 API in rc files which
makes the keystone to fail. here is an extraction..
root@controller:~# keystone tenant-list
Authorization Failed: The resource could
Public bug reported:
Instance destroy and Instance snapshot are locking operations, meaning
that they can only occur sequencially. This is the result of the bugfix
for https://bugs.launchpad.net/nova/+bug/1461970 .
The problem is that the destroy instance can occur before snapshoting,
resulting
Public bug reported:
A job in the Ironic gate gate-tempest-dsvm-ironic-pxe_ssh-postgres is
broken due some change in Neutron which is affecting the Postgres
database backend.
The error is:
2015-08-19 03:23:38.802 ERROR oslo_db.sqlalchemy.exc_filters
[req-61b2cae0-f5a2-420e-b2ab-e3db3e3b00da
Public bug reported:
Neutron events have been added to nova. If the event network-vif-
unplugged is received, the nova compute manager will proceed to call
the compute driver's detach_interface method. The mentioned method is
not implemented in the HyperVDriver, causing errors. See log.
LOG:
Public bug reported:
in file cinder\api\contrib\cgsnapshots.py, comments of the code is not
capitalized at the beginning and the other places always be capitalized.
in cinder\api\contrib\cgsnapshots.py:
Line 198: cgsnapshots support.
the word [cgsnapshots ] should be capitalized.
** Affects:
Public bug reported:
in file cinder\api\contrib\consistencygroups.py, comments of the code is
not capitalized at the beginning and the other places always be
capitalized.
in cinder\api\contrib\consistencygroups.py:
Line 352: consistency groups support.
the word [consistency ] should be
Public bug reported:
http://developer.openstack.org/api-ref-compute-v2.html #1.4.5. Update server
There is a misspelling in the Description of Request parameter
“auto_disk_config (Optional)” .
Now:
Defines how the server's root disk partition is handled when the server is
started or
** Project changed: neutron = cinder
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1486418
Title:
Comments of the code should be capitalized at the beginning
Status in Cinder:
New
Public bug reported:
Removing version of API for bookmark URL is wrong
Function remove_version_from_href() receives SCRIPT_NAME.
SCRIPT_NAME consists of concatenation of Apache(or other web server) alias and
URL mapping from api-paste.conf. This concatenation is executed in
`keystone` CLI doesn't work with v3. You need to either use v2 or use
python-openstackclient (`openstack` CLI).
** Changed in: keystone
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
Public bug reported:
http://developer.openstack.org/api-ref-compute-v2.html #1.4.5. Update
server
There is a mistake in the Description of Request parameter
“auto_disk_config (Optional)” .
Now:
True. The root partition expands to encompass all available virtual disk.
Change the context
** Also affects: horizon
Importance: Undecided
Status: New
--
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/1486745
Title:
unscoped_token not hashed
** Project changed: neutron = 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/1486425
Title:
misspelling in the documentation “Compute API v2 (SUPPORTED)”
Status
39 matches
Mail list logo
