Public bug reported:
The case is: computenode1 and comptuenode3 share the storage from
sharedstrorage1, computenode3 has local disk. The expected result from
AllocationCandidates is (computenode1, sharedstorage1), (computenode2,
sharedstorage1) and (computenode3). But the current return is
(comput
Public bug reported:
a. i install ocata on two host, all agent work well, as below:
[root@controller openstack]# openstack network agent list
+--+++---+---+---+---+
| ID
** Changed in: nova
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/1709747
Title:
500 error MessagingTimeout from API when getting S
Public bug reported:
While attempting to deploy the attached hot template I ran into a few
issues:
1. Multiple router_centralized_snat interfaces are being created.
2. One router_centralized_snat interface is created, but it's Down.
When Multiple interfaces are created the stack can't be deleted
Public bug reported:
In EC2 clouds, the only way to determine whether an instance is
configured for IPv6 is by querying the metadata service. In order to
query metadata to determine network configuration, DataSourceEc2 needs
to configure the network with dhcp and then query the datasource.
Add op
Public bug reported:
In ng create instance form, we can create and import keypair, keypair
has quota management, when the keypair quota exceeded, if we create or
import keypair, it will fail and the API will return "Quota exceeded,
too many key pairs. (HTTP 403) (Request-ID: req-841e0499-ae34-4029
Public bug reported:
Pull in functionality from Ryan Harper's
https://git.launchpad.net/~raharper/+git/cloudinit-analyze into
cloudinit proper so that this tooling can be leveraged more easily by
any cloud-init consumer.
** Affects: cloud-init
Importance: Medium
Assignee: Chad Smith (c
Alternatively, do you see any issues in the nova-consoleauth logs?
** Changed in: nova
Status: Invalid => Incomplete
** Summary changed:
- HTTP exception thrown: Unexpected API Error.
+ 500 from API when getting SPICE console
** Summary changed:
- 500 from API when getting SPICE console
Is a spice console even properly configured and enabled on the compute
service for the instance?
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://b
This is a bug in the nova-lxd driver code, which manages bugs through
some other launchpad project.
** Tags added: lxd
** Changed in: nova
Status: New => Invalid
** Also affects: nova-lxd
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Public bug reported:
Aug 10 10:08:12 ubuntudbs devstack@n-api.service[8770]: ERROR
nova.api.openstack.extensions [None req-03396686-9700-4323-b7e5-1054fcc167d2
alt_demo admin] Unexpected exception in API method: MessagingTimeout: Timed out
waiting for a reply to message ID d5abd16bee8846eaa7644
Mitaka is EOL
** Changed in: keystone/mitaka
Status: Fix Committed => 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/1588860
Title:
keystone-ma
Mitaka is EOL
** Changed in: keystone/mitaka
Status: Fix Committed => 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/1579604
Title:
project del
Mitaka is EOL
** Changed in: keystone/mitaka
Status: New => Won't Fix
** Changed in: keystone/mitaka
Status: Won't Fix => Fix Released
** Changed in: keystone/mitaka
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Mitaka is EOL
** Changed in: keystone/mitaka
Status: Fix Committed => 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/1629446
Title:
federated l
As per lance, this is being marked as wont fix. we can re-visit when/if
microversions or v4 is implemented.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity
Mitaka is EOL
** Changed in: keystone/mitaka
Status: New => Won't Fix
** Changed in: keystone/mitaka
Status: Won't Fix => Fix Released
** Changed in: keystone/mitaka
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
I am marking this bug closed as the two patches in #17 have merged (inc.
the backport).
** Changed in: keystone
Status: New => Fix Released
** Changed in: keystone
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Yahoo!
Engineering Team
Unfortunately, we cannot change the behavior without a microversion
uspport or something similar. ?name= will need to maintain returning an
empty list, as that is the contract. I am closing this as wont fix.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notific
It looks like this was fixed a while ago. Feel free to reopen if I'm
mistaken.
** Changed in: tripleo
Status: Triaged => 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
Public bug reported:
when supplying cloud-init with a network-configuration in version:2
format, the rename code doesn't find any of the set-name parameters as
the function expects a v1 config format.
** Affects: cloud-init
Importance: Undecided
Status: New
--
You received this bu
As others have noted, the rpm upgrade process should handle updating the
rootwrap filters. The only exception would be if a user edited them
after installation, but in that case they're responsible for merging in
the updated ones themselves.
** Changed in: tripleo
Status: Triaged => Fix Re
Reviewed: https://review.openstack.org/477740
Committed:
https://git.openstack.org/cgit/openstack/cinder/commit/?id=6932f2a84171a44b29482cd3d5e93629e8e869d8
Submitter: Jenkins
Branch:master
commit 6932f2a84171a44b29482cd3d5e93629e8e869d8
Author: Felipe Monteiro
Date: Tue Jun 27 05:22:00 2
Public bug reported:
How to reproduce this:
In master(pike) horizon,
Go to Admin dashboard and networks panel
Click Create a network, give your network a name, select a project and
unclear "Create Subnet"
Click Create button and you should not be able to proceed.
See attached screenshot for m
This is likely fixed by these changes to use wsgi_intercept in our
compute API and Placement API fixtures:
https://github.com/openstack/nova/commit/fdf27abf7db233ca51f12e2926d78c272b54935b
https://github.com/openstack/nova/commit/eed6ced78776a3b9a7ada7b0c8ff74eaa376efaf
** Changed in: nova
** Changed in: keystone
Status: In Progress => Invalid
** Changed in: keystone
Assignee: Lance Bragstad (lbragstad) => (unassigned)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https:/
Reviewed: https://review.openstack.org/481794
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=9edda95f043cf5ba2cf02adf1d19ebfc413c9adf
Submitter: Jenkins
Branch:master
commit 9edda95f043cf5ba2cf02adf1d19ebfc413c9adf
Author: Ying Zuo
Date: Thu Jul 6 13:54:13 2017 -07
** Changed in: keystone
Status: Invalid => In Progress
** Changed in: keystone
Assignee: (unassigned) => Lance Bragstad (lbragstad)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https:/
Public bug reported:
Refer:
https://bugs.launchpad.net/neutron/+bug/1705351
And:
https://review.openstack.org/#/c/491851/
Sinkhole should simply return None when 'target' attribute is
referenced.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug no
Reviewed: https://review.openstack.org/491439
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=2bd7df84dcf8a45ce92b82f2360a1b39df522297
Submitter: Jenkins
Branch:master
commit 2bd7df84dcf8a45ce92b82f2360a1b39df522297
Author: Sylvain Bauza
Date: Mon Aug 7 13:03:37 2017 +
The reproducer is following:
kernel: 4.4.0-89-generic
conntrack: 1:1.4.3-3
conntrackd: 1:1.4.3-3
Create a conntrack entry:
sudo conntrack -I --protonum tcp --src 1.2.3.4 --sport 65535 --dst
8.8.8.8 --dport 6 --state ESTABLISHED --timeout 120
Trace from dmesg:
[ 2964.587682]
Reviewed: https://review.openstack.org/363585
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=ef85c99f5e5ba091b6711d76c88d50aa2dae6989
Submitter: Jenkins
Branch:master
commit ef85c99f5e5ba091b6711d76c88d50aa2dae6989
Author: jichenjc
Date: Sun Jul 31 21:42:01 2016 +0800
This bug was fixed in the package neutron - 2:8.4.0-0ubuntu4
---
neutron (2:8.4.0-0ubuntu4) xenial; urgency=medium
* d/p/Update-the-host_id-for-network-router_gateway-interf.patch:
keep the router's gateway interface updated when keepalived
fails over (LP: #1694337).
-- Fe
This bug was fixed in the package neutron - 2:10.0.2-0ubuntu1.1
---
neutron (2:10.0.2-0ubuntu1.1) zesty; urgency=medium
* d/p/Update-the-host_id-for-network-router_gateway-interf.patch:
keep the router's gateway interface updated when keepalived fails
over (LP: #1694337).
** 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/1708316
Title:
Nova send wrong information when there are several netw
Public bug reported:
The test in on XenServer.
nova live-migration
If we run the live-migration without the option of "--block-migrate", it will
failed with error as:
RemoteError: Remote error: RemoteError Remote error: CantStartEngineError No
sql_connection parameter is established"
- Th
woops... neutron-fwaas-dashboard is not affected.
** No longer affects: neutron-fwaas-dashboard
--
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/1406333
Title:
LOG m
neutron-fwaas-dashboard and neutron-vpnaas-dashboard are affected. They
were split out from horizon after the fix for this bug was merged, but
unfortunately the split out codes were prepared before the fix was
merged. Needs to take care of it.
** Also affects: neutron-fwaas-dashboard
Importance
Public bug reported:
Steps to reproduce
==
1. Create instance with (for example) qemu as nova-compute backend.
2. Change nova-compute backend to (for example) lxd.
3. Restart nova-compute service
Expected result
===
I expected to see an error with something like this:
Public bug reported:
fullstack issues "ovs-ofctl add-flow br-test-foo
ct_state=+trk,actions=drop" to confirm conntrack support but results in:
http://logs.openstack.org/18/489918/4/check/gate-neutron-dsvm-fullstack-
ubuntu-xenial/f9aa19e/console.html#_2017-08-09_05_24_52_006295
Stderr: sudo: no
40 matches
Mail list logo
