Public bug reported:
In new Launch Instance wizard, vertical margin between .form-groups is
zero, causing form field too close.
Steps to reproduce:
- Open new Launch Instance wizard.
- switch to Key Pare step
- click on `Import Key Pair` button, you will see the Public Key field is too
close
The expiration timer hasn't started for some reason.
** Changed in: neutron
Status: Incomplete = 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/1298355
Title:
Lock wait
Public bug reported:
neutronV20.find_resourceid_by_name_or_id() when used without the parent_id
parameter works . But in case we want to pass the parent_id to the method it
fails
with this error
_fx() takes exactly 0 arguments (3 given)
** Affects: python-neutronclient
Importance:
Public bug reported:
The following failures in test discovery were noted:
https://review.openstack.org/#/c/169962/
https://bugs.launchpad.net/neutron/+bug/1443480
It was eventually determined that the use of the unittest discovery
mechanism to perform manual discovery in package init for the
Public bug reported:
version: stable/icehouse from 2014.2.2 onwards (does not impact
stable/{juno|kilo})
nova-api fails to handle Not Authorized from neutron:
2015-04-20 00:49:29.399 22741 TRACE nova.api.openstack action_result =
self.dispatch(meth, request, action_args)
2015-04-20
** 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/1407721
Title:
Add range support to all address fields in
Haven't seen this in a while, marking as invalid
** Changed in: neutron
Status: Incomplete = 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/1313800
Title:
lock wait
no, we are not seeing this.
** Changed in: neutron
Status: Incomplete = 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/1313794
Title:
lock_wait timeout caused by
Public bug reported:
In the new Launch Instance wizard, first step, there are redundant
validation indicators for `Instance Name`. When the field is empty, it
will show a red asterisk AND a warning icon.
** Affects: horizon
Importance: Undecided
Status: Invalid
** Changed in:
[Expired for OpenStack Compute (nova) juno because there has been no
activity for 60 days.]
** Changed in: nova/juno
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
_create_namespace method was recently removed
(commit 7f7343b1afc0b1b953e5c36a753397a6d37316cb)
but still has a few users.
neutron/tests/functional/agent/linux/test_interface.py:namespace =
self._create_namespace()
neutron/tests/functional/agent/test_ovs_flows.py:
Public bug reported:
nova boot failed in spawn step, the ironic hypervisor show the
mem/cpu/disk resource still be occpied by the nova instance which is in
error status, I understand for such boot failed case, the ironic
hypervisor resource should be released once the boot is completed with
How can this be a bug if export is not even a implemented task yet?
** Changed in: glance
Status: New = Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1446286
Title:
Public bug reported:
In creating/updating firewall, it is not implemented tenant_id check in
validation.
Therefore, when executing following operation with admin privilege,
the error continues to tracing into neutron's log even the firewall has created.
[Operation]
1. Create
** 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://bugs.launchpad.net/bugs/1383465
Title:
[pci-passthrough] nova-compute fails to
Public bug reported:
As part of BP multiple IPv6 prefixes, we can have multiple IPv6 prefixes on
router internal ports. Patch, I7d4e8194815e626f1cfa267f77a3f2475fdfa3d1, adds
the necessary support for a legacy router.
For an HA router, instead of configuring the addresses on the router internal
Public bug reported:
In the file /var/log/apache2/horizon.error.log there are many lines that
are not errors:
[Fri Apr 17 14:49:32.604840 2015] [:error] [pid 28933:tid 140515448411904]
Login successful for user admin.
[Fri Apr 17 13:04:25.892490 2015] [:error] [pid 28933:tid 140515448411904]
Public bug reported:
Creating port with specifying both port_security_enabled=False and
security_groups=[] raises PortSecurityAndIPRequiredForSecurityGroups
Steps to reproduce:
1) Make sure that port security is enabled for ML2 (for DevStack
https://review.openstack.org/#/c/162063/)
2) create
I don't see any reason for this to be a Medium bug - there's
absolutely no negative impact described here. In fact, the documented
behavior is as-designed. To quote myself from the code review above:
The most obvious conflicting use case I can think of is having two
services of the same type in
Agree with fungi
** Changed in: ossa
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1435396
Title:
No notifications for role grants using v2
** Changed in: ossa
Status: Incomplete = 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/1445199
Title:
Nova user should not have admin role
Status in
Public bug reported:
In all the horizon docs, the conventions need to be updated per the doc
conventions wiki (see link below). This needs to be done for all the
docs throughout.
one of the pages that needs to be updated:
http://docs.openstack.org/developer/horizon/topics/policy.html
link to
** Changed in: ossa
Importance: Undecided = High
** Changed in: ossa
Status: Incomplete = Confirmed
** Also affects: neutron/kilo
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed
Public bug reported:
http://logs.openstack.org/21/174821/1/gate/gate-neutron-dsvm-
functional/eb6b441/console.html#_2015-04-20_07_41_14_649
This is happening quite often and is not just this specific test:
2015-04-20 07:41:14.649 | 2015-04-20 07:41:14.642 | {4}
** Changed in: pbr
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://bugs.launchpad.net/bugs/1415106
Title:
gate-tempest-dsvm-large-ops fails with RPC
Public bug reported:
Context and information:
--
Currently, 404 is seen by the user when image-delete call is made via the
Glance API or through the Images API of Nova for an Image in deleted status.
However, if an Image is in pending_delete and a user with
Public bug reported:
test_dvr_router_add_internal_network_set_arp_cache and
test_dvr_router_rem_fips_on_restarted_agent don't clean up after
themselves when run successfully.
** Affects: neutron
Importance: Undecided
Assignee: Assaf Muller (amuller)
Status: In Progress
**
Public bug reported:
On startup, the L3 agent looks for namespaces to clean that don't belong
to him, in order to minimize system resources (namespaces) in the
machine.
The fullstack tests run an l3 agent that after deletes some namespaces
that he doesn't know. This in turns causes the deletion
You've switched the status of this bug to indicate an exploitable
security vulnerability. Can you please clarify the conditions under
which this bug can be exploited by a malicious actor, and the extent of
the impact it implies?
** Also affects: ossa
Importance: Undecided
Status: New
** Also affects: keystone/kilo
Importance: Undecided
Status: New
** Changed in: keystone/kilo
Milestone: None = kilo-rc2
** Changed in: keystone/kilo
Status: New = In Progress
** Changed in: keystone/kilo
Importance: Undecided = Medium
--
You received this bug
Public bug reported:
Overview:
When a user attempts to export a deactivated image, the operation fails as
expected, but the message that is returned explaining why it failed is very
generic.
Steps to reproduce:
1) Import an image as user A
2) Deactivate the image as admin
3) Export the image
Reviewed: https://review.openstack.org/175219
Committed:
https://git.openstack.org/cgit/openstack/tempest/commit/?id=92b63aa8211b6a54f47c3ec2f1c77abf15017be8
Submitter: Jenkins
Branch:master
commit 92b63aa8211b6a54f47c3ec2f1c77abf15017be8
Author: Matt Riedemann mrie...@us.ibm.com
Date:
Public bug reported:
The L3 agent currently tries to delete a router by wrapping the delete
call in a try/except Exception block, but fails to log the caught
exception.
** Affects: neutron
Importance: Undecided
Assignee: Assaf Muller (amuller)
Status: In Progress
** Changed
33 matches
Mail list logo
