Public bug reported:
floatingip status is not reliable as it is set to active during creation itself
[1] rather than waiting for agent [2] to update it once agent finishes adding
SNAT/DNAT rules.
[1] https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py#L1234
[2]
https://github.c
Reviewed: https://review.openstack.org/500353
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=a4d05ce55da8e4e86dfd13933bfea6250085c72d
Submitter: Jenkins
Branch:master
commit a4d05ce55da8e4e86dfd13933bfea6250085c72d
Author: Akihiro Motoki
Date: Sun Sep 3 08:27:42 20
Reviewed: https://review.openstack.org/496259
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=4c5231c2587e9e4de8e272d1e565a160d96f9bf5
Submitter: Jenkins
Branch:master
commit 4c5231c2587e9e4de8e272d1e565a160d96f9bf5
Author: Marek Lycka
Date: Tue Aug 22 13:52:54 2017
Public bug reported:
TBA
** Affects: nova
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/1718567
Title:
Mention API beh
https://docs.openstack.org/ocata/install-guide-rdo/nova-controller-
install.html#finalize-installation says:
In the [glance] section, configure the location of the Image service
API:
[glance]
# ...
api_servers = http://controller:9292
So you missed a step.
** Changed in: nova
Cells v1 support is basically frozen, we aren't fixing latent bugs:
https://docs.openstack.org/nova/latest/user/cells.html#status
** Changed in: nova
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Reschedules and up-calls from the cell conductor to the API database
(and scheduler) don't work in superconductor mode in devstack. I
commented on the devstack patch. Please read and understand this first:
https://docs.openstack.org/nova/latest/user/cellsv2_layout.html
** Changed in: nova
This cannot be reproduced now.
** Tags removed: space
** Changed in: horizon
Status: In Progress => 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/151
** Also affects: nova-powervm
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/1718545
Title:
[vnc]vncserver_proxyclient_addres
As of now, we see version-less endpoint for identity service like
http://172.27.201.206/identity
** Changed in: horizon
Assignee: Dan Nguyen (daniel-a-nguyen) => (unassigned)
** Changed in: horizon
Status: In Progress => New
** Changed in: horizon
Importance: Low => Undecided
**
This bug no longer exists. The error message "Specify "Network Address"
or clear "Create Subnet" checkbox in previous step." was shown at the
top header when I click Next while keeping "Network Address" blank.
** Changed in: horizon
Assignee: qiaomin032 (chen-qiaomin) => (unassigned)
** Chan
Reviewed: https://review.openstack.org/500379
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=0afe2c201a7d114564a0f0aed03ba91ffd776023
Submitter: Jenkins
Branch:master
commit 0afe2c201a7d114564a0f0aed03ba91ffd776023
Author: venkata anil
Date: Sun Sep 3 17:52:04 2017
Reviewed: https://review.openstack.org/478437
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=aaddd51d6fa8863a505e3f33810660b0b27be14d
Submitter: Jenkins
Branch:master
commit aaddd51d6fa8863a505e3f33810660b0b27be14d
Author: naichuans
Date: Wed Jun 28 08:36:29 2017 +000
Public bug reported:
[0] removed options [vnc]vncserver_proxyclient_address and
[vnc]vncserver_listen without a deprecation period. Lemme splain:
Take for example vncserver_proxyclient_address. It was originally
[DEFAULT]vncserver_proxyclient_address. That was moved to
[vnc]vncserver_proxyclie
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
All features except extra-dhcp-opts are already supported or covered by other
bugs, so marking this as Invalid.
if extra-dhcp-opts support is needed, it should be filed as a separate specific
bug.
** Changed in: horizon
Milestone: next => None
** Changed in: horizon
Status: Confirmed
It was reported long ago. Since then, there were a lot of improvements
on policy-based action and the feature now works (as of now). Marking it
as Invalid.
** Changed in: horizon
Status: Confirmed => Invalid
** Changed in: horizon
Milestone: next => None
--
You received this bug noti
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Tags added: integration-tests
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed t
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Tags added: integration-tests
** Changed in: horizon
Status: In Progress => Won't Fix
** Changed in: horizon
Milestone: next => None
--
You received this bug notification because you are a memb
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
h
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
h
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
h
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: Confirmed => Won't Fix
** Changed in: horizon
Milestone: next => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
h
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
h
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
h
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Tags added: integration-tests
** Changed in: horizon
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: In Progress => Won't Fix
** Changed in: horizon
Milestone: next => None
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
*** This bug is a duplicate of bug 1588663 ***
https://bugs.launchpad.net/bugs/1588663
** This bug has been marked a duplicate of bug 1588663
cannot specify fixed ip when user create a port
** Changed in: horizon
Milestone: next => None
--
You received this bug notification because y
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
htt
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
htt
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
htt
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
Integration tests have been abandoned all together by Horizon. This no
longer applies.
** Changed in: horizon
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://b
** Changed in: horizon
Status: Won't Fix => 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/1343684
Title:
API pagination support for heat event list
Sta
This is related to LBaaS v1 dashboard. LBaaS v1 API and its dashboard
was dropped a while ago, so Won't Fix.
** Changed in: horizon
Milestone: next => None
** Changed in: horizon
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
E
As of Queens-1, this bug no longer exists. The logic has been improved
since the bug reported. Perhaps the policy support improvement helps it.
** Changed in: horizon
Status: Confirmed => Invalid
** Changed in: horizon
Milestone: next => None
--
You received this bug notification bec
*** This bug is a duplicate of bug 1634877 ***
https://bugs.launchpad.net/bugs/1634877
** This bug has been marked a duplicate of bug 1634877
It would be good to have the abilty to turn on/off port security
** Changed in: horizon
Milestone: next => None
--
You received this bug notif
** Also affects: nova/ocata
Importance: Undecided
Status: New
** No longer affects: nova/ocata
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => Confirmed
** Changed in: nova/pike
Importance: Undecided => Medium
*
This will be done as part of
https://blueprints.launchpad.net/horizon/+spec/pike-docs-overhaul.
** 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 (Horizo
Flavors Extra Specs has been removed from Horizon a few releases back.
** 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/
Looks like it's already implemented in master. Please, re-open bug if
it's still actual
** Changed in: horizon
Status: In Progress => Fix Released
** Changed in: horizon
Assignee: Wim De Clercq (wim-de-clercq) => (unassigned)
--
You received this bug notification because you are a m
Public bug reported:
(OpenStack Nova, commit d8b30c3772, per OSA-14.2.7)
if an instance build fails on a hypervisor the "retry" field of the
instance's request spec is populated with which host and how many times
it attempted to retry the build. this field remains populated during the
life-time o
Looks like we've already merged patch to Horizon
** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1203413
Closing this bug according to the previous comment
** 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/12
** 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 Compute (nova).
https://bugs.launchpad.net/bugs/1259292
Title:
Some tests use assertEqual(observed, expe
Reviewed: https://review.openstack.org/408304
Committed:
https://git.openstack.org/cgit/openstack/keystone/commit/?id=d03f35ee6753600bcd5ddfc8f692d00376284aa3
Submitter: Jenkins
Branch:master
commit d03f35ee6753600bcd5ddfc8f692d00376284aa3
Author: Aqsa
Date: Wed Mar 22 11:30:27 2017 +
Reviewed: https://review.openstack.org/505123
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=2f8edeedc88491214d2502c5b1d17a155f452a47
Submitter: Jenkins
Branch:master
commit 2f8edeedc88491214d2502c5b1d17a155f452a47
Author: ericxiett
Date: Tue Sep 19 16:50:14 2017 +0
** Changed in: nova
Assignee: Sean Dague (sdague) => jichenjc (jichenjc)
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/pike
Importance: Undecided
Status: New
** Changed in: nova/pike
Status: New => In Progress
** Changed in: nova/pike
As
Reviewed: https://review.openstack.org/499592
Committed:
https://git.openstack.org/cgit/openstack/glance/commit/?id=877cd166b56ec4b7f5530ea9bf1587077692275b
Submitter: Jenkins
Branch:master
commit 877cd166b56ec4b7f5530ea9bf1587077692275b
Author: Bernhard M. Wiedemann
Date: Thu Aug 31 15:1
Reviewed: https://review.openstack.org/503890
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=fd1403fd9a971cf3cbd863fa33ca68eb019fbdc1
Submitter: Jenkins
Branch:master
commit fd1403fd9a971cf3cbd863fa33ca68eb019fbdc1
Author: Sławek Kapłoński
Date: Thu Sep 14 02:11:50
Reviewed: https://review.openstack.org/501132
Committed:
https://git.openstack.org/cgit/openstack/os-vif/commit/?id=fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Submitter: Jenkins
Branch:master
commit fa4ff64b86e6e1b6399f7250eadbee9775c22d32
Author: Sahid Orentino Ferdjaoui
Date: Wed Sep 6 03
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Importance: Undecided => Medium
** Also affects: nova/newton
Importance: Undecided
Status: New
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Also affects: nova/pike
Importance: U
Public bug reported:
The instance.live.migration.force.complete legacy notification does not
have any test coverage and therefore it is missed the whitelisting of
allowed legacy notification. We should add test coverage and whitelist
this notification.
This is a problem since I034b4041414a797f65e
Public bug reported:
Occasionally, Virtuozzo Storage CI fails 1 testcase, with following error in
nova-compute:
Sep 20 09:40:55 localhost.localdomain nova-compute[67785]: Command:
pstorage-mount -c testcluster_uypcf0k16f -u stack -g root -m 0770 -l
/var/log/vstorage/testcluster_uypcf0k16f/nova.
Reviewed: https://review.openstack.org/501342
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a76277f81a005cb48088fd9452637b4e7ee1b9f5
Submitter: Jenkins
Branch:master
commit a76277f81a005cb48088fd9452637b4e7ee1b9f5
Author: Stephen Finucane
Date: Wed Sep 6 16:44:53 201
Reviewed: https://review.openstack.org/503601
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=062f5b2e876a09119e43c1905f91610cd4e5d015
Submitter: Jenkins
Branch:master
commit 062f5b2e876a09119e43c1905f91610cd4e5d015
Author: Yikun Jiang
Date: Wed Sep 13 19:35:49 2017 +0
Public bug reported:
Disabling a host in horizon and live-migrating instances off fail with
the following error if the instances are created with a single boot
command. eg. create 10 cirros instances through the horizon dashboard.
The instances are all KVM and backed by Cinder Volumes.
2017-09-19
After some brief discussion in #openstack-nova I've moved this to
oslo.log. The issue here appears to be that we spawn multiple separate
conductor processes writing to the same nova-conductor.log file. We
don't want to stop doing this, as it would break people.
It seems that by default python logg
Distro patch to unblock Ubuntu Pike UCA and Artful (needs conditional
check for general consumption).
** Patch added: "qemu-2.10-compat.patch"
https://bugs.launchpad.net/nova/+bug/1718295/+attachment/4953632/+files/qemu-2.10-compat.patch
** Changed in: nova
Status: Invalid => New
--
Public bug reported:
I'm looking at conductor logs generated by a customer running RH OSP 10
(Newton). The logs appear to be corrupt in a manner I'd expect to see if
2 processes were writing to the same log file simultaneously. For
example:
===
2017-09-14 15:54:39.689 120626 ERROR nova.servicegro
Since it is a wanted behavioral change in upstream qemu setting that task to
"Won't Fix" unless we come up with a reason to convince qemu to do so.
Once might argue that info should imply force-share or such, but unless we do
so make clear that no qemu change is expected.
James already mentioned
This appears like it might be an issue with the ppa in pike
** Also affects: qemu
Importance: Undecided
Status: New
** Project changed: qemu => ubuntu
** Package changed: ubuntu => qemu (Ubuntu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
Public bug reported:
Description
===
When instance rescheduling happens in cell:
1. Nova compute casts to the build_instances method in cell1 conductor.
2. In cell1 conductor, build_instances method calls the
scheduler_client.select_destinations method, it calls to scheduler for getting
Public bug reported:
There is no option in horizon to select subnet and Fixed IP while creating ports
According to openstack horizon design, port create form either takes a subnet
or a Fixed IP
According to the user docs
https://docs.openstack.org/releasenotes/horizon/newton.html
Port creation
Public bug reported:
- [X] This doc is inaccurate in this way: package named neutron-
linuxbridge-agent is unavailable, whereas neutron-plugin-linuxbridge-
agent is.
---
Release: 11.0.1.dev75 on 2017-09-14 04:10
SHA: 8baed13677c70cf4f1a17c5cc457c3b65bfead1b
Source
Marking this as Won't Fix per comment #8.
** Changed in: horizon
Status: Triaged => Won't Fix
--
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/1308189
Title:
As of Queens-1, the current panel is kept when switching projects. I am
not sure when it was implemented. Anyway the requested feature has been
implemented.
** Changed in: horizon
Status: In Progress => New
** Changed in: horizon
Status: New => Fix Released
--
You received this bu
Public bug reported:
When supplying a subport for a trunk with segmenation_id 0 Neutron
reports:
Invalid subport details '{u'segmentation_type': u'vlan', u'port_id':
u'449451c4-f134-4fbc-b405-df9109746e51', u'segmentation_id': 0}':
missing segmentation information. Must specify both segmentation_
This is related to LBaaS v1 API which has been dropped, and LBaas
dashboard is also no longer part of horizon. Marking this as Won't Fix.
** Changed in: horizon
Status: Confirmed => Won't Fix
** Changed in: horizon
Assignee: Verónica Musso (veronica-a-musso) => (unassigned)
** Change
Perhaps this still exists in the current horizon but there is no problem for
years, so I believe there is no need to fix this.
In addition, we are in the migration to Angular-based table.
** Changed in: horizon
Assignee: Gabriel Hurley (gabriel-hurley) => (unassigned)
** Changed in: horizon
Horizon side depends on Nova change and there seems no activity in nova
side. We, horizon team, remove horizon from the affected project and
would like to file a bug or a feature request once nova supports some
kind of feature on this.
** No longer affects: horizon
--
You received this bug notif
Per comment #6, there is nothing to do in horizon side. Marking this as
Invalid.
** 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 Identity (keystone).
https://bug
Reviewed: https://review.openstack.org/485121
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=905d31dd9715505599b0a2ad123eebef37f606f5
Submitter: Jenkins
Branch:master
commit 905d31dd9715505599b0a2ad123eebef37f606f5
Author: jichenjc
Date: Sun Jul 9 10:35:23 2017 +0800
horizon just displays hypervisor types returned from nova. This does not
affect horizon directly.
** No longer affects: horizon
--
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/b
Reviewed: https://review.openstack.org/505446
Committed:
https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=ee22ca8373abd3b5a4c44a9c5c4da39c511195c8
Submitter: Jenkins
Branch:master
commit ee22ca8373abd3b5a4c44a9c5c4da39c511195c8
Author: Matt Riedemann
Date: Wed Sep 20 00:29
Public bug reported:
I have 3 controllers and each controllers are running neutron-server.
When I delete router_gateway, some of the controllers occasionally crash
with DBDeadlock exceptions:
69597:2017-09-20 10:58:10.606 2114 ERROR neutron_lib.callbacks.manager
[req-31af8910-b348-49c4-9082-8647
https://review.openstack.org/#/c/486133/ has been merged.
** Changed in: neutron
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/1706061
Title:
Reviewed: https://review.openstack.org/502080
Committed:
https://git.openstack.org/cgit/openstack/ironic/commit/?id=2427ffca8bd0e2ab5127020ae6ffea9decfdc915
Submitter: Jenkins
Branch:master
commit 2427ffca8bd0e2ab5127020ae6ffea9decfdc915
Author: Dmitry Tantsur
Date: Fri Sep 8 16:44:24 201
Public bug reported:
The projects which deploy OpenStack from source or using python wheels
currently have to either carry templates for api-paste, policy and
rootwrap files or need to source them from git during deployment. This
results in some rather complex mechanisms which could be radically
s
86 matches
Mail list logo
