[Yahoo-eng-team] [Bug 1819569] [NEW] Swap volumes of vm failed: pivot of disk 'vdb' requires an active copy job
Public bug reported:
Description
===
I had one volume, vol-1 attached to two VMs, vm-1 and vm-2, then tried
to swap vm-1's volume to another volume vol-2, but failed.
The Cinder backend attached the volume to vm successfully.
Nova reported below error:
Mar 08 01:34:42.984286 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver [None req-1033d1c1-bd3b-4990-a8da-e503d25a041b
tempest-TestMultiAttachVolumeSwap-890516006
tempest-TestMultiAttachVolumeSwap-890516006] Failure rebasing volume /dev/sdj
on vdb.: libvirt.libvirtError: Requested operation is not valid: pivot of disk
'vdb' requires an active copy job
Mar 08 01:34:42.984521 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver Traceback (most recent call last):
Mar 08 01:34:42.984846 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/opt/stack/new/nova/nova/virt/libvirt/driver.py", line 1557, in _swap_volume
Mar 08 01:34:42.985032 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver dev.abort_job(pivot=True)
Mar 08 01:34:42.985214 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/opt/stack/new/nova/nova/virt/libvirt/guest.py", line 754, in abort_job
Mar 08 01:34:42.986537 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver self._guest._domain.blockJobAbort(self._disk,
flags=flags)
Mar 08 01:34:42.986914 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/usr/local/lib/python3.5/dist-packages/eventlet/tpool.py", line 190, in doit
Mar 08 01:34:42.987246 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver result = proxy_call(self._autowrap, f, *args,
**kwargs)
Mar 08 01:34:42.987608 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/usr/local/lib/python3.5/dist-packages/eventlet/tpool.py", line 148, in
proxy_call
Mar 08 01:34:42.987958 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver rv = execute(f, *args, **kwargs)
Mar 08 01:34:42.988276 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/usr/local/lib/python3.5/dist-packages/eventlet/tpool.py", line 129, in execute
Mar 08 01:34:42.988434 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver six.reraise(c, e, tb)
Mar 08 01:34:42.988591 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/usr/local/lib/python3.5/dist-packages/six.py", line 693, in reraise
Mar 08 01:34:42.988746 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver raise value
Mar 08 01:34:42.988895 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/usr/local/lib/python3.5/dist-packages/eventlet/tpool.py", line 83, in tworker
Mar 08 01:34:42.989045 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver rv = meth(*args, **kwargs)
Mar 08 01:34:42.989194 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver File
"/usr/local/lib/python3.5/dist-packages/libvirt.py", line 772, in blockJobAbort
Mar 08 01:34:42.989366 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver if ret == -1: raise libvirtError
('virDomainBlockJobAbort() failed', dom=self)
Mar 08 01:34:42.989516 UnityiSCSISlave nova-compute[19437]: ERROR
nova.virt.libvirt.driver libvirt.libvirtError: Requested operation is not
valid: pivot of disk 'vdb' requires an active copy job
Steps to reproduce
==
1. In OpenStack, attach a volume, vol-1 to two vms, vm-1 and vm-2. Volume vol-1
is provisioned on external storage system.
2. Swap vol-1 of vm-1 to another volume, vol-2.
Actual results
==
You can see above failure: Failure rebasing volume /dev/sdj (vol-2) on
vdb.
Expected results
vm-1's volume updated to vol-2.
Environment
===
OpenStack: master (Stein) devstack
libvirt-python: 5.1.0
libvirt-bin: 4.0.0-1ubuntu8.5~cloud0
Logs
1. Full n-cpu log locates:
http://publiclogs.emc.com/51/633451/5/check/EMC_Unity_iSCSI/a2d0e05/EMC_Unity_iSCSI/1218/logs/screen-n-cpu.txt.gz
Search via request id: req-1033d1c1-bd3b-4990-a8da-e503d25a041b
2. libvirt log is attached.
If you need more info, please let me know.
** Affects: nova
Importance: Undecided
Status: New
** Tags: libvirt
** Attachment added: "libvirtd log"
https://bugs.launchpad.net/bugs/1819569/+attachment/5245583/+files/libvirtd.log
--
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/1819569
Title:
Swap volumes of vm failed: pivot of disk 'vdb' requires an active copy
job
Status in OpenStack Compute (nova):
New
Bug description:
Description
===
I had one volume, vol-1 attached to two VMs, vm-1 and vm-2, then tried
to swap vm-1's volume to another volume vol-2, but failed.
The Cinder
[Yahoo-eng-team] [Bug 1819568] [NEW] network_data.json doesn't contain information about floating IPs
Public bug reported: Don't seem to be able to get floating IP information from openstack metadata network_data.json I can get this via EC2 metadata and would be good if it was in openstack metadata too ** 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/1819568 Title: network_data.json doesn't contain information about floating IPs Status in OpenStack Compute (nova): New Bug description: Don't seem to be able to get floating IP information from openstack metadata network_data.json I can get this via EC2 metadata and would be good if it was in openstack metadata too To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1819568/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1818047] Re: nova-status doesn't render cell DB connection strings before use
Reviewed: https://review.openstack.org/641021
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=38f2ce549ce4b21d5085824df701f9d2392b5604
Submitter: Zuul
Branch:master
commit 38f2ce549ce4b21d5085824df701f9d2392b5604
Author: Matt Riedemann
Date: Tue Mar 5 09:00:20 2019 -0500
Handle templated cell mappings in nova-status
The nova-status upgrade check code is intentionally written
to not use versioned objects and just work with the data model
directly.
However, CellMapping database_connection template support was
added in Rocky and the template URL is only formatted when using
the object on read from the database, which means if you are using
a template for the database_connection nova-status will break since
the get_engine() code is getting a template string rather than a
properly formatted URL.
This change fixes the bug by using the CellMapping object code to
pull the mappings from the database which will format the database
connection URL. Note that we cannot simply update the sqlalchemy
RowProxy objects we get normally since those are read-only, and
because of how the mappings are used as objects with attribute
access rather than as a dict we cannot just convert the RowProxy
to a dict - we would have to put it in some kind of object for
attribute access and if we are going to do that we might as well
just use the CellMapping objects we have so that's what we do in
this change.
Change-Id: I5ce175517f6feb6e82ba507078a565b71427a4b0
Closes-Bug: #1818047
** Changed in: nova
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/1818047
Title:
nova-status doesn't render cell DB connection strings before use
Status in OpenStack Compute (nova):
Fix Released
Status in OpenStack Compute (nova) rocky series:
Triaged
Bug description:
Description
===
I've been working on introducing basic upgrade check calls in TripleO
but have encountered the following issue now template based db
connection strings are being used by TripleO in support of cellsv2:
$ nova-status upgrade check
[..]
ArgumentError: Could not parse rfc1738 URL from string
'{scheme}://{username}:{password}@{hostname}/nova?{query}'
http://logs.openstack.org/39/635139/2/check/tripleo-ci-
centos-7-standalone/91d4b45/logs/undercloud/home/zuul/standalone_deploy.log.txt.gz#_2019-02-26_22_04_00
Steps to reproduce
==
http://logs.openstack.org/39/635139/2/check/tripleo-ci-
centos-7-standalone/91d4b45/logs/reproducer-quickstart.sh
Expected result
===
Connection string is formatted correctly before use.
Actual result
=
Connection string is not formatted before use leading to `nova-status`
errors.
Environment
===
1. Exact version of OpenStack you are running. See the following
list for all releases: http://docs.openstack.org/releases/
Master / Stein
2. Which hypervisor did you use?
(For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
What's the version of that?
N/A
2. Which storage type did you use?
(For example: Ceph, LVM, GPFS, ...)
What's the version of that?
N/A
3. Which networking type did you use?
(For example: nova-network, Neutron with OpenVSwitch, ...)
N/A
Logs & Configs
==
See above.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1818047/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819260] Re: Adding floating IP fails with SQLA 1.3.0
Reviewed: https://review.openstack.org/642117 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=c04b8ddd907d786c0ea2fccd31b82561f2cdb8fc Submitter: Zuul Branch:master commit c04b8ddd907d786c0ea2fccd31b82561f2cdb8fc Author: Mike Bayer Date: Fri Mar 8 14:09:14 2019 -0500 Join on explcit relationship paths The join() in get_router_for_floatingip() is joining from entity to entity without an explicit ON clause which creates an ambiguous situation. SQLAlchemy 1.3 guards against this now, so use the real relationship-bound path so that the ORM does not need to guess. Closes-bug: #1819260 Change-Id: Ia377a9d1a32a78abdaee74c79e395acd77e486ef ** 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/1819260 Title: Adding floating IP fails with SQLA 1.3.0 Status in neutron: Fix Released Bug description: Hi, Trying to evaluate if we can upgrade Buster to SQLAlchemy 1.3.0, doing this in my PoC: openstack server add floating ip demo-server 192.168.105.101 leads to this stack dump below. Obviously, there's something wrong that needs fixing. Best would be before Stein is out. 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource [req-2ca7dd4c-515f-4958-964c-8506811c0b5a a498c39ddde54be4aafa7b3ded5563e6 9e0e0a4c736a4687ade8c5e765353bd7 - default default] update failed: No details.: sqlalchemy.exc.InvalidRequestError: Can't determine which FROM clause to join from, there are multiple FROMS which can join to this entity. Try adding an explicit ON clause to help resolve the ambiguity. 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource Traceback (most recent call last): 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/api/v2/resource.py", line 98, in resource 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource result = method(request=request, **args) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron/api/v2/base.py", line 626, in update 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource return self._update(request, id, body, **kwargs) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 140, in wrapped 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource setattr(e, '_RETRY_EXCEEDED', True) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource self.force_reraise() 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource raise value 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 136, in wrapped 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_db/api.py", line 154, in wrapper 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource self.force_reraise() 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/six.py", line 693, in reraise 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource raise value 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/oslo_db/api.py", line 142, in wrapper 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2019-03-09 10:31:26.785 624233 ERROR neutron.api.v2.resource File "/usr/lib/python3/dist-packages/neutron_lib/db/api.py", line 183, in wrapped 2019-03-09 10:31:26.785 624233 ERROR
[Yahoo-eng-team] [Bug 1696830] Re: nova-placement-api default config files is too strict
After speaking with coreycb we're going to drop nova/placement from this as it no longer quite fits and the existing snap related bugs are sufficient to provide an aide-mémoire. ** Changed in: nova 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 Compute (nova). https://bugs.launchpad.net/bugs/1696830 Title: nova-placement-api default config files is too strict Status in OpenStack Compute (nova): Won't Fix Status in oslo.config: Fix Released Status in Glance Snap: Fix Released Status in Keystone Snap: Fix Released Status in Neutron Snap: Fix Released Status in Nova Snap: Fix Released Status in Nova Hypervisor Snap: Fix Released Bug description: If nova.conf doesn't exist in the typical location of /etc/nova/nova.conf and OS_PLACEMENT_CONFIG_DIR isn't set, nova- placement-api's wsgi application will fail. In our case with the OpenStack snap, we have two possible paths we may pick nova.conf up from, based on what --config-file specifies. I think the right answer here is to be a bit more flexible and not set the default config file if it's path doesn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696830/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819374] Re: test_interface_detach_with_port_with_bandwidth_request intermittently fails
Reviewed: https://review.openstack.org/642387
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=d52c8fea06e333c9cda42eb60925a112203fc83a
Submitter: Zuul
Branch:master
commit d52c8fea06e333c9cda42eb60925a112203fc83a
Author: Balazs Gibizer
Date: Mon Mar 11 10:05:02 2019 +0100
fix race in test_interface_detach_with_port_with_bandwidth_request
During port detach the unbind towards neutron happens before the
port allocation is removed from placement. The functional test only
waited for the port unbind before asserted the remaining allocations and
therefore it was racy.
Fortunately the instance.interface_detach.end is emitted after the both
the unbind and the allocation shrink. So the test is changed to wait for
this notification instead.
Change-Id: I53d76d6353ae634e387672e14943f518955b221e
Closes-Bug: #1819374
** Changed in: nova
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/1819374
Title:
test_interface_detach_with_port_with_bandwidth_request intermittently
fails
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Seen here:
http://logs.openstack.org/21/641021/1/gate/nova-tox-functional-
py35/b057262/job-output.txt.gz#_2019-03-09_17_01_22_053827
2019-03-09 17:01:22.053827 | ubuntu-xenial | {1}
nova.tests.functional.test_servers.PortResourceRequestBasedSchedulingTest.test_interface_detach_with_port_with_bandwidth_request
[3.961215s] ... FAILED
2019-03-09 17:01:22.053957 | ubuntu-xenial |
2019-03-09 17:01:22.053999 | ubuntu-xenial | Captured pythonlogging:
2019-03-09 17:01:22.054050 | ubuntu-xenial | ~~~
2019-03-09 17:01:22.054142 | ubuntu-xenial | b'2019-03-09 17:01:18,266
WARNING [placement.db_api] TransactionFactory already started, not
reconfiguring.'
2019-03-09 17:01:22.054231 | ubuntu-xenial | b'2019-03-09 17:01:19,023
INFO [nova.service] Starting conductor node (version 18.1.0)'
2019-03-09 17:01:22.054328 | ubuntu-xenial | b'2019-03-09 17:01:19,046
INFO [nova.service] Starting scheduler node (version 18.1.0)'
2019-03-09 17:01:22.054415 | ubuntu-xenial | b"2019-03-09 17:01:19,073
INFO [nova.virt.driver] Loading compute driver
'fake.FakeDriverWithPciResources'"
2019-03-09 17:01:22.054558 | ubuntu-xenial | b'2019-03-09 17:01:19,073
WARNING [nova.compute.monitors] Excluding nova.compute.monitors.cpu monitor
virt_driver. Not in the list of enabled monitors (CONF.compute_monitors).'
2019-03-09 17:01:22.054651 | ubuntu-xenial | b'2019-03-09 17:01:19,075
INFO [nova.service] Starting compute node (version 18.1.0)'
2019-03-09 17:01:22.054800 | ubuntu-xenial | b'2019-03-09 17:01:19,104
WARNING [nova.compute.manager] No compute node record found for host host1. If
this is the first time this service is starting on this host, then you can
ignore this warning.'
2019-03-09 17:01:22.054886 | ubuntu-xenial | b'2019-03-09 17:01:19,110
WARNING [nova.compute.resource_tracker] No compute node record for host1:host1'
2019-03-09 17:01:22.055002 | ubuntu-xenial | b'2019-03-09 17:01:19,115
INFO [nova.compute.resource_tracker] Compute node record created for
host1:host1 with uuid: 0e59ca49-7858-479c-8b7c-13a78199a981'
2019-03-09 17:01:22.055174 | ubuntu-xenial | b'2019-03-09 17:01:19,167
INFO [placement.requestlog] 127.0.0.1 "GET
/placement/resource_providers?in_tree=0e59ca49-7858-479c-8b7c-13a78199a981"
status: 200 len: 26 microversion: 1.14'
2019-03-09 17:01:22.055329 | ubuntu-xenial | b'2019-03-09 17:01:19,178
INFO [placement.requestlog] 127.0.0.1 "POST /placement/resource_providers"
status: 200 len: 828 microversion: 1.20'
2019-03-09 17:01:22.055522 | ubuntu-xenial | b'2019-03-09 17:01:19,179
INFO [nova.scheduler.client.report] [req-40799b9c-9042-4da4-bd70-e4afd7bc1632]
Created resource provider record via placement API for resource provider with
UUID 0e59ca49-7858-479c-8b7c-13a78199a981 and name host1.'
2019-03-09 17:01:22.055677 | ubuntu-xenial | b'2019-03-09 17:01:19,196
INFO [placement.requestlog] 127.0.0.1 "PUT
/placement/resource_providers/0e59ca49-7858-479c-8b7c-13a78199a981/inventories"
status: 200 len: 399 microversion: 1.26'
2019-03-09 17:01:22.055888 | ubuntu-xenial | b'2019-03-09 17:01:19,204
INFO [placement.requestlog] 127.0.0.1 "GET
/placement/traits?name=in:COMPUTE_VOLUME_MULTI_ATTACH,COMPUTE_TRUSTED_CERTS,COMPUTE_NET_ATTACH_INTERFACE_WITH_TAG,COMPUTE_VOLUME_EXTEND,COMPUTE_VOLUME_ATTACH_WITH_TAG,COMPUTE_NET_ATTACH_INTERFACE"
status: 200 len: 200 microversion: 1.6'
2019-03-09 17:01:22.056067 | ubuntu-xenial | b'2019-03-09 17:01:19,222
INFO [placement.requestlog] 127.0.0.1 "PUT
/placement/resource_providers/0e59ca49-7858-479c-8b7c-13a78199a981/traits"
status: 200 len: 235
[Yahoo-eng-team] [Bug 1816647] Re: Unable to dump policy using oslopolicy-policy-generator for glance
Reviewed: https://review.openstack.org/637985 Committed: https://git.openstack.org/cgit/openstack/glance/commit/?id=517d8d66c3083bdbe85784ade73d85d0b4ddd83b Submitter: Zuul Branch:master commit 517d8d66c3083bdbe85784ade73d85d0b4ddd83b Author: Cyril Roelandt Date: Tue Feb 19 20:32:11 2019 +0100 Add an oslo.policy.enforcer entrypoint This will allow oslopolicy-policy-generator to generate useful information about Glance policies. Change-Id: I3aeeeb67d19832ad72f0ab06c8adc0b018020c71 Closes-Bug: #1816647 ** Changed in: glance Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1816647 Title: Unable to dump policy using oslopolicy-policy-generator for glance Status in Glance: Fix Released Bug description: Steps to reproduce: $ cd glance/ # Using the master branch $ python3 -m venv vvv (vvv) $ source vvv/bin/activate (vvv) $ pip install oslo.policy (vvv) $ pip install -r requirements.txt (vvv) $ python setup.py install (vvv) $ oslopolicy-policy-generator --namespace glance WARNING:stevedore.named:Could not load glance Traceback (most recent call last): File "/home/cyril/tmp/oslopo/glance/vvv/bin/oslopolicy-policy-generator", line 10, in sys.exit(generate_policy()) File "/home/cyril/tmp/oslopo/glance/vvv/lib/python3.7/site-packages/oslo_policy/generator.py", line 338, in generate_policy _generate_policy(conf.namespace, conf.output_file) File "/home/cyril/tmp/oslopo/glance/vvv/lib/python3.7/site-packages/oslo_policy/generator.py", line 283, in _generate_policy enforcer = _get_enforcer(namespace) File "/home/cyril/tmp/oslopo/glance/vvv/lib/python3.7/site-packages/oslo_policy/generator.py", line 87, in _get_enforcer enforcer = mgr[namespace].obj File "/home/cyril/tmp/oslopo/glance/vvv/lib/python3.7/site-packages/stevedore/extension.py", line 326, in __getitem__ return self._extensions_by_name[name] KeyError: 'glance' To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1816647/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819477] [NEW] [OVS] When cleaning min QoS, queue could be already deleted
Public bug reported: When OVS agent is started and QoS extension is enabled, the minimum bandwidth QoS and Queues are deleted [1]-->[2]. Although is not possible to have a QoS with deleted Queues assigned (a "referential integrity violation" will be risen), a race condition could happen during functional and fullstack tests [3]. While deleting the Queues referred in the Qos register, an exception catch should be added to hide if the Queue is already deleted. In this case there is no need to raise this exception. [1] https://github.com/openstack/neutron/blob/590002728d4686cb947391911534c4d42f36cfb5/neutron/plugins/ml2/drivers/openvswitch/agent/extension_drivers/qos_driver.py#L57 [2] https://github.com/openstack/neutron/blob/590002728d4686cb947391911534c4d42f36cfb5/neutron/agent/common/ovs_lib.py#L992 [3] http://logs.openstack.org/95/642295/2/check/neutron-fullstack/26d552e/logs/dsvm-fullstack-logs/TestDscpMarkingQoSOvs.test_dscp_marking_packets_openflow-cli_/neutron-openvswitch-agent--2019-03-11--12-30-51-339462.txt.gz#_2019-03-11_12_30_57_450 ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1819477 Title: [OVS] When cleaning min QoS, queue could be already deleted Status in neutron: New Bug description: When OVS agent is started and QoS extension is enabled, the minimum bandwidth QoS and Queues are deleted [1]-->[2]. Although is not possible to have a QoS with deleted Queues assigned (a "referential integrity violation" will be risen), a race condition could happen during functional and fullstack tests [3]. While deleting the Queues referred in the Qos register, an exception catch should be added to hide if the Queue is already deleted. In this case there is no need to raise this exception. [1] https://github.com/openstack/neutron/blob/590002728d4686cb947391911534c4d42f36cfb5/neutron/plugins/ml2/drivers/openvswitch/agent/extension_drivers/qos_driver.py#L57 [2] https://github.com/openstack/neutron/blob/590002728d4686cb947391911534c4d42f36cfb5/neutron/agent/common/ovs_lib.py#L992 [3] http://logs.openstack.org/95/642295/2/check/neutron-fullstack/26d552e/logs/dsvm-fullstack-logs/TestDscpMarkingQoSOvs.test_dscp_marking_packets_openflow-cli_/neutron-openvswitch-agent--2019-03-11--12-30-51-339462.txt.gz#_2019-03-11_12_30_57_450 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1819477/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819460] [NEW] instance stuck in BUILD state due to unhandled exceptions in conductor
Public bug reported: There are two calls[1][2] during ConductorTaskManager.build_instances, used during re-schedule, that could potentially raise exceptions which leads to that the instance is stuck in BUILD state instead of going to ERROR state. [1] https://github.com/openstack/nova/blob/892ead1438abc9a8a876209343e6a85c80f0059f/nova/conductor/manager.py#L670 [2] https://github.com/openstack/nova/blob/892ead1438abc9a8a876209343e6a85c80f0059f/nova/conductor/manager.py#L679 ** Affects: nova Importance: Low Assignee: Balazs Gibizer (balazs-gibizer) Status: New ** Tags: conductor re-schedule ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) ** Changed in: nova Importance: Undecided => Low ** Tags added: conductor ** Tags added: re-schedule -- 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/1819460 Title: instance stuck in BUILD state due to unhandled exceptions in conductor Status in OpenStack Compute (nova): New Bug description: There are two calls[1][2] during ConductorTaskManager.build_instances, used during re-schedule, that could potentially raise exceptions which leads to that the instance is stuck in BUILD state instead of going to ERROR state. [1] https://github.com/openstack/nova/blob/892ead1438abc9a8a876209343e6a85c80f0059f/nova/conductor/manager.py#L670 [2] https://github.com/openstack/nova/blob/892ead1438abc9a8a876209343e6a85c80f0059f/nova/conductor/manager.py#L679 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1819460/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819453] Re: keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType' object
** Also affects: keystone
Importance: Undecided
Status: New
--
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/1819453
Title:
keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType'
object
Status in OpenStack Identity (keystone):
New
Status in keystone package in Ubuntu:
New
Bug description:
Proposed action:
=
Key / value failed check error.
Should check key exists and warn user of bad users / continue
Bug presented by:
=
openstack user list --domain customerdata
cannot concatenate 'str' and 'NoneType' objects (HTTP 400) (Request-ID:
req-cc0e225d-d033-4dfa-aff8-7311389d4f58)
Trace:
==
(keystone.common.wsgi): 2019-03-11 12:30:47,154 ERROR cannot concatenate
'str' and 'NoneType' objects
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 228,
in __call__
result = method(req, **params)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
235, in wrapper
return f(self, request, filters, **kwargs)
File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py",
line 233, in list_users
return UserV3.wrap_collection(request.context_dict, refs, hints=hints)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
499, in wrap_collection
cls.wrap_member(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
468, in wrap_member
cls._add_self_referential_link(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
464, in _add_self_referential_link
ref['links']['self'] = cls.base_url(context) + '/' + ref['id']
TypeError: cannot concatenate 'str' and 'NoneType' objects
Offending Data:
===
@ line 233 i put LOG.debug( pprint.pformat( refs ) )
grep -b 2 "'id': None," /varlog/keystone/keystone.log
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
Platform:
=
cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
verions:
dpkg --list | grep keystone
ii keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Daemons
ii python-keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Python library
ii python-keystoneauth1 2.18.0-0ubuntu2~cloud0
all authentication library for OpenStack Identity - Python 2.7
ii python-keystoneclient1:3.10.0-0ubuntu1~cloud0
all client library for the OpenStack Keystone API - Python 2.x
ii python-keystonemiddleware4.14.0-0ubuntu1.2~cloud0
all Middleware for OpenStack Identity (Keystone) - Python 2.x
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1819453/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819453] Re: keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType' object
** Project changed: keystone => keystone (Ubuntu)
--
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/1819453
Title:
keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType'
object
Status in keystone package in Ubuntu:
New
Bug description:
Proposed action:
=
Key / value failed check error.
Should check key exists and warn user of bad users / continue
Bug presented by:
=
openstack user list --domain customerdata
cannot concatenate 'str' and 'NoneType' objects (HTTP 400) (Request-ID:
req-cc0e225d-d033-4dfa-aff8-7311389d4f58)
Trace:
==
(keystone.common.wsgi): 2019-03-11 12:30:47,154 ERROR cannot concatenate
'str' and 'NoneType' objects
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 228,
in __call__
result = method(req, **params)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
235, in wrapper
return f(self, request, filters, **kwargs)
File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py",
line 233, in list_users
return UserV3.wrap_collection(request.context_dict, refs, hints=hints)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
499, in wrap_collection
cls.wrap_member(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
468, in wrap_member
cls._add_self_referential_link(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
464, in _add_self_referential_link
ref['links']['self'] = cls.base_url(context) + '/' + ref['id']
TypeError: cannot concatenate 'str' and 'NoneType' objects
Offending Data:
===
@ line 233 i put LOG.debug( pprint.pformat( refs ) )
grep -b 2 "'id': None," /varlog/keystone/keystone.log
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
Platform:
=
cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
verions:
dpkg --list | grep keystone
ii keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Daemons
ii python-keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Python library
ii python-keystoneauth1 2.18.0-0ubuntu2~cloud0
all authentication library for OpenStack Identity - Python 2.7
ii python-keystoneclient1:3.10.0-0ubuntu1~cloud0
all client library for the OpenStack Keystone API - Python 2.x
ii python-keystonemiddleware4.14.0-0ubuntu1.2~cloud0
all Middleware for OpenStack Identity (Keystone) - Python 2.x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keystone/+bug/1819453/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819453] [NEW] keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType' object
Public bug reported:
Proposed action:
=
Key / value failed check error.
Should check key exists and warn user of bad users / continue
Bug presented by:
=
openstack user list --domain customerdata
cannot concatenate 'str' and 'NoneType' objects (HTTP 400) (Request-ID:
req-cc0e225d-d033-4dfa-aff8-7311389d4f58)
Trace:
==
(keystone.common.wsgi): 2019-03-11 12:30:47,154 ERROR cannot concatenate 'str'
and 'NoneType' objects
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 228, in
__call__
result = method(req, **params)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
235, in wrapper
return f(self, request, filters, **kwargs)
File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py",
line 233, in list_users
return UserV3.wrap_collection(request.context_dict, refs, hints=hints)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
499, in wrap_collection
cls.wrap_member(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
468, in wrap_member
cls._add_self_referential_link(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
464, in _add_self_referential_link
ref['links']['self'] = cls.base_url(context) + '/' + ref['id']
TypeError: cannot concatenate 'str' and 'NoneType' objects
Offending Data:
===
@ line 233 i put LOG.debug( pprint.pformat( refs ) )
grep -b 2 "'id': None," /varlog/keystone/keystone.log
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
Platform:
=
cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
verions:
dpkg --list | grep keystone
ii keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Daemons
ii python-keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Python library
ii python-keystoneauth1 2.18.0-0ubuntu2~cloud0
all authentication library for OpenStack Identity - Python 2.7
ii python-keystoneclient1:3.10.0-0ubuntu1~cloud0
all client library for the OpenStack Keystone API - Python 2.x
ii python-keystonemiddleware4.14.0-0ubuntu1.2~cloud0
all Middleware for OpenStack Identity (Keystone) - Python 2.x
** Affects: keystone (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Proposed action:
=
Key / value failed check error.
Should check key exists and warn user of bad users / continue
Bug presented by:
=
- openstack user list --domain neo.id
+ openstack user list --domain customerdata
cannot concatenate 'str' and 'NoneType' objects (HTTP 400) (Request-ID:
req-cc0e225d-d033-4dfa-aff8-7311389d4f58)
Trace:
==
(keystone.common.wsgi): 2019-03-11 12:30:47,154 ERROR cannot concatenate
'str' and 'NoneType' objects
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 228,
in __call__
result = method(req, **params)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
235, in wrapper
return f(self, request, filters, **kwargs)
File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py",
line 233, in list_users
return UserV3.wrap_collection(request.context_dict, refs, hints=hints)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
499, in wrap_collection
cls.wrap_member(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
468, in wrap_member
cls._add_self_referential_link(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
464, in _add_self_referential_link
ref['links']['self'] = cls.base_url(context) + '/' + ref['id']
TypeError: cannot concatenate 'str' and 'NoneType' objects
Offending Data:
===
@ line 233 i put LOG.debug( pprint.pformat( refs ) )
grep -b 2 "'id': None," /varlog/keystone/keystone.log
{'domain_id':
[Yahoo-eng-team] [Bug 1811405] Re: OVSFWTagNotFound raised many times in neutron-openvswitch-agent logs
Reviewed: https://review.openstack.org/630910
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=22f55822aab17c758f5f723c304b1acaf3179ec1
Submitter: Zuul
Branch:master
commit 22f55822aab17c758f5f723c304b1acaf3179ec1
Author: Lajos Katona
Date: Tue Jan 15 09:20:54 2019 +0100
Catch OVSFWTagNotFound in update_port_filter
In neutron.agent.linux.openvswitch_firewall.firewall make the method
update_port_filter catch OVSFWTagNotFound and log it to avoid
traceback in log files.
Change-Id: I584d867f0e1c47447cb8790fd715fa01ec902438
Closes-Bug: #1811405
** 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/1811405
Title:
OVSFWTagNotFound raised many times in neutron-openvswitch-agent logs
Status in neutron:
Fix Released
Bug description:
I found out that recently exception like:
Jan 11 08:56:11.074296 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [None
req-207e9202-dfc1-4b0d-b9d4-85eaec6174ee None None] Error while processing VIF
ports: neutron.agent.linux.openvswitch_firewall.exceptions.OVSFWTagNotFound:
Cannot get tag for port tap20acc597-23 from its other_config: {}
Jan 11 08:56:11.074665 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most
recent call last):
Jan 11 08:56:11.074999 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/opt/stack/new/neutron/neutron/agent/linux/openvswitch_firewall/firewall.py",
line 526, in get_or_create_ofport
Jan 11 08:56:11.075349 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent of_port =
self.sg_port_map.ports[port_id]
Jan 11 08:56:11.075713 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent KeyError:
'20acc597-23f0-4c18-980e-061aa6494ccf'
Jan 11 08:56:11.076036 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
Jan 11 08:56:11.077854 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent During handling
of the above exception, another exception occurred:
Jan 11 08:56:11.078269 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
Jan 11 08:56:11.078611 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most
recent call last):
Jan 11 08:56:11.079337 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/opt/stack/new/neutron/neutron/agent/linux/openvswitch_firewall/firewall.py",
line 79, in get_tag_from_other_config
Jan 11 08:56:11.079670 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent return
int(other_config['tag'])
Jan 11 08:56:11.08 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent KeyError: 'tag'
Jan 11 08:56:11.080351 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
Jan 11 08:56:11.080677 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent During handling
of the above exception, another exception occurred:
Jan 11 08:56:11.081027 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent
Jan 11 08:56:11.081354 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent Traceback (most
recent call last):
Jan 11 08:56:11.081681 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent File
"/opt/stack/new/neutron/neutron/plugins/ml2/drivers/openvswitch/agent/ovs_neutron_agent.py",
line 2196, in rpc_loop
Jan 11 08:56:11.082077 ubuntu-xenial-rax-dfw-0001639322
neutron-openvswitch-agent[13907]: ERROR
neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent port_info,
[Yahoo-eng-team] [Bug 1818919] Re: CooperativeReader not py3-ready
** Also affects: glance/queens Importance: Undecided Status: New ** Also affects: glance/stein Importance: High Status: Triaged ** Also affects: glance/rocky Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1818919 Title: CooperativeReader not py3-ready Status in Glance: Triaged Status in Glance queens series: New Status in Glance rocky series: New Status in Glance stein series: Triaged Bug description: Tim Burke noticed this in IRC today: https://github.com/openstack/glance/blob/17.0.0/glance/common/utils.py#L231 Should be returning b'' since we're supposed to be returning bytes. Apparently our unit tests could use some beefing up, because they're not breaking under py3. To manage notifications about this bug go to: https://bugs.launchpad.net/glance/+bug/1818919/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1648629] Re: ScaleIO Volumes Created before Newton, do not connect or disconnect after Newton upgrade
Reviewed: https://review.openstack.org/640875 Committed: https://git.openstack.org/cgit/openstack/os-brick/commit/?id=6b60614afaf88819ce92a2d0ed269035a3c8b261 Submitter: Zuul Branch:master commit 6b60614afaf88819ce92a2d0ed269035a3c8b261 Author: Erik Olof Gunnar Andersson Date: Mon Mar 4 13:21:18 2019 -0800 Fix VxFlexOs KeyError after upgrade A long time ago the driver was changed to store volume_id in the nova database and use that. Previously it would use the volume_name and make a call to get the volume_id. Both should be supported, but as the code path currently throws a KeyError it will never reach the backwardscompatible code. This makes sure that the driver works even after an upgrade from Mitaka. Change-Id: Ic389e1a8f0f43ef410eee89202fef19d554fce90 Closes-Bug: #1648629 ** Changed in: os-brick Status: New => 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/1648629 Title: ScaleIO Volumes Created before Newton, do not connect or disconnect after Newton upgrade Status in OpenStack Compute (nova): Invalid Status in os-brick: Fix Released Bug description: Description === ScaleIO volumes that were created pre stable/newton ( stable/mitaka ) in my case, do not connect or disconnect to/from the hypervisor when nova-compute attempts the connection after the upgrade to stable/newton. This appears to be because the os_brick 1.2 to 1.6 change includes a new attribute 'scaleIO_volume_id' This field is not created if the volumes were created at stable/mitaka or before. In this case, this field is not found in nova.block_device_mappings 'connection_info' column. This field is created for volumes created after stable/newton upgrade. Steps to reproduce == 1. Install ScaleIO 2. Install openstack via openstack-ansible stable/mitaka 3. Create and connect ScaleIO volumes to instances 4. Upgrade to stable/newton 5. Shutdown a instance 6. Attempt start of a instance Expected result === The instance should start Actual result = The instance would not start. http://pastebin.com/Pvd6HrcL --after manually adding the 'scaleIO_volume_id' parameter to nova.block_device_mapping.connection_info the connect / disconnect works as expected. Environment === 1. Exact version of OpenStack you are running. See the following stable/newton deployed via openstack-ansible 14.0.3 2. Which hypervisor did you use? libvirt+kvm 2. Which storage type did you use? scaleIO 2.0.1 3. Which networking type did you use? neutron with linux bridge Logs & Configs == http://pastebin.com/Pvd6HrcL os_brick version with OSA stable/mitaka = 1.2 os_brick version with OSA stable/newton = 1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1648629/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819446] [NEW] After the vm's port name is modified, the port status changes from down to active.
Public bug reported: Hello, I've faced a problem with ml2 plugin in Neutron (Queens). steps as as follows: 1. stop VM A, The port status of VM A changes from active to down. 2. update the port name. 3. the port status will change from down to active. Is this phenomenon correct? ** 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/1819446 Title: After the vm's port name is modified, the port status changes from down to active. Status in neutron: New Bug description: Hello, I've faced a problem with ml2 plugin in Neutron (Queens). steps as as follows: 1. stop VM A, The port status of VM A changes from active to down. 2. update the port name. 3. the port status will change from down to active. Is this phenomenon correct? To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1819446/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819430] [NEW] unnecessary placement call to fill group mapping during boot
Public bug reported: To fill the request group - resource provider mapping nova needs to look at the allocation that is made in placement as well as the traits of the used providers. These are explicit placement calls today. However it turns out that the Selection object already contains the allocation data so one of the extra placement call can be removed. This change can lead to a bit better performance. ** Affects: nova Importance: Low Assignee: Balazs Gibizer (balazs-gibizer) Status: In Progress ** Tags: conductor performance ** Changed in: nova Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer) ** Changed in: nova Importance: Undecided => Low ** Changed in: nova Status: New => In Progress -- 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/1819430 Title: unnecessary placement call to fill group mapping during boot Status in OpenStack Compute (nova): In Progress Bug description: To fill the request group - resource provider mapping nova needs to look at the allocation that is made in placement as well as the traits of the used providers. These are explicit placement calls today. However it turns out that the Selection object already contains the allocation data so one of the extra placement call can be removed. This change can lead to a bit better performance. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1819430/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819425] [NEW] Non-admin user can not filter instance by instance-uuid
Public bug reported: Non-admin user can not filter instance by instance-uuid ** 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/1819425 Title: Non-admin user can not filter instance by instance-uuid Status in OpenStack Compute (nova): New Bug description: Non-admin user can not filter instance by instance-uuid To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1819425/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819424] [NEW] Create an instance named "my instance" (with multiple spaces in the middle). After the creation is successful, the instance name in the table is "my instance" (the
Public bug reported: Create an instance named "my instance" (with multiple spaces in the middle). After the creation is successful, the instance name in the table is "my instance" (there is only one space in the middle) ** Affects: horizon Importance: Undecided Assignee: pengyuesheng (pengyuesheng) Status: In Progress ** Changed in: horizon Assignee: (unassigned) => pengyuesheng (pengyuesheng) -- 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/1819424 Title: Create an instance named "my instance" (with multiple spaces in the middle). After the creation is successful, the instance name in the table is "my instance" (there is only one space in the middle) Status in OpenStack Dashboard (Horizon): In Progress Bug description: Create an instance named "my instance" (with multiple spaces in the middle). After the creation is successful, the instance name in the table is "my instance" (there is only one space in the middle) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1819424/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1819423] [NEW] Horizon does not support CSRF_COOKIE_HTTPONLY option
Public bug reported: Steps to reproduce: Deploy Openstack, Devstack Pike is enough add following option into /etc/openstack-dashboard/local_settings.py : CSRF_COOKIE_HTTPONLY = True Restart Apache Expected result: Horizon works Actual result: Several issues appear in Horizon. Request to /api/policy returns 403, and "Policy check failed" warning displayed. At least "Launch instance" and "Create image" dashboards are affected ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "Screen Shot 2018-11-09 at 12.52.45 PM.png" https://bugs.launchpad.net/bugs/1819423/+attachment/5245358/+files/Screen%20Shot%202018-11-09%20at%2012.52.45%20PM.png -- 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/1819423 Title: Horizon does not support CSRF_COOKIE_HTTPONLY option Status in OpenStack Dashboard (Horizon): New Bug description: Steps to reproduce: Deploy Openstack, Devstack Pike is enough add following option into /etc/openstack-dashboard/local_settings.py : CSRF_COOKIE_HTTPONLY = True Restart Apache Expected result: Horizon works Actual result: Several issues appear in Horizon. Request to /api/policy returns 403, and "Policy check failed" warning displayed. At least "Launch instance" and "Create image" dashboards are affected To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1819423/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
