Public bug reported:
Openstack mitaka 3 node setup. Horizon is installed on controller node.
All the services are up and running. when try to access horizon on
http://controller/horizon, it is not accessible:
Error logs:
[Fri May 27 11:41:13.655871 2016] [:info] [pid 5335:tid 139981529089792]
** Changed in: neutron
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/1587723
Title:
routers created as demo user are not listed when admin
Status in
Public bug reported:
Steps to reproduce:
1. Create a router as demo user
2. From CLI, the router can be listed when you are admin user
3. From dashboard, the router is not listed when logged in as admin
** Affects: neutron
Importance: Undecided
Assignee: Sharat Sharma (sharat-sharma)
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]
** Changed in: nova
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
[Expired for OpenStack Dashboard (Horizon) because there has been no
activity for 60 days.]
** Changed in: horizon
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1563329
Reviewed: https://review.openstack.org/320233
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=5ca5ecc0b9fc745750c37c093429d02b2633ffb7
Submitter: Jenkins
Branch:master
commit 5ca5ecc0b9fc745750c37c093429d02b2633ffb7
Author: Kenji Ishii
Date:
Public bug reported:
There is no way to view the interfaces attached to a router from the
CLI. To know the interfaces attached to the router, we have to rely on
dashboard. So an extra field has to be added to the router-show table to
display the attached interfaces.
** Affects: neutron
Confirmed with origin/master
SHA:ced89e7b26b3cff323852e1d8a9c6db80334f4dd
** Changed in: nova
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
we use 'hard reboot' and 'soft reboot' explicitly, so this bug is
invalid, sorry for the confusion.
** Changed in: horizon
Status: New => Invalid
** Changed in: horizon
Assignee: Zhenguo Niu (niu-zglinux) => (unassigned)
--
You received this bug notification because you are a
Public bug reported:
We can soft and hard reboot a running instance, A soft reboot attempts a
graceful shut down and restart of the instance. A hard reboot power
cycles the instance, by default when you reboot an instance, is a soft
reboot in nova CLI, and you need to explicitly pass a --hard
Public bug reported:
Now nova service delete is using the same logic for compute service and
the others. See
https://github.com/openstack/nova/blame/stable/kilo/nova/db/sqlalchemy/api.py#L446
And as a result, if there is any service running associated with compute
service(on the same host), then
Public bug reported:
The npm-run-test job in the gate has shown itself to be less reliable
lately. In particular it tends to hang until the timeout, after
successfully completing the tests.
There have been similar failures in the past due to a variety of
reasons. Most likely there's a memory
Reviewed: https://review.openstack.org/307526
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=88a1a8cfe9d9d5bc8b0e7ff0040f28c3d3c5
Submitter: Jenkins
Branch:master
commit 88a1a8cfe9d9d5bc8b0e7ff0040f28c3d3c5
Author: Adolfo Duarte
Date:
Reviewed: https://review.openstack.org/322508
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=993446bc2397c16fa6ead61535680bb2503bf32f
Submitter: Jenkins
Branch:master
commit 993446bc2397c16fa6ead61535680bb2503bf32f
Author: Gary Kotton
Date: Sun
Public bug reported:
I get the neutron lbaas code files and the service file from github
website. Detailed address is "https://github.com/openstack/neutron-
lbaas","https://github.com/openstack-packages/neutron-lbaas/tree/rpm-
kilo". Then , I start the neutron-lbaas-agent.service ,but the service
Reviewed: https://review.openstack.org/123741
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=ce5fb26bf5f431f0cdaa6860a732338db868a8fb
Submitter: Jenkins
Branch:master
commit ce5fb26bf5f431f0cdaa6860a732338db868a8fb
Author: Paul Karikh
Date:
Public bug reported:
Mitaka introduced a regression to the old instance launch wizard where
it no longer checks the default security group.
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering
Public bug reported:
In Mitaka, the new launch instance wizard regresses functionality from
the old launch wizard with regards to defaults. If there is only one
neutron network, it is not automatically selected, if there is only one
keypair, its not selected, and the default security group is not
Public bug reported:
https://review.openstack.org/123741
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/horizon" is set up so that we directly report the
documentation bugs against it. If this needs changing, the docimpact-group
option
Reviewed: https://review.openstack.org/305525
Committed:
https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=c304a5389d1ca7aae33cc55af63de2173c1f7b5e
Submitter: Jenkins
Branch:master
commit c304a5389d1ca7aae33cc55af63de2173c1f7b5e
Author: Franklin Naval
Reviewed: https://review.openstack.org/322772
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=fcdec6cd1392ceea3a5b226d8cf3a42cad95a87a
Submitter: Jenkins
Branch:master
commit fcdec6cd1392ceea3a5b226d8cf3a42cad95a87a
Author: Sahid Orentino Ferdjaoui
Would like to hear from folks - this is impacting a lot of projects, and
people can't build from git branches...
IMO this is extremely critical and we need to get a response.
** Also affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you
** Also affects: barbican
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/1586979
Title:
AMQP 2.0 prevents services from starting
Status in
Reviewed: https://review.openstack.org/322743
Committed:
https://git.openstack.org/cgit/openstack/neutron-vpnaas/commit/?id=beff6e945ce4cf31f4a6ae977df72410dc80b717
Submitter: Jenkins
Branch:master
commit beff6e945ce4cf31f4a6ae977df72410dc80b717
Author: Thomas Bechtold
I added oslo.messaging to this. If it needs to be marked duplicate then
that is fine, but considering nobody can build Openstack in this state,
there needs to be some urgency on this. I tested a couple of
workarounds, but the best one so far for us has been to uninstall amqp
and reinstall the
Confirmed this also affects Ironic.
Searched and found this open bug in oslo.messaging, addressing the underlying
issue:
https://bugs.launchpad.net/oslo.messaging/+bug/1586840
** Also affects: ironic
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
1. Log in to Horizon Dashboard.
2. Go to Project/Compute/Instances.
3. Take and drop the "Launch instance" button into the text field.
Actual result: we can see button-action in this field
Excepted result: empty text field
This bug appears for all cases with field +
Reviewed: https://review.openstack.org/317738
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=bf4f7e8b25fefb03f0555dbc7ebeac8d8308cfc6
Submitter: Jenkins
Branch:master
commit bf4f7e8b25fefb03f0555dbc7ebeac8d8308cfc6
Author: Matt Borland
Date:
Reviewed: https://review.openstack.org/323228
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=5532fb71925a2473545b0f290367234b09fc7d7f
Submitter: Jenkins
Branch:master
commit 5532fb71925a2473545b0f290367234b09fc7d7f
Author: Zhenmei
Date: Tue May 31
Public bug reported:
Dear,
I am using Mitaka RDO release on Controller and I am trying install
nova-compute node using RDO on XenServer 7 (Dundee) with XenAPI driver.
I have successfully installed neutron on the XenServer.
I am having a following bug while trying to install openstack-nova-
Reviewed: https://review.openstack.org/287793
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=408e358f791956e1c39e4ec2c254926ee48a8014
Submitter: Jenkins
Branch:master
commit 408e358f791956e1c39e4ec2c254926ee48a8014
Author: Timur Sufiev
Date:
** Changed in: bgpvpn
Status: In Progress => 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/1554452
Title:
Request release for networking-bgpvpn
Status in bgpvpn:
** No longer affects: bgpvpn
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1512324
Title:
networking-bgpvpn kilo branch
Status in neutron:
Fix Released
Bug description:
While we
** Changed in: bgpvpn
Status: New => Won't Fix
** Changed in: neutron
Status: Confirmed => Fix Released
** Changed in: bgpvpn
Status: Won't Fix => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Public bug reported:
The macvtap agent only works with the NoopFWDriver. If another driver is
configured it terminates. Now there are two ways in configuring the
NoopFWDriver
1) directly: neutron.agent.firewall.NoopFirewallDriver
2) via the alias: noop
Today only the direct way is supporte,
** Changed in: bgpvpn
Milestone: 4.0.0 => None
** No longer affects: neutron
** Changed in: bgpvpn
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
** Changed in: django-openstack-auth
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1585682
Title:
Horizon gating on
This bug is invalid, since:
1) Inheritance is only applied to children of the node that carries the actual
inherited assignment
2) Effective assignments only show the result of all group & inherited
assignments, as well as valid non-inedited direct user assignments - but do not
include the
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
** No longer affects: 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/1563295
Title:
Inconsistent behaviour when unicode args used for logging
Status in oslo.log:
JianGang - bugs.launchpad.net is not a support tool, you should be using
ask.openstack.org, or the openst...@lists.openstack.org list for
questions relating to how to configure neutron.
Unless you are suggesting a new enhancement and I'm mis-understanding?
** Changed in: neutron
Status:
Can be easily reproduced with:
from oslo_log import log as logging
LOG = logging.getLogger(__name__)
LOG.info("Oslo Logging %s", u'\u2622'.encode('utf8'))
The issue is related to implicit decoding of logging arguments due
_ensure_unicode for message:
Public bug reported:
As the macvtap agent does only support flat and vlan networks, the
physical_interface_mappings prameter must contain at least one mapping.
Without a mapping, no networkconnectivity can be provided by this agent.
Ideally the agent would terminate with an appropriate error
Public bug reported:
While creating a router the following situation occurred:
[root@Mitaka5 ~(keystone_admin)]# neutron router-create --description "This is
a bug" router_one
Created a new router:
+-+--+
| Field |
** Also affects: kolla
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/1501380
Title:
Evolution of options and features in neutron-db-manage
Reviewed: https://review.openstack.org/321640
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=caa5e910598707d2cfc56faedb6dff97c574e50c
Submitter: Jenkins
Branch:master
commit caa5e910598707d2cfc56faedb6dff97c574e50c
Author: Timur Sufiev
Date:
Public bug reported:
Some mechanism drivers cooperate with another backend(SDN controller).
In this case, drivers may want to change status of port so that
user can recognize process for the port is failed when failure in calling to
backend.
However, currently there is no helper function in
Public bug reported:
Nova sometimes raises an exception when running the periodic instance deleted,
see below. The error is quite spurious, and it is not happening always so I
cannot get the reason why this is happening. The periodic reclaim is trying to
delete the instance, but the DB is not
Public bug reported:
We have the following traceback in a networking-bgpvpn test [1].
2016-05-31 09:04:33.341 | FAIL:
networking_bgpvpn.tests.unit.db.test_db.BgpvpnDBTestCase.test_db_associate_twice
2016-05-31 09:04:33.341 | tags: worker-0
2016-05-31 09:04:33.342 |
Added affected projects that we've tested so far. I have not
specifically tested Glance in my sandbox. Overall, AMQP 2.0 is breaking
everything. Our automation is working around the problem by
uninstalling 2.0 and installing 1.4.9 manually.
Would like to hear feedback on this. Some folks are
Public bug reported:
In the class DhcpAgentNotifyAPI docstring, it said that the related server side
is neutron.agent.dhcp_agent.DhcpAgent, it should be changed to
neutron.agent.dhcp.agent.DhcpAgent
** Affects: neutron
Importance: Undecided
Assignee: Zhenmei (zma-4)
Status:
Public bug reported:
Config option 'use_veth_interconnection' should be deprecated. Instead
we can always use Open vSwitch patch ports.
The discussion started in a review here:
https://review.openstack.org/#/c/318317/2
openstack/neutron/doc/source/devref/openvswitch_agent.rst
line 471
AFAICT
You have been subscribed to a public bug:
Config option 'use_veth_interconnection' should be deprecated. Instead
we can always use Open vSwitch patch ports.
The discussion started in a review here:
https://review.openstack.org/#/c/318317/2
Public bug reported:
Specifying '-F' or '--filed' parameter in the qos related commands,
returns abnormal result
3 problems:
1) Specifying '-F' or '--field' parameter in addition to 'rules' in
'qos-policy-show' command, the result returned contains extra field 'rules',
while specifying '-F' as
Public bug reported:
heat TemplateForm glance.image sizeformat error
** Affects: horizon
Importance: Undecided
Assignee: zhurong (zhu-rong)
Status: In Progress
** Attachment added: "snap.png"
https://bugs.launchpad.net/bugs/1587286/+attachment/467/+files/snap.png
**
Public bug reported:
[Summary]
Unexpected volume-detach happen under a specific condition.
[Version]
Later than 13.0.0
[Steps to reproduce]
1. Attach "volume-A" to "VM-A" by volume-attach API.
e.g.
$ nova volume-attach /dev/vdb
2. Volume-attach API is failed in nova-api by unexpected
Public bug reported:
A yesno filter should consider string
For instance, a bootable item in cinder volume
can be string "true" or string "false".
So, a yesno filter returns "Yes" if value of bootable is string "false".
There is a possibility of same case in other item.
By all rights, we
Reviewed: https://review.openstack.org/315474
Committed:
https://git.openstack.org/cgit/openstack/zaqar/commit/?id=d744f813a0509d91d230a3260f4d1dcb7fed8c0f
Submitter: Jenkins
Branch:master
commit d744f813a0509d91d230a3260f4d1dcb7fed8c0f
Author: sharat.sharma
Public bug reported:
In some scenes, Traffics of VMs belong to different logic network will pass
through different physic network domains with various MTU values. like blow:
------ ---
| VM1 || VM2 | | VM3 |
61 matches
Mail list logo