Public bug reported:
Currently, the default setting is
'/etc/keystone/ssl/certs/signing_cert.pem' which is the public key
certificate which contains,
- Signature Algorithm
- Public Key
- Signature Algorithm
- Subject
etc.
But sigver.read_cert_from_file expects the certificate's content
holds
don;t see this issue on kilo setup , so close it
** 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/1498472
Title:
lbaas:after
This is expected behavior. That config value is to influence the
automatic scheduling. It shouldn't interfere with manual scheduling by
an admin.
** Changed in: neutron
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
I suspect Neutron is involved
** 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/1507558
Title:
Ironic gate breakage:
Public bug reported:
File
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py",
line 96, in run
for _state in self.run_iter():
File
"/usr/lib/python2.7/site-packages/taskflow/engines/action_engine/engine.py",
line 146, in run_iter
Public bug reported:
Template for 500 error uses CONF.WEBROOT to set Home link, where CONF is
loaded by templatetag from horizon.conf. But in
horizon/conf/__init__.py, only HORIZON_CONF is set and nothing else. As
a result, 500.html is rendered with empty url for Home link.
** Affects: horizon
** Changed in: glance
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1503187
Title:
DOC: Update glance status image with deactivate status
** Also affects: heat/liberty
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/1503501
Title:
oslo.db no longer requires testresources and
** Changed in: horizon
Status: In Progress => Fix Released
--
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/1234950
Title:
network topology order
Status in
Public bug reported:
Change set https://review.openstack.org/#/c/233766/ leads exeption in
networking_cisco/plugins/ml2/drivers/cisco/n1kv/exceptions.py
there is issue like that
--
error: testr failed (3)
Failed to import test module:
** Project changed: neutron => networking-cisco
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1507552
Title:
Changing in cisco exeption.py is requred
Status in networking-cisco:
New
Public bug reported:
ENVIRONMENT: devstack(19 oct 2015)
PREPEARE STEP: If it possible, remove all JobBinaries
STEPS TO REPRODUCE:
1. Navigate to JobBinaries
2. Click on "Create JobTemplate"
3. Navigate to "Libs" tab
4. Click on "+"
5. Create JobBinary and click "Create"
EXPECTED RESULT:
Public bug reported:
Nova Version: 2.22.0
I have share nfs storage mounting the /var/lib/nova between two compute
nodes. When I tried to re-sizing the instance using nova resize command,
it is failing and below is the output of log
2015-10-19 05:13:15.582 14325 ERROR
Public bug reported:
fwaas lacks tempest scenario tests
** 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/1507522
Title:
Public bug reported:
We can use dhcp-agent-network-add/remove to manually reschedule a net between
dhcp-agents. And "neutron dhcp-agent-list-hosting-net" and ip or ps commands
can be used to confirm network is rescheduled to new agent.
But dhcp port binding doesn't get updated in db site, we
Public bug reported:
In preview stack detail page, URL for the cancel button redirecting to
the 'access and security' table.
** Affects: horizon
Importance: Undecided
Assignee: Masco Kaliyamoorthy (masco)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Masco
Public bug reported:
When you disable the compute service of a host you cannot add it to an
aggregate.
To reproduce (tested on Kilo MOS packages on Ubuntu 14.04):
# nova-manage service disable compute01 nova-compute
# nova aggregate-add-host az1 compute01
ERROR (ClientException): The server has
Public bug reported:
We can use dhcp-agent-network-add to manually schedule a net to dhcp-
agents. And when we manually schedule dhcp-agent, neutron code should
check configure dhcp_agents_per_network, to verify current manually
scheduling could be support or not.
Pre-conditions:
2 active
Public bug reported:
To provide the support for running connectivity tests between the vms of
a tenant, from a centralized management system so that troubleshooting
the environment becomes easier.
Problem Description
===
Currently there is no automated system which can manage and
Public bug reported:
It is useful that there is sample data for policy.v3cloudsample.json.
** Affects: keystone
Importance: Undecided
Assignee: Hidekazu Nakamura (nakamura-h)
Status: New
** Changed in: keystone
Assignee: (unassigned) => Hidekazu Nakamura (nakamura-h)
--
** Also affects: glance/kilo
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1504184
Title:
Glance does not error gracefully on token
Public bug reported:
When setting the configuration parameter force_config_drive=true in the
/etc/nova/nova.conf config file and restarting the nova service or even
rebooting the whole server the openstack-nova-compute service fails to
start:
/var/log/nova/nova-compute.log
2015-10-19
Public bug reported:
Using cloud-init 0.7.7 in the wily cloud-images daily:
[ 12.493421] cloud-init[872]: 2015-10-19 10:14:26,302 - util.py[WARNING]:
Failed command: /sbin/udevadm settle --quiet --timeout=5
--exit-if-exists=/dev/fd0
[ 12.493665] cloud-init[872]: Unexpected error while
** Also affects: oslo.config
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/1507516
Title:
NoSuchOptError: no such option:
Public bug reported:
Overview:
After an upgrade to using keystone v3 the old style of location ceases to work.
This happens because it raises a 404 which in turn raises a 401. As it tries to
go to the location /v2.0/auth/tokens which did not exist in v2, but rather the
link is /v2.0/tokens.
Public bug reported:
https://review.openstack.org/#/c/215136/ was merged in the gate and
broke Ironic. It seems we have a weird issue in neutron db code that
makes fetch on router_id raise NotFound when updating a floating IP.
The patch was reverted in master, but we should understand what went
in master branch this function deprecated
** 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/1507517
Title:
When
Public bug reported:
reproduce step
1 when I try to delete a interface from a router , the neutron ask a subnet-ID
instead of interface ID , but the help prompt the direct me input a INTERFACE
ID,
I don't know what different with interface ID and subnet ID ? but I think this
should be have a
** Changed in: neutron
Importance: Undecided => Low
** Changed in: neutron
Status: New => Confirmed
** Summary changed:
- the neutron prompt inaccuracy information when delete the interface from a
router
+ router-interface-delete information prompt is inaccurate
** Project
Public bug reported:
vm occur i/o blocked about every five days. vm log as below:
INFO: task jbd2/dm-0-8:373 blocked for more than 120 seconds. Not
tainted 2.6.32-504.30.3.el6.x86_64 #1 "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
jbd2/dm-0-8 D 0
Public bug reported:
That would allow agents to fetch an object as if they have access to
database.
** Affects: neutron
Importance: Low
Assignee: Ihar Hrachyshka (ihar-hrachyshka)
Status: Confirmed
** Tags: oslo qos
--
You received this bug notification because you are a
Public bug reported:
Instead of reimplementing the serialization in neutron, allow
oslo.versionedobjects to handle it by using their own serializer.
** Affects: neutron
Importance: Low
Assignee: Ihar Hrachyshka (ihar-hrachyshka)
Status: Confirmed
** Tags: oslo qos
**
Public bug reported:
When updating admin_state of a functioning ipsec connection to DOWN, it
can be seen in vpn agent logs that pluto fails to restart with the
following error:
2015-10-19 14:05:11.622 TRACE neutron_vpnaas.services.vpn.device_drivers.ipsec
Command: ['ip', 'netns', 'exec',
Public bug reported:
Followed instruction on
https://wiki.openstack.org/wiki/Network/LBaaS/docs/how-to-create-tls-
loadbalancer#Create_TLS_enabled_load_balancer: to create a TLS listener.
After setting the undocumented cert_manager option to barbican I get the
following error:
015-10-14
The OVS documentation refers to documentation of its own implementation.
The Neutron QoS API offers an abstraction that happens to have only one
implementation at this time, but has your own LB patch
(https://review.openstack.org/236210) as a second one. As long as
something translates from the
** Changed in: python-novaclient
Status: Fix Committed => Fix Released
** Changed in: python-novaclient
Milestone: None => 2.32.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
This line:
https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py#L359
can raise exception when _restore_local_vlan_map runs in environments
with flat or untagged VLAN networks. For example:
File
Public bug reported:
neutron-openvswitch-agent seems to create wrong OVS flows for newly
created networks. This causes package losses, including lost DHCP
requests, resulting in instances that did not receive an IP. This can
cause tempest tests to fail.
Restarting the neutron-openvswitch-agent
Actually, I'll go ahead and mark this "Triaged"; it *is* a real bug, it
just isn't as critical as we assumed.
To fix this bug, we should configure cloud-init to NOT call pollinate
during enlistment (to avoid this spurious error).
As a follow-on fix, it might be a good idea for cloud-init to fall
Public bug reported:
In neutron in qos bw limit rule table in database and in API extension
parameter "max-burst-kbps" has got wrong units suggested. Burst should
be given in kb instead of kbps because according to for example ovs
documentation:
Public bug reported:
The openstack_dashboard Karma configuration is not looking in the right
place for templates and other resources. For example, you cannot use
the 'templates' module to load templates for use in directive testing.
** Affects: horizon
Importance: Undecided
Assignee:
openstack/juno is security support
** Changed in: neutron
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1498315
Title:
Suggest do not display
Public bug reported:
This change:
http://git.openstack.org/cgit/openstack/rally/diff/rally/plugins/openstack/scenarios/keystone/basic.py?id=f871de842214f103b4841160e90c73cd98c4f5ad
Breaks this job:
Public bug reported:
As per the release process of Neutron sub-project, this bug report is to
request the Neutron release team to tag and release "networking-ale-
omniswitch" sub-project along with Liberty main release.
https://launchpad.net/networking-ale-omniswitch
Public bug reported:
self._wait_till_spinner_disappears() is changed to
self.wait_till_popups_disappear().
This needs to be changed for instance tests: in instancespage.py
** Affects: horizon
Importance: Undecided
Assignee: Amogh (amogh-r-mavinagidad)
Status: In Progress
--
Public bug reported:
Summary : Support for filtering based on ICMP codes is missing in Openstack
firewall.
Further information :
High level description: Currently Openstack firewall rules allow
filtering of ICMP packets.However filtering is done for all ICMP packets. There
can be a
Public bug reported:
(A)Summary : Firewall rules in Openstack does not support scheduling
(B)Further information :
(B.1)High level description: Currently Openstack firewall rules do not allow
scheduling. When a router is associated with a firewall, the rules making the
firewall are active for
[Expired for Keystone because there has been no activity for 60 days.]
** Changed in: keystone
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1464377
** Changed in: nova
Status: Expired => 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/1414527
Title:
The multipath device descriptors remove failed when the
Resolved:
After upgrading from Juno to Kilo python-neutronclient was stuck at an
older version.
apt-get install python-neutronclient=1:2.3.11-0ubuntu1.2~cloud0 all
nodes fixed the issue.
** Changed in: nova
Status: New => Opinion
** Changed in: nova
Status: Opinion => Invalid
--
** Changed in: oslo.messaging
Status: Fix Committed => Fix Released
** Changed in: oslo.messaging
Milestone: None => 2.7.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Changed in: oslo.versionedobjects
Status: Fix Committed => Fix Released
** Changed in: oslo.versionedobjects
Milestone: None => 0.12.0
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Guys,
The vncserver_listen doesn't work anymore in a dual-stack setup, error:
2015-10-19 21:22:03.180 2737 ERROR nova.compute.manager [instance:
9fc58e29-41a0-44a8-aa31-1773d5cdea13] 2015-10-20T01:22:02.895921Z qemu-
system-x86_64: -vnc [::]:0: Failed to start VNC server on
** Changed in: nova
Status: Expired => 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/1414865
Title:
Lost the sd* devices which belong to the multipath
Public bug reported:
As part of networking-vsphere project which runs ovsvapp agent
on each ESXi host inside service VM, which talk to neutron-server
having l2pop enabled in a multi-hypervisor mode like KVM, ESXi.
The tunnels are not getting established between KVM compute node
and ESXi host.
55 matches
Mail list logo
