Public bug reported:
openflow connection is sometimes lost and the subsequent openflow command
fails. ~70 occurences in a week in logstash search.
Retrying should save such cases.
example:
http://logs.openstack.org/98/436798/25/check/gate-tempest-dsvm-neutron-
@mriedem The issue is in nova/virt/vmwareapi/virt.py. This is where the
network type is being set for the instance.
** Description changed:
- For NSX-mh, network type is being set to opaque, but that does not
- appear to be valid.
-
+ When nova-vmware is used as compute with NSX-mh neutron
Reviewed: https://review.openstack.org/396800
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=c73e1c8fa82c8059d0c8e8848413380ab6050ad5
Submitter: Jenkins
Branch:master
commit c73e1c8fa82c8059d0c8e8848413380ab6050ad5
Author: Cindy Lu
Date: Fri Nov
Public bug reported:
http://logs.openstack.org/03/444603/5/check/gate-neutron-dsvm-
functional-ubuntu-xenial/52405e2/testr_results.html.gz
Traceback (most recent call last):
File "neutron/tests/base.py", line 116, in func
return f(self, *args, **kwargs)
File
[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 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/1646327
Public bug reported:
Networking-ovn used neutron.agent.ovsdb.native.connection[1] to connect
OVN_Northbound and OVN_Southbound, but it need not to enable_connection_uri
when get_schema_helper, thus get_schema_helper was overrided[2].
Latter the main code in connect.get_schema_helper was moved
Public bug reported:
I understand there are code to clean up the instance directory on the
target host if the live migration failed, but the directory is not
cleanup if libvirt's connection is timeout.
I haven't got a change to root cause the issue, but I feel the code
could be optimized a
I'm not sure what this has to do with Nova, so I'm marking this as
invalid for Nova.
** Changed in: nova
Status: New => Invalid
** Tags added: vmware
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute
6.5 OS updates was in https://review.openstack.org/#/c/403492
** Changed in: nova
Status: In Progress => Fix Released
** Changed in: nova
Assignee: xhzhf (guoyongxhzhf) => Eric Brown (ericwb)
** Changed in: nova
Importance: Undecided => Low
--
You received this bug notification
And to be clear, you have custom image metadata properties that are not
part of the ImageMetaProps object? That's why they get filtered out of
the object.
Also, this is in the zvm virt driver right?
image_meta = self._image_api.get(context, image_meta.id)
And that's specifically because the zvm
Srinivas - the compute API never blocks a delete request, unless the
server is locked. So by design you can attempt to delete a server in any
case where it's unlocked (if you're an admin you can bypass the locked
state too). So we aren't going to put a conditional on the delete API
such that you
Public bug reported:
Similar to https://bugs.launchpad.net/neutron/+bug/1533013, l2pop can
puke out exceptions when a port is deleted that has a host corresponding
to either no agent or an agent without a tunneling_ip.
2017-03-09 01:34:17.432 42625 ERROR neutron.plugins.ml2.managers
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova/ocata
Status: New => Confirmed
** Changed in: nova/ocata
Importance: Undecided => High
** Tags added: ocata-backport-potential
--
You received this bug notification because you are a member
** Changed in: neutron-lbaas-dashboard
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/1608980
Title:
Remove MANIFEST.in as it is not explicitly
Marking this invalid as you can delete a pool via horizon. Did you
remember to delete the health monitor first?
I agree that in the future we could enable the cascade delete feature in
horizon with a warning, but that would be an RFE and not the bug as
reported. Closing this as invalid as you
Public bug reported:
Since we have switched to using the OVS firewall for the OVS scenario,
the job has been failing with a timeout in connectivity.
There are errors in the agent log that look suspect:
2017-03-10 06:12:47.785 1325 ERROR
neutron.agent.linux.openvswitch_firewall.firewall
*** This bug is a duplicate of bug 1670627 ***
https://bugs.launchpad.net/bugs/1670627
For master (pike) this is the fix:
https://review.openstack.org/#/c/443403/
For ocata, the fix will be a backport of this:
https://review.openstack.org/#/c/443395/
** This bug has been marked a
Reviewed: https://review.openstack.org/443395
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=018068c4caac324643c7c6a4360fad855dd096eb
Submitter: Jenkins
Branch:master
commit 018068c4caac324643c7c6a4360fad855dd096eb
Author: Matt Riedemann
Date:
Public bug reported:
GET /v2.0/networks/{network_id} API responds with \u escaped Unicode characters
even though the request headers specify that the client will only accept UTF-8
encdoding.
Both these headers were tried, with same result : “Accept:
Public bug reported:
GET ‘servers’ API responds with \u escaped Unicode characters even though the
request headers specify that the client will only accept UTF-8 encdoding.
Both these headers were tried, with same result : “Accept:
** Also affects: python-openstackclient
Importance: Undecided
Status: New
** Changed in: python-openstackclient
Assignee: (unassigned) => David Rabel (rabel-b1)
** No longer affects: python-openstackclient
--
You received this bug notification because you are a member of Yahoo!
This is a neutron DVR bug and not an LBaaS/Octavia bug. It may be a
duplicate of existing DVR bugs.
** Project changed: octavia => neutron
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
You have been subscribed to a public bug:
I reported #1629539, which was on Mitaka/LBaaSv1, but I'm seeing the
exact same behaviour on Newton/LBaaSv2.
There's apparently a fix (for Kilo) in #1493809. There's also #1494003
(a duplicate of #1493809), which have a lot of debug output and
apparently
>From description you provided it doesn't look like an error.
> Unable to create allocation for 'MEMORY_MB' on resource provider
'610ee875-405e-4738-8099-5a218fa4986f'. The requested amount would
violate inventory constraints.
means that on compute node you don't have enough memory resource.
You
Public bug reported:
Normally dhcp agents should not provide routable services. There is one
exception: monitoring. Checking dhcp agents availability by sending PING
requests is very easy and sits well with existing monitoring frameworks.
Outside of checking of availability of DHCP agent itself
Public bug reported:
While testing the ocata codebase, it seems that the addition of the
multifactor auth in core, breaks our LDAP identity backend.
We are getting an exception while loading the user to check if it has
MFA enabled or not. The LDAP identity driver does not provide a options
** Also affects: nova/ocata
Importance: Undecided
Status: New
** Changed in: nova/ocata
Assignee: (unassigned) => Lee Yarwood (lyarwood)
** Changed in: nova/ocata
Status: New => In Progress
** Changed in: nova/ocata
Importance: Undecided => Low
** Tags added: libvirt
Reviewed: https://review.openstack.org/444357
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=abd18a12e3e6b571d35499857a005a7bfd7237a4
Submitter: Jenkins
Branch:master
commit abd18a12e3e6b571d35499857a005a7bfd7237a4
Author: Ionuț Bîru
Date: Fri Mar 10
Public bug reported:
I have recently installed a new Openstackcloud.
One controller and two nova nodes. When I tried to launch a new instance I got
an error.
I could only launch instance on the controller node, but not on the two nova
nodes.
The error message I got was:
==>
*** This bug is a duplicate of bug 1634696 ***
https://bugs.launchpad.net/bugs/1634696
** This bug has been marked a duplicate of bug 1634696
Leading or trailing space in name throws error for new or updated Instances
** Changed in: horizon
Milestone: next => None
** Changed in:
Going to close this as the bug report is really too vague without the
original driver.
** 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,
*** This bug is a duplicate of bug 1558917 ***
https://bugs.launchpad.net/bugs/1558917
** Changed in: horizon
Assignee: Kevin Chen (kevchentw) => (unassigned)
** Changed in: horizon
Status: In Progress => Triaged
** This bug has been marked a duplicate of bug 1558917
When
Reviewed: https://review.openstack.org/443752
Committed:
https://git.openstack.org/cgit/openstack/cinder/commit/?id=52310fa8645cc10b91de7d2b4e10a3b42d4ef073
Submitter: Jenkins
Branch:master
commit 52310fa8645cc10b91de7d2b4e10a3b42d4ef073
Author: Eric Harney
Date: Thu
UI Bootstrap is capped via upper-constraints for Mitaka:
https://github.com/openstack/requirements/blob/stable/mitaka/upper-
constraints.txt#L34
If you're not using upper constraints in your installations, you're
going to make life very difficult for yourself :)
** Changed in: horizon
Public bug reported:
I reported #1629539, which was on Mitaka/LBaaSv1, but I'm seeing the
exact same behaviour on Newton/LBaaSv2.
There's apparently a fix (for Kilo) in #1493809. There's also #1494003
(a duplicate of #1493809), which have a lot of debug output and
apparently a way to reproduce.
Public bug reported:
Deferred bridge doesn't obey of_interface:
https://git.openstack.org/cgit/openstack/neutron/tree/neutron/agent/common/ovs_lib.py?id=fbe8f9eddbdd61e6692b92c57b930f17923a0ed7#n340
and instead always calls ovs-ofctl.
** Affects: neutron
Importance: Undecided
Assignee:
Public bug reported:
Kolla stable/ocata on ubuntu xenial
Neutron log:
2017-03-13 04:40:12.948 23 INFO neutron.db.db_base_plugin_v2
[req-7f8f0445-f5b9-4bf5-b8e0-f298954a6a95 e0dc60aa4ad342f6807613e4d6203baa
3f243f2f6d2547128217c34f850315f6 - - -] Found port
Public bug reported:
As per this https://review.openstack.org/#/c/401245/ UI bootstrap issue
has been fixed in master but when I checkout `stable/mitaka` I get these
errors and modal doesn't work for my plugin.
For now I've patched horizon (mitaka) with similar changes. Would like
to know reason
Reviewed: https://review.openstack.org/444769
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=f54c52418bdae0403353447d688b77be15e8a044
Submitter: Jenkins
Branch:master
commit f54c52418bdae0403353447d688b77be15e8a044
Author: Akihiro Motoki
Date:
Public bug reported:
When accessing images page, the following error raised:
error invoking apiclient
Traceback (most recent call last):
File "/opt/stack/horizon/openstack_dashboard/api/rest/utils.py", line 131, in
_wrapped
return JSONResponse(data, json_encoder=json_encoder)
File
Can't reproduce with the latest master
** Changed in: horizon
Status: New => Opinion
--
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/1671921
Title:
Boot
Public bug reported:
I installed according to the official document, when to start the nova-compute
error.
Then i check the/var/log/nova/nova-ompute.log,found e error for
oslo_service:PlacementNotConfigured: This com.ute is not configured to talk to
the placement service, Configure
43 matches
Mail list logo