[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).
https://bugs
Public bug reported:
The image name filter on Instance panel is using a simple way to get the
correct image ID from a mapping. There are 2 problems could happen here:
1. Horizon is using an API call like this:
/v2/images?limit=1000&sort_key=created_at&sort_dir=des to get the images
list so as to
Public bug reported:
Currently, Horizon does have a blacklist for Nova extension to skip some
features of Nova which can be used by cloud operators.
However, on the Instance panel, there are 5 actions need to call the
extension_supported function to check if the feature/extension is
supported or
Ceilometer dashboard has been moved out of Horizon.
** Changed in: horizon
Status: Confirmed => 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/1243694
Reviewed: https://review.openstack.org/510689
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=2ac329b90274ecbf7dd3234b39c74dc974658c30
Submitter: Jenkins
Branch:master
commit 2ac329b90274ecbf7dd3234b39c74dc974658c30
Author: Boden R
Date: Mon Oct 9 14:49:49 2017 -060
Reviewed: https://review.openstack.org/506093
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=87ca0d8af0d6440a7effd4da9e47321b3a335442
Submitter: Jenkins
Branch:master
commit 87ca0d8af0d6440a7effd4da9e47321b3a335442
Author: Sylvain Bauza
Date: Thu Sep 21 10:52:46 2017
Reviewed: https://review.openstack.org/510191
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=cda315c54f52a35b45fef6bb3c9457f3520550fe
Submitter: Jenkins
Branch:master
commit cda315c54f52a35b45fef6bb3c9457f3520550fe
Author: Boden R
Date: Fri Oct 6 11:16:35 2017 -060
Reviewed: https://review.openstack.org/503530
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=b9ecb3804c85dedccb578b1e930e68270a3535e1
Submitter: Jenkins
Branch:master
commit b9ecb3804c85dedccb578b1e930e68270a3535e1
Author: Swaminathan Vasudevan
Date: Tue Sep 12 21:
Public bug reported:
Launch an instance on Azure (20171005.1) and I find in /var/log/cloud-init.log
the following:
2017-10-10 21:16:25,598 - DataSourceAzure.py[WARNING]: Failed publishing
hostname: Unexpected error while running command.
Command: ['sh', '-xc', 'i=$interface; x=0; ifdown $i || x=
Public bug reported:
The DVR multinode scenario job is failing its floating IP east-west
tests.
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSameNetwork
neutron.tests.tempest.scenario.test_floatingip.FloatingIpSeparateNetwork
Example:
http://logs.openstack.org/84/500384/18/check/gat
The first requirement doesn't seem to be used in keystone at all. It
must be getting pulled in due to a transitive dependency somewhere?
The second seems specific to oslo_utils and not keystone. Add oslo to
this bug report so that we can get some more eyes on this.
I'm unsure how to fix this from
This appears to be an attempt to file a bug against horizon, or is at
least UI specific.
** Changed in: keystone
Status: New => Incomplete
** Also affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Enginee
** Also affects: keystone/ocata
Importance: Undecided
Status: New
** Changed in: keystone/ocata
Status: New => Fix Committed
** Changed in: keystone/ocata
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Tea
** Also affects: keystone/ocata
Importance: Undecided
Status: New
** Changed in: keystone/ocata
Importance: Undecided => High
** Changed in: keystone/ocata
Status: New => Fix Committed
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
Reviewed: https://review.openstack.org/510603
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=0ffe03a2650a698de1b83289098ed535734b2360
Submitter: Jenkins
Branch:master
commit 0ffe03a2650a698de1b83289098ed535734b2360
Author: Balazs Gibizer
Date: Mon Oct 9 16:29:09 2017
Reviewed: https://review.openstack.org/483969
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=ad33ae5771de3a90472ca836a7b2292c6334fe9e
Submitter: Jenkins
Branch:master
commit ad33ae5771de3a90472ca836a7b2292c6334fe9e
Author: Balazs Gibizer
Date: Fri Jul 14 17:19:03 2017
Public bug reported:
http://logs.openstack.org/13/474213/7/check/gate-tempest-dsvm-neutron-
dvr-multinode-scenario-ubuntu-xenial-
nv/752030f/logs/testr_results.html.gz
Traceback (most recent call last):
File "/opt/stack/new/neutron/neutron/tests/tempest/scenario/test_trunk.py",
line 91, in _de
Reviewed: https://review.openstack.org/500384
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=f5718972257cf229c8a9db0a5fc4349acbaade12
Submitter: Jenkins
Branch:master
commit f5718972257cf229c8a9db0a5fc4349acbaade12
Author: venkata anil
Date: Tue Sep 19 07:41:19 201
Public bug reported:
When a neutron port is attached to a VM, it can be deleted. This is
possible without detached from VM first.
A condition should be added to avoid deletion of neutron port if it is
attached to VM (device id being not None).
** Affects: neutron
Importance: Undecided
Marking as high severity since this is a regression introduced in Pike.
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova
Importance: Medium => High
** Changed in: nova/pike
Status: New =>
** Changed in: tempest
Assignee: (unassigned) => Matt Riedemann (mriedem)
** Changed in: nova
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpa
** Also affects: nova
Importance: Undecided
Status: New
** Changed in: tempest
Status: Triaged => Invalid
** Changed in: tempest
Status: Invalid => Confirmed
** Changed in: nova
Status: New => Triaged
--
You received this bug notification because you are a member
Public bug reported:
We have a problem with the metadata service not being responsive, when
the proxied in the router namespace on some of our networking nodes
after upgrading to Ocata (Running on CentOS 7.4, with the RDO packages).
Instance routes traffic to 169.254.169.254 to it's default gate
Public bug reported:
After we enabled live snapshot by default for the libvirt driver, we get
these stacktraces all over the n-cpu logs anytime we create a snapshot
image:
http://logs.openstack.org/65/509465/18/check/gate-tempest-dsvm-py35
-ubuntu-xenial/0e88c0a/logs/screen-n-cpu.txt#_Oct_10_13_4
Public bug reported:
launching an instance in lxd I see in /var/log/cloud-init-output.log the
following
the SimpleTable should be a rendered version of the network information.
Cloud-init v. 17.1 running 'init' at Tue, 10 Oct 2017 15:13:35 +. Up 6.00
seconds.
ci-info: +
Public bug reported:
Hi Guys,
I met an strange issue. when creating a vm with one network , but it
appeared two network interfaces and two ip addresses.
It seems like https://ask.openstack.org/en/question/85238/instance-
getting-two-ip-addresses/
In nova-scheduler.log, we can see it happened fa
** Changed in: neutron
Status: Confirmed => 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/1627749
Title:
qos driver api can have better error handling
Status in net
The problem isn't nova. It's taking a long time to setup networking on
the neutron side after the VIF is plugged for the guest on the compute
host. Nova starts waiting for an event callback from neutron here:
46259:2017-10-03 20:07:07.322 7 DEBUG nova.compute.manager [req-
de0f02c8-9410-424f-bdac-
Hi Jakub, It does seem OpenFlow does not allow sending traffic back to a
previous table:
https://3vf60mmveq1g8vzn48q2o71a-wpengine.netdna-ssl.com/wp-content/uploads/2014/10/openflow-switch-v1.5.1.pdf
Page 20, middle of the 3rd paragraph.
** Changed in: neutron
Status: New => Invalid
--
Y
Public bug reported:
When creating a new instance from image, the resulting instance does not
receive the image_ref metadata.
This effect has shown up with
Ubuntu:
openstack-dashboard3:12.0.0-0ubuntu1~cloud0
openstack-dashboard 3:11.0.3-0ubuntu3~cloud0
Cento
Public bug reported:
When creating a new instance from image, the resulting instance does not
receive the image_ref metadata.
This effect has shown up with
Ubuntu:
openstack-dashboard3:12.0.0-0ubuntu1~cloud0
openstack-dashboard 3:11.0.3-0ubuntu3~cloud0
Cento
In neutron development, this topic failed to gather attraction, and
neutron team has not received this kind of requests except this one.
As horizon, this bug has no activity for a long time as well.
Considering this situation, I would like to mark this as Won't Fix (for
both horizon and neutron).
Nova security group API has been dropped in the latest Nova REST API (I
don't check the exact micro version though), so this bug no longer
affects Nova.
** No longer affects: nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to ne
"External Gateway" can be set in the router create form and this form
can be launched from the network topology, so this bug no longer exists.
** Changed in: horizon
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
As of now (Queens-1), UUID is shown if a name is empty. This seems to
have been fixed as another bug. I failed to find a corresponding bug,
but the reported issue no longer exists.
** Changed in: horizon
Milestone: next => None
** Changed in: horizon
Status: In Progress => Invalid
--
LBaaS v1 panel was dropped several releases ago.
** Changed in: horizon
Assignee: Tatiana Ovchinnikova (tmazur) => (unassigned)
** Changed in: horizon
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is sub
Assigning the proper quota for floating IP is the role of operators.
Operators should know the size of floating IPs.
In addition, this kind of thing should be verified in the backend
service. Quota can be set via CLI, API and GUI, so having this kind of
logic in GUI does not look like a good idea.
*** This bug is a duplicate of bug 1517704 ***
https://bugs.launchpad.net/bugs/1517704
** This bug has been marked a duplicate of bug 1517704
Test still passes even with tests failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subsc
Public bug reported:
After update ocata to pike.
[root@mgmt2 ~]# rpm -qa | grep openstack-neutron-lbaas
openstack-neutron-lbaas-11.0.1-1.el7.noarch
[root@mgmt2 ~]# rpm -qa | grep openstack-dashboard
openstack-dashboard-12.0.0-2.el7.noarch
When accessing "Load Balancers" Tab in Horizon UI a foll
Adding the charm because maybe there's a more unique field we can use
than uid, given this behaviour with re-use of uid's
** Project changed: keystone => charm-keystone-ldap
** Also affects: keystone
Importance: Undecided
Status: New
--
You received this bug notification because you a
Now the security group is a separate panel and the breadcrumb list is
supported, so we can easily move back to the security group list from
the SG rule page, so I think the requested feature is achieved (in a
different way).
** Changed in: horizon
Status: Confirmed => Invalid
** Changed in
Public bug reported:
Not sure if this should be a bug or a RFE.
After setting change_password_upon_first_use security_compliance in
keystone.conf:
[security_compliance]
change_password_upon_first_use = True
For a new user it is impossible to login in Horizon, it prompts "Invalid
credentials."
The new launch instance form with Angular implementation is now the
default and we are planning to deprecate and drop the legacy launch
instance form. In the new form, the network information is shown more
clearly and this issue does not apply to the new launch instance.
Considering this, we would
** Also affects: nova
Importance: Undecided
Status: New
** No longer affects: mos
--
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/1708572
Title:
Unable to live
[comments as my neutron hat]
The demand is still not clear. Security Group behavior is stateful, so the
ingress rule and egress rule are completely different.
There is no other feedback like this so far. This is the only one. Use case is
not clear. So I don't add neutron to the affected project.
This is no longer valid.
** Changed in: horizon
Status: Triaged => Invalid
** Changed in: horizon
Importance: Wishlist => Undecided
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://
This is already supported as of Pike.
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/routers/forms.py#L42
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/routers/forms.py#L48-L66
** Changed in: horizon
Status:
The project table is being re-implemented with Angular and the current
implementation will be replaced sooner or later.
** Changed in: horizon
Assignee: ChangBo Guo(gcb) (glongwave) => (unassigned)
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug noti
As discussed in the review above, we decided to keep the current
pattern.
** Changed in: horizon
Milestone: next => None
** Changed in: horizon
Status: In Progress => Won't Fix
** Changed in: horizon
Assignee: Artem Tiumentcev (darland-maik) => (unassigned)
--
You received this
49 matches
Mail list logo
