[Yahoo-eng-team] [Bug 1696648] [NEW] Neutron allows user to create a security group with invalid tenant id.
Public bug reported: When user tries to create a security group by using the command "neutron security-group-create test --tenant-id NEC", it is creating a security group successfully without verifying the provided tenant id. User should not be allowed to use invalid tenant-id to create security group ** 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/1696648 Title: Neutron allows user to create a security group with invalid tenant id. Status in neutron: New Bug description: When user tries to create a security group by using the command "neutron security-group-create test --tenant-id NEC", it is creating a security group successfully without verifying the provided tenant id. User should not be allowed to use invalid tenant-id to create security group To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1696648/+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 1693670] Re: Fix doc generation for Python3
** Also affects: barbican Importance: Undecided Status: New ** Changed in: barbican Status: New => In Progress ** Changed in: barbican Assignee: (unassigned) => Vu Cong Tuan (tuan.vu) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1693670 Title: Fix doc generation for Python3 Status in Barbican: In Progress Status in neutron: Fix Released Status in tacker: Fix Released Status in zaqar: Fix Released Bug description: Fix the Sphinx html_last_updated_fmt for Python3. The html_last_updated_fmt option is interpeted as a byte string in python3, causing Sphinx build to break. This patch makes it utf-8 string. To manage notifications about this bug go to: https://bugs.launchpad.net/barbican/+bug/1693670/+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 1696605] [NEW] TypeError: unorderable types: int() < NoneType() possible during quota limit check
Public bug reported: Saw this on a recent py35 unit test run [1]: Traceback (most recent call last): File "/home/jenkins/workspace/gate-nova-python35/nova/tests/unit/network/test_manager.py", line 1234, in test_allocate_floating_ip self.network.allocate_floating_ip(ctxt, ctxt.project_id) File "/home/jenkins/workspace/gate-nova-python35/nova/network/floating_ips.py", line 223, in allocate_floating_ip project_id) File "/home/jenkins/workspace/gate-nova-python35/.tox/py35/lib/python3.5/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper result = fn(cls, context, *args, **kwargs) File "/home/jenkins/workspace/gate-nova-python35/nova/objects/quotas.py", line 201, in check_deltas cls.limit_check_project_and_user(context, **check_kwargs) File "/home/jenkins/workspace/gate-nova-python35/.tox/py35/lib/python3.5/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper result = fn(cls, context, *args, **kwargs) File "/home/jenkins/workspace/gate-nova-python35/nova/objects/quotas.py", line 136, in limit_check_project_and_user project_id=project_id, user_id=user_id) File "/home/jenkins/workspace/gate-nova-python35/nova/quota.py", line 1639, in limit_check_project_and_user user_values=user_values, project_id=project_id, user_id=user_id) File "/home/jenkins/workspace/gate-nova-python35/nova/quota.py", line 628, in limit_check_project_and_user overs = [key for key, val in merged_values.items() File "/home/jenkins/workspace/gate-nova-python35/nova/quota.py", line 629, in if merged_quotas[key] >= 0 and merged_quotas[key] < val] TypeError: unorderable types: int() < NoneType() The problem is some logic that tries to .get(key) a value from one of two dicts that contains the key [2] and if the found value is 0, it won't take precedence over a default not found value of None. In the case where None is picked, we end up with a merged value of None, which blows up (thankfully) in Python 3. [1] http://logs.openstack.org/42/446242/18/check/gate-nova-python35/fdf57fc/testr_results.html.gz [2] https://github.com/openstack/nova/blob/c7afbb9/nova/quota.py#L613-L614 ** Affects: nova Importance: Undecided Assignee: melanie witt (melwitt) Status: In Progress ** Tags: quotas -- 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/1696605 Title: TypeError: unorderable types: int() < NoneType() possible during quota limit check Status in OpenStack Compute (nova): In Progress Bug description: Saw this on a recent py35 unit test run [1]: Traceback (most recent call last): File "/home/jenkins/workspace/gate-nova-python35/nova/tests/unit/network/test_manager.py", line 1234, in test_allocate_floating_ip self.network.allocate_floating_ip(ctxt, ctxt.project_id) File "/home/jenkins/workspace/gate-nova-python35/nova/network/floating_ips.py", line 223, in allocate_floating_ip project_id) File "/home/jenkins/workspace/gate-nova-python35/.tox/py35/lib/python3.5/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper result = fn(cls, context, *args, **kwargs) File "/home/jenkins/workspace/gate-nova-python35/nova/objects/quotas.py", line 201, in check_deltas cls.limit_check_project_and_user(context, **check_kwargs) File "/home/jenkins/workspace/gate-nova-python35/.tox/py35/lib/python3.5/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper result = fn(cls, context, *args, **kwargs) File "/home/jenkins/workspace/gate-nova-python35/nova/objects/quotas.py", line 136, in limit_check_project_and_user project_id=project_id, user_id=user_id) File "/home/jenkins/workspace/gate-nova-python35/nova/quota.py", line 1639, in limit_check_project_and_user user_values=user_values, project_id=project_id, user_id=user_id) File "/home/jenkins/workspace/gate-nova-python35/nova/quota.py", line 628, in limit_check_project_and_user overs = [key for key, val in merged_values.items() File "/home/jenkins/workspace/gate-nova-python35/nova/quota.py", line 629, in if merged_quotas[key] >= 0 and merged_quotas[key] < val] TypeError: unorderable types: int() < NoneType() The problem is some logic that tries to .get(key) a value from one of two dicts that contains the key [2] and if the found value is 0, it won't take precedence over a default not found value of None. In the case where None is picked, we end up with a merged value of None, which blows up (thankfully) in Python 3. [1] http://logs.openstack.org/42/446242/18/check/gate-nova-python35/fdf57fc/testr_results.html.gz [2] https://github.com/openstack/nova/blob/c7afbb9/nova/quota.py#L613-L614 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696605/+subscriptions -- Mailing list: https://launchpad.net/~
[Yahoo-eng-team] [Bug 1696437] Re: OpenStack logo doesn't look good on error page
Reviewed: https://review.openstack.org/471797 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=2b3c7bdbcb1202019e89d701d870013c56eb3b05 Submitter: Jenkins Branch:master commit 2b3c7bdbcb1202019e89d701d870013c56eb3b05 Author: Ivan Kolodyazhny Date: Wed Jun 7 17:28:53 2017 +0300 Fix styles for error page template 500.html template has incorrect styles for OpenStack logo. This patch fixes margins and background image size to fit into the container. Change-Id: Icc2af2731eb8a842c12c073474f3865709b6de2b Closes-Bug: #1696437 ** 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/1696437 Title: OpenStack logo doesn't look good on error page Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 500.html template has incorrect styles for OpenStack logo To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1696437/+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 1669857] Re: libvirt.VIR_DOMAIN_AFFECT_CONFIG provided when detaching volumes during LM rollback
Reviewed: https://review.openstack.org/441204 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=563c0927d14d052e3f1fad80df95fe4a7c48d38b Submitter: Jenkins Branch:master commit 563c0927d14d052e3f1fad80df95fe4a7c48d38b Author: Matt Riedemann Date: Tue Jun 6 14:08:37 2017 -0400 libvirt: Check if domain is persistent before detaching devices Previously the libvirt driver would always assume that it was only detaching devices (volumes or virtual interfaces) from a persistent domain however that is not always the case. For example when rolling back from a live migration an attempt is made to detach volumes from the transient destination domain that is being cleaned up. This attempt would fail with the previous assumption of the domain being persistent in place. This change introduces a simple call to has_persistent_configuration within detach_device_with_retry to confirm the state of the domain before attempting to detach. Closes-Bug: #1669857 Closes-Bug: #1696125 Change-Id: I95948721a0119f5f54dbe50d4455fd47d422164b ** 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/1669857 Title: libvirt.VIR_DOMAIN_AFFECT_CONFIG provided when detaching volumes during LM rollback Status in OpenStack Compute (nova): Fix Released Bug description: Description === During a live-migration rollback the libvirt driver will attempt to detach volumes from the transient destination domain while providing the libvirt.VIR_DOMAIN_AFFECT_CONFIG flag. This will always fail as the domain is not persistent. Steps to reproduce == - live-migrate an instance with volumes attached. - force a rollback of the live-migration resulting in volumes being detached from the destination domain. Expected result === libvirt.VIR_DOMAIN_AFFECT_CONFIG flag not provided while attempting to detach a volume from the transient destination domain. Actual result = libvirt.VIR_DOMAIN_AFFECT_CONFIG flag provided while attempting to detach a volume from the transient destination domain, resulting in a failure during the live-migration rollback. Environment === 1. Exact version of OpenStack you are running. See the following list for all releases: http://docs.openstack.org/releases/ master 2. Which hypervisor did you use? (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...) What's the version of that? libvirt 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 == Rollback of failed live migration with attached volume fails on destination https://bugzilla.redhat.com/show_bug.cgi?id=1424481 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1669857/+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 1696125] Re: Detach interface failed - Unable to detach from guest transient domain (pike)
Reviewed: https://review.openstack.org/441204 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=563c0927d14d052e3f1fad80df95fe4a7c48d38b Submitter: Jenkins Branch:master commit 563c0927d14d052e3f1fad80df95fe4a7c48d38b Author: Matt Riedemann Date: Tue Jun 6 14:08:37 2017 -0400 libvirt: Check if domain is persistent before detaching devices Previously the libvirt driver would always assume that it was only detaching devices (volumes or virtual interfaces) from a persistent domain however that is not always the case. For example when rolling back from a live migration an attempt is made to detach volumes from the transient destination domain that is being cleaned up. This attempt would fail with the previous assumption of the domain being persistent in place. This change introduces a simple call to has_persistent_configuration within detach_device_with_retry to confirm the state of the domain before attempting to detach. Closes-Bug: #1669857 Closes-Bug: #1696125 Change-Id: I95948721a0119f5f54dbe50d4455fd47d422164b ** 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/1696125 Title: Detach interface failed - Unable to detach from guest transient domain (pike) Status in OpenStack Compute (nova): Fix Released Bug description: Seeing this in Tempest runs on master (pike): http://logs.openstack.org/24/471024/2/check/gate-tempest-dsvm-neutron- linuxbridge-ubuntu- xenial/6b98d38/logs/screen-n-cpu.txt.gz?level=TRACE#_Jun_06_02_16_02_855503 Jun 06 02:16:02.855503 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: WARNING nova.compute.manager [None req-b4a50024-a2fd-4279-b284-340d2074f1c1 tempest-TestNetworkBasicOps-1479445685 tempest-TestNetworkBasicOps-1479445685] [instance: 2668bcb9-b13d-4b5b-8ee5-edbdee3b15a8] Detach interface failed, port_id=3843caa3-ab04-45f1-94d8-f330390e40fe, reason: Device detach failed for fa:16:3e:ab:e3:3f: Unable to detach from guest transient domain.: DeviceDetachFailed: Device detach failed for fa:16:3e:ab:e3:3f: Unable to detach from guest transient domain. Jun 06 02:16:02.884007 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server [None req-b4a50024-a2fd-4279-b284-340d2074f1c1 tempest-TestNetworkBasicOps-1479445685 tempest-TestNetworkBasicOps-1479445685] Exception during message handling: InterfaceDetachFailed: Failed to detach network adapter device from 2668bcb9-b13d-4b5b-8ee5-edbdee3b15a8 Jun 06 02:16:02.884180 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server Traceback (most recent call last): Jun 06 02:16:02.884286 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/server.py", line 157, in _process_incoming Jun 06 02:16:02.884395 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) Jun 06 02:16:02.884538 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 213, in dispatch Jun 06 02:16:02.884669 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) Jun 06 02:16:02.884777 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 183, in _do_dispatch Jun 06 02:16:02.884869 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) Jun 06 02:16:02.884968 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/opt/stack/new/nova/nova/exception_wrapper.py", line 77, in wrapped Jun 06 02:16:02.885069 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server function_name, call_dict, binary) Jun 06 02:16:02.885171 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ Jun 06 02:16:02.885272 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server self.force_reraise() Jun 06 02:16:02.885367 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server File "/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise Jun 06 02:16:02.885461 ubuntu-xenial-ovh-bhs1-9149075 nova-compute[24118]: ERROR oslo_messaging.rpc.server six.reraise(self.
[Yahoo-eng-team] [Bug 1696574] [NEW] support HEAD requests for all GET /v3/* actions
Public bug reported: There was an effort in the past to ensure all GET APIs within keystone support corresponding HEAD methods [0]. This bug report is to cleanup the remaining APIs that have been introduced since then or overlooked. The fix for this should be either updating each GET API to support HEAD using get_head_action or updating each get_action usage with a comment explaining why get_head_action isn't needed. [0] https://bugs.launchpad.net/keystone/+bug/1370335 ** Affects: keystone Importance: Wishlist Status: Triaged ** Tags: low-hanging-fruit ** Changed in: keystone Status: New => Triaged ** Changed in: keystone Importance: Undecided => Low ** Changed in: keystone Importance: Low => Wishlist ** Tags added: low-hanging-fruit -- 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/1696574 Title: support HEAD requests for all GET /v3/* actions Status in OpenStack Identity (keystone): Triaged Bug description: There was an effort in the past to ensure all GET APIs within keystone support corresponding HEAD methods [0]. This bug report is to cleanup the remaining APIs that have been introduced since then or overlooked. The fix for this should be either updating each GET API to support HEAD using get_head_action or updating each get_action usage with a comment explaining why get_head_action isn't needed. [0] https://bugs.launchpad.net/keystone/+bug/1370335 To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1696574/+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 1678694] Re: Can't attach volume to volume-backed instance
It looks like it's not an issue in nova nor cinder. If you take the XML that nova is using (if you turn debug log, you'll see it in nova-compute.log): 025aa02e-9348-4740-94dc-c862ac0e And try to attach it to the domain manually: # virsh attach-device instance-080a test-dev.xml --live error: Failed to attach device from test-dev.xml error: internal error: unable to execute QEMU command 'object-add': attempt to add duplicate property 'scsi0-0-0-0-secret0' to object (type 'container') You will see the same error. It's most likely a bug in libvirt, which in CentOS 7 is at version 2.0.0. Reported libvirt bug: https://bugzilla.redhat.com/show_bug.cgi?id=1459690 ** Bug watch added: Red Hat Bugzilla #1459690 https://bugzilla.redhat.com/show_bug.cgi?id=1459690 ** Changed in: nova Status: New => Invalid ** Changed in: nova Status: Invalid => Confirmed -- 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/1678694 Title: Can't attach volume to volume-backed instance Status in OpenStack Compute (nova): Confirmed Bug description: When trying to attach a cinder volume to an instance that was launched with a cinder root drive, the attachment silently fails both on the CLI and in Horizon. From the nova-compute.log on the hypervisor, "libvirtError: internal error: unable to execute QEMU command 'object- add': attempt to add duplicate property 'scsi0-0-0-0-secret0' to object (type 'container')" - so it seems like nova isn't aware of the existing cinder root drive. Steps to reproduce: 1) Launch an instance (either via CLI or in Horizon), specifying a cinder volume as the root 2) Create a volume and try to attach it to the instance Expected outcome: Second volume attaches successfully to the instance Actual outcome: Volume silently fails to attach, remains in "available" state, error log as above in nova-compute.log Environment CentOS 7.2 Mitaka (13.1.2-1.el7) libvirt+kvm ceph storage To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1678694/+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 1696554] [NEW] api-ref: wrong type for marker in GET /os-hypervisors(/detail)
Public bug reported: The api-ref for: https://developer.openstack.org/api-ref/compute/?expanded=list- hypervisors-detail#list-hypervisors and https://developer.openstack.org/api-ref/compute/?expanded=list- hypervisors-details-detail#list-hypervisors-details says the marker is a string, but it's actually an int, it's the compute_nodes.id field. Eventually used here: https://github.com/openstack/nova/blob/3d84232d7b2cf658413370fc9496ab329020738d/nova/db/sqlalchemy/api.py#L669 https://github.com/openstack/nova/blob/3d84232d7b2cf658413370fc9496ab329020738d/nova/db/sqlalchemy/api.py#L631 ** Affects: nova Importance: Medium Status: Confirmed ** Tags: api-ref ** Changed in: nova Status: New => Confirmed ** Changed in: nova Importance: Undecided => Medium -- 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/1696554 Title: api-ref: wrong type for marker in GET /os-hypervisors(/detail) Status in OpenStack Compute (nova): Confirmed Bug description: The api-ref for: https://developer.openstack.org/api-ref/compute/?expanded=list- hypervisors-detail#list-hypervisors and https://developer.openstack.org/api-ref/compute/?expanded=list- hypervisors-details-detail#list-hypervisors-details says the marker is a string, but it's actually an int, it's the compute_nodes.id field. Eventually used here: https://github.com/openstack/nova/blob/3d84232d7b2cf658413370fc9496ab329020738d/nova/db/sqlalchemy/api.py#L669 https://github.com/openstack/nova/blob/3d84232d7b2cf658413370fc9496ab329020738d/nova/db/sqlalchemy/api.py#L631 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696554/+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 1696537] [NEW] test_keepalived_multiple_sighups_does_not_forfeit_mastership fails when neutron-server tries to bind with Linuxbridge driver (agent not enabled)
Public bug reported:
This happens locally and in gate. Gate example:
http://logs.openstack.org/59/471059/2/check/gate-neutron-dsvm-fullstack-
ubuntu-xenial/df11b90/testr_results.html.gz
Traceback (most recent call last):
File "neutron/tests/base.py", line 118, in func
return f(self, *args, **kwargs)
File "neutron/tests/fullstack/test_l3_agent.py", line 252, in
test_keepalived_multiple_sighups_does_not_forfeit_mastership
tenant_id, '13.37.0.0/24', network['id'], router['id'])
File "neutron/tests/fullstack/test_l3_agent.py", line 61, in
_create_and_attach_subnet
router_interface_info['port_id'])
File "neutron/tests/fullstack/test_l3_agent.py", line 51, in
block_until_port_status_active
common_utils.wait_until_true(lambda: is_port_status_active(), sleep=1)
File "neutron/common/utils.py", line 685, in wait_until_true
raise WaitTimeout("Timed out after %d seconds" % timeout)
neutron.common.utils.WaitTimeout: Timed out after 60 seconds
This is not 100% failure rate, depends on which driver server picks to
bind ports: ovs or linuxbridge. If the latter, it just spins attempting
to bind with it over and over, until bails out. It never tries to switch
to ovs.
In server log, we see this: http://logs.openstack.org/59/471059/2/check
/gate-neutron-dsvm-fullstack-ubuntu-xenial/df11b90/logs/dsvm-fullstack-
logs/TestHAL3Agent.test_keepalived_multiple_sighups_does_not_forfeit_mastership
/neutron-server--2017-06-05--
21-41-34-957535.txt.gz#_2017-06-05_21_42_13_400
2017-06-05 21:42:13.400 12566 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-6618e950-5260-404d-a511-e314408542f5 - - - - -] Port
4f8dcf10-6f91-4860-b239-6b04460244a3 on network
155ebfd5-20cf-44bc-9cb5-bc885b8d2eae not bound, no agent of type Linux bridge
agent registered on host host-745fd526 bind_port
/opt/stack/new/neutron/neutron/plugins/ml2/drivers/mech_agent.py:103
2017-06-05 21:42:13.401 12566 ERROR neutron.plugins.ml2.managers
[req-6618e950-5260-404d-a511-e314408542f5 - - - - -] Failed to bind port
4f8dcf10-6f91-4860-b239-6b04460244a3 on host host-745fd526 for vnic_type normal
using segments []
2017-06-05 21:42:13.401 12566 INFO neutron.plugins.ml2.plugin
[req-6618e950-5260-404d-a511-e314408542f5 - - - - -] Attempt 2 to bind port
4f8dcf10-6f91-4860-b239-6b04460244a3
...
2017-06-05 21:42:13.822 12566 ERROR neutron.plugins.ml2.managers
[req-6618e950-5260-404d-a511-e314408542f5 - - - - -] Failed to bind port
4f8dcf10-6f91-4860-b239-6b04460244a3 on host host-745fd526 for vnic_type normal
using segments []
The fullstack test case configures both ml2 drivers.
** Affects: neutron
Importance: High
Status: Confirmed
** Tags: fullstack
** Changed in: neutron
Importance: Undecided => High
** Changed in: neutron
Status: New => Confirmed
** Tags added: fullstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1696537
Title:
test_keepalived_multiple_sighups_does_not_forfeit_mastership fails
when neutron-server tries to bind with Linuxbridge driver (agent not
enabled)
Status in neutron:
Confirmed
Bug description:
This happens locally and in gate. Gate example:
http://logs.openstack.org/59/471059/2/check/gate-neutron-dsvm-
fullstack-ubuntu-xenial/df11b90/testr_results.html.gz
Traceback (most recent call last):
File "neutron/tests/base.py", line 118, in func
return f(self, *args, **kwargs)
File "neutron/tests/fullstack/test_l3_agent.py", line 252, in
test_keepalived_multiple_sighups_does_not_forfeit_mastership
tenant_id, '13.37.0.0/24', network['id'], router['id'])
File "neutron/tests/fullstack/test_l3_agent.py", line 61, in
_create_and_attach_subnet
router_interface_info['port_id'])
File "neutron/tests/fullstack/test_l3_agent.py", line 51, in
block_until_port_status_active
common_utils.wait_until_true(lambda: is_port_status_active(), sleep=1)
File "neutron/common/utils.py", line 685, in wait_until_true
raise WaitTimeout("Timed out after %d seconds" % timeout)
neutron.common.utils.WaitTimeout: Timed out after 60 seconds
This is not 100% failure rate, depends on which driver server picks to
bind ports: ovs or linuxbridge. If the latter, it just spins
attempting to bind with it over and over, until bails out. It never
tries to switch to ovs.
In server log, we see this:
http://logs.openstack.org/59/471059/2/check/gate-neutron-dsvm-
fullstack-ubuntu-xenial/df11b90/logs/dsvm-fullstack-
logs/TestHAL3Agent.test_keepalived_multiple_sighups_does_not_forfeit_mastership
/neutron-server--2017-06-05--
21-41-34-957535.txt.gz#_2017-06-05_21_42_13_400
2017-06-05 21:42:13.400 12566 DEBUG neutron.plugins.ml2.drivers.mech_agent
[req-6618e950-5260-404d-a511-e314408542f5 - - - - -] Port
4f8dcf10-6f91-4860-b23
[Yahoo-eng-team] [Bug 1686116] Re: domain xml not well defined when using virtio-scsi disk bus
Reviewed: https://review.openstack.org/459737 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=724ca8227a23a918d1810f866af661ac2a0730a3 Submitter: Jenkins Branch:master commit 724ca8227a23a918d1810f866af661ac2a0730a3 Author: Sahid Orentino Ferdjaoui Date: Tue Apr 25 05:42:41 2017 -0400 libvirt: update LibvirtConfigGuestDeviceAddress to provide XML This commit is adding a method format_dom() to the config object LibvirtConfigGuestDeviceAddress. That in the aim to provide full description of the controller used by the device. Closes-Bug: #1686116 Change-Id: I9620feffa74b8f7bc932eed03e3a60f46533681d ** 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/1686116 Title: domain xml not well defined when using virtio-scsi disk bus Status in OpenStack Compute (nova): Fix Released Bug description: When using virtio-scsi we should be able to attach up to 256 devices but because the XML device definition do not specify which controller to use and place on that on that one, we are currently able to attach no more than 6 disks. step to reproduce the issue: - glance image-update --property hw_scsi_model=virtio-scsi " to creates the virtio-scsi controller - glance image-update --property hw_disk_bus=scsi " disks will be using scsi Start instance with more than 6 disks/volumes To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1686116/+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 1695719] Re: AttributeError in project snapshot detail page
Reviewed: https://review.openstack.org/470749 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=a27753153b73c3be46c1eb83975aa6990ea3bc1a Submitter: Jenkins Branch:master commit a27753153b73c3be46c1eb83975aa6990ea3bc1a Author: wei.ying Date: Sun Jun 4 21:16:33 2017 +0800 Fix AttributeError in project/admin snapshot detail page If click the name link and go into the details page for the snapshot, the snapshot object lose the property of volume. It will be thrown an exception in the console. AttributeError: 'VolumeSnapshot' object has no attribute '_volume' Change-Id: I365992a9f784af293f40d74e0f80828d9a7e699b Closes-Bug: #1695719 ** 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/1695719 Title: AttributeError in project snapshot detail page Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Env: devstack master branch Steps to reproduce: 1. Go to project/volumes/snapshots panel. 2. Click a snapshot name and redirect to its detail page. 3. View the console. Error while checking action permissions. Traceback (most recent call last): File "/opt/stack/horizon/horizon/tables/base.py", line 1359, in _filter_action return action._allowed(request, datum) and row_matched File "/opt/stack/horizon/horizon/tables/actions.py", line 136, in _allowed self.allowed(request, datum)) File "/opt/stack/horizon/openstack_dashboard/dashboards/project/snapshots/tables.py", line 45, in allowed if (snapshot._volume and File "/opt/stack/horizon/openstack_dashboard/api/base.py", line 121, in __getattribute__ return object.__getattribute__(self, attr) AttributeError: 'VolumeSnapshot' object has no attribute '_volume' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1695719/+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 1695954] Re: QoS policy API does not accept 'tenant_id' filter
or you know what.. he mentions.. in the API layer. I could see how this may be useful for people who just use the curl command. ** Changed in: neutron Status: New => Opinion -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1695954 Title: QoS policy API does not accept 'tenant_id' filter Status in neutron: Opinion Bug description: The list operation of QoS policy API does not accept 'tenant_id' as filter. 'project_id' filtering works. We treat project_id and tenant_id equally in the API layer. It would be a bug. ubuntu@sheep6:~/devstack (master) [OS_CLOUD:devstack][18:32:40]$ openstack token issue ++-+ | Field | Value | ++-+ | expires| 2017-06-05T19:32:46+ | | id | gABZNaPOLTZpwefhxI9PNpNhDtJUuuQSNIyFP063zkoN6RfqM9Cu81k-WXBTWkKWcQzC2-fWQXUVUY5fvL5PunEcSpEn3gimAG1SOdBTL8IKzn8G6SDicc1G5ilZy-ruE99F3ztn4QW8BLd-Vh8F6O0Mkp0GwkIs4tE5e48r8xQh3kI_RFs | | project_id | dda5fe79cdd547e18647a4dd70cb411f | | user_id| 7bcf326322944db99548092976dadd6b | ++-+ ubuntu@sheep6:~/devstack (master) [OS_CLOUD:devstack][18:32:46]$ neutron qos-policy-list --tenant-id dda5fe79cdd547e18647a4dd70cb411f neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Invalid input for operation: 'tenant_id' is not supported for filtering. Neutron server returns request_ids: ['req-0a0d76b2-b557-43a9-8608-48642512f951'] ubuntu@sheep6:~/devstack (master) [OS_CLOUD:devstack][18:32:52]$ neutron qos-policy-list --project-id dda5fe79cdd547e18647a4dd70cb411f neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1695954/+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 1694574] Re: Failed loading flavors in instance launch under MSIE11
Reviewed: https://review.openstack.org/469452
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=a1dd0350502fc089dc42157e4692960ca8ec82e0
Submitter: Jenkins
Branch:master
commit a1dd0350502fc089dc42157e4692960ca8ec82e0
Author: Radomir Dopieralski
Date: Wed May 31 14:18:23 2017 +0200
Fix instance launch dialog under MSIE11
The novaAPI.getFlavors() call takes only a single parameter, which
should be an object with params. But it is being called with two
parameters here, both "true", which makes IE11 fail with TypeError
later on, when it tries to iterate over keys of params.
Change-Id: I0dcfcdca3dda2d94509d7a574184e7f82f21ca22
Closes-Bug: #1694574
** 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/1694574
Title:
Failed loading flavors in instance launch under MSIE11
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
No flavors are shown in the "Launch Instance" dialog in Internet
Explorer 11 (IE11).
Instead, the following alert message is displayed: "Error: Unable to
retrieve the flavors."
The following error appears in the console:
TypeError: Object.keys: argument is not an Object
at forEachSorted
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:705:46)
at ngParamSerializer
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1201:137)
at sendReq
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1236:126)
at serverRequest
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1232:1)
at processQueue
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1469:243)
at Anonymous function
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1470:135)
at Scope.prototype.$eval
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1516:530)
at Scope.prototype.$digest
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1510:184)
at Scope.prototype.$apply
(http://10.124.196.21/dashboard/static/dashboard/js/768aef8292b1.js:1517:266)
at Anonymous funct
With COMPRESS disabled, I was able to get a more readable traceback:
HTML1300: Navigation occurred.
File: instances
JQMIGRATE: Logging is active
TypeError: Object.keys: argument is not an Object
at forEachSorted
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:351:3)
at ngParamSerializer
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:10539:7)
at sendReq
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:11732:11)
at serverRequest
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:11571:9)
at processQueue
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:16383:11)
at Anonymous function
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:16399:27)
at Scope.prototype.$eval
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:17682:9)
at Scope.prototype.$digest
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:17495:15)
at Scope.prototype.$apply
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:17790:13)
at Anonymous function (http://192.168.0.199/dash
JQMIGRATE: jQuery.fn.attr('selected') may use property instead of attribute
console.trace()
at migrateWarn
(http://192.168.0.199/dashboard/static/horizon/lib/jquery_migrate/jquery-migrate.js:43:5)
at jQuery.attr
(http://192.168.0.199/dashboard/static/horizon/lib/jquery_migrate/jquery-migrate.js:155:4)
at access
(http://192.168.0.199/dashboard/static/horizon/lib/jquery/jquery.js:875:6)
at attr
(http://192.168.0.199/dashboard/static/horizon/lib/jquery/jquery.js:4058:3)
at renderEmptyOption
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:28838:9)
at writeNgOptionsValue
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:28883:15)
at ngModelCtrl.$render
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:31205:9)
at ngModelWatch
(http://192.168.0.199/dashboard/static/horizon/lib/angular/angular.js:27815:9)
Unfortunately, MSIE truncates the callback just when it gets
interesting...
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1694574/+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 1678109] Re: Boot from volume default
Reviewed: https://review.openstack.org/425283 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=d734f482ece979018801f38242933dd627e8cd2d Submitter: Jenkins Branch:master commit d734f482ece979018801f38242933dd627e8cd2d Author: Mohammed Naser Date: Wed Jan 25 11:53:09 2017 -0500 Add config for default create volume option This patch adds the ability to configure the default "create volume" value when launching an instance with Cinder enabled. Co-Authored-By: Rob Cresswell Closes-Bug: 1678109 Change-Id: I272f7f1b20cc1276976c464a82d1776de92d17e7 ** 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/1678109 Title: Boot from volume default Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In the instance launcher, when selecting Image or Image snapshot as boot source, the Create volume option is set to yes by default. 1) Has this default value choice been discussed somewhere? 2) Is there a way to change that default value? It'd be nice :-) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1678109/+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 1696001] Re: nova-manage cell_v2 map_cell0 can create invalid connection URL
Reviewed: https://review.openstack.org/471487 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9a33092fa9b0c65b37b9fdc860f5a571908d7a69 Submitter: Jenkins Branch:master commit 9a33092fa9b0c65b37b9fdc860f5a571908d7a69 Author: Sylvain Bauza Date: Tue Jun 6 23:28:59 2017 +0200 Fix cell0 naming when QS params on the connection We had a problem when the nova connection string included parameters on the query string like charset encoding. Note that the connection string necessarly needs to be RFC1738 compliant as per Sqlalchemy rules, so it's totally safe to just unquote what the SQLA helper method gives us as a result. Also removed a tested connection string since it wasn't RFC1738 compatible. Change-Id: I45fe9b92e8d93a0099d33bb0070e9d4e540595ac Closes-Bug: #1696001 ** 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/1696001 Title: nova-manage cell_v2 map_cell0 can create invalid connection URL Status in OpenStack Compute (nova): Fix Released Status in OpenStack Compute (nova) newton series: In Progress Status in OpenStack Compute (nova) ocata series: In Progress Bug description: Description === nova-manage cell_v2 map_cell0 will automatically generate a database connection url from the existing connection configuration setting. However, if the connection has query parameters like a charset defined, it will generate an invalid URL. Steps to reproduce == Set the following in the nova.conf: [database] connection = mysql+pymysql://nova:passw...@db.example.com/nova?charset=utf8 Run: nova-manage cell_v2 map_cell0 Excepted result === Cell0 is mapped to mysql+pymysql://nova:passw...@db.example.com/nova_cell0?charset=utf8 Actual Result = Cell0 is mapped to mysql+pymysql://nova:passw...@db.example.com/nova?charset=utf8nova_cell0 Subsequent API calls may fail because of this with exceptions like: 2017-06-05 20:54:20.343 2197 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/dist-packages/pymysql/connections.py", line 660, in __init__ 2017-06-05 20:54:20.343 2197 ERROR nova.api.openstack.extensions self.encoding = charset_by_name(self.charset).encoding 2017-06-05 20:54:20.343 2197 ERROR nova.api.openstack.extensions AttributeError: 'NoneType' object has no attribute 'encoding' because utf8nova_cell0 is not a valid encoding. Environment: OpenStack Ocata, # dpkg -l | grep nova-common ii nova-common 2:15.0.5-1~u16.04+mcp5 all OpenStack Compute - common files To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696001/+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 1696476] [NEW] Identification of e24cloud platform as using Ec2 datasource
Public bug reported: Hi, I'd like to ask you, to add identification for e24cloud platform (e24cloud.com) with Ec2 Datasource. It can be identified via system vendor field: # cat /sys/class/dmi/id/sys_vendor e24cloud # dmidecode --string=system-manufacturer e24cloud I'll be happy to test a patch. ** Affects: cloud-init Importance: Undecided Status: New ** Description changed: Hi, - I'd like to ask you, to add identification for e24cloud platform with - Ec2 Datasource. + I'd like to ask you, to add identification for e24cloud platform + (e24cloud.com) with Ec2 Datasource. It can be identified via system vendor field: # cat /sys/class/dmi/id/sys_vendor e24cloud - # dmidecode --string=system-manufacture + # dmidecode --string=system-manufacturer e24cloud I'll be happy to test a patch. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1696476 Title: Identification of e24cloud platform as using Ec2 datasource Status in cloud-init: New Bug description: Hi, I'd like to ask you, to add identification for e24cloud platform (e24cloud.com) with Ec2 Datasource. It can be identified via system vendor field: # cat /sys/class/dmi/id/sys_vendor e24cloud # dmidecode --string=system-manufacturer e24cloud I'll be happy to test a patch. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1696476/+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 1696437] [NEW] OpenStack logo doesn't look good on error page
Public bug reported: 500.html template has incorrect styles for OpenStack logo ** Affects: horizon Importance: Undecided Assignee: Ivan Kolodyazhny (e0ne) Status: In Progress ** Attachment added: "Selection_078.jpg" https://bugs.launchpad.net/bugs/1696437/+attachment/4891203/+files/Selection_078.jpg ** Changed in: horizon Assignee: (unassigned) => Ivan Kolodyazhny (e0ne) -- 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/1696437 Title: OpenStack logo doesn't look good on error page Status in OpenStack Dashboard (Horizon): In Progress Bug description: 500.html template has incorrect styles for OpenStack logo To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1696437/+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 1696433] [NEW] ConfigDrive through Openstack gave datasource mismatch
Public bug reported: ** # A new feature in cloud-init identified possible datasources for# # this system as:# # ['ConfigDrive', 'None'] # # However, the datasource used was: OpenStack# ## # In the future, cloud-init will only attempt to use datasources that# # are identified or specifically configured. # # For more information see # # https://bugs.launchpad.net/bugs/1669675 # ## # If you are seeing this message, please file a bug against # # cloud-init at # #https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid # # Make sure to include the cloud provider your instance is # # running on.# ## # After you have filed a bug, you can disable this warning by launching # # your instance with the cloud-config below, or putting that content # # into /etc/cloud/cloud.cfg.d/99-warnings.cfg# ## # #cloud-config # # warnings: # # dsid_missing_source: off # ** version: 0.7.9-113-g513e99e0-0 Openstack has a ConfigDrive option (which was set to true) so this should not throw an error ** Affects: cloud-init Importance: Undecided Status: New ** Tags: dsid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1696433 Title: ConfigDrive through Openstack gave datasource mismatch Status in cloud-init: New Bug description: ** # A new feature in cloud-init identified possible datasources for# # this system as:# # ['ConfigDrive', 'None'] # # However, the datasource used was: OpenStack# ## # In the future, cloud-init will only attempt to use datasources that# # are identified or specifically configured. # # For more information see # # https://bugs.launchpad.net/bugs/1669675 # ## # If you are seeing this message, please file a bug against # # cloud-init at # #https://bugs.launchpad.net/cloud-init/+filebug?field.tags=dsid # # Make sure to include the cloud provider your instance is # # running on.# ## # After you have filed a bug, you can disable this warning by launching # # your instance with the cloud-config below, or putting that content # # into /etc/cloud/cloud.cfg.d/99-warnings.cfg# ## # #cloud-config # # warnings: # # dsid_missing_source: off # ** version: 0.7.9-113-g513e99e0-0 Openstack has a ConfigDrive option (which was set to true) so this should not throw an error To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1696433/+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 1696417] [NEW] nova-manage db online_data_migrations can fail when upgrading to newton under certain conditions
Public bug reported: Reproduceable under conditions: * Mitaka upgraded to Newton * online_data_migrations have not yet migrated flavors and/or aggregates from the nova database, to the nova-api database * One or more of the datetime-fields (created_at, updated_at, deleted_at) are set. ** Because a custom flavor has been created ** Because a flavor has been updated ** Because a flavor has been deleted (deleted flavors are probably not relevant, as the new table have no deleted flag, it just removes them altogether) Steps to reproduce: * Run 'nova-manage db online_data_migrations' It throws an error message like: Error attempting to run Workaround: * Set created_at,updated_at and deleted_at to NULL * Run migration I have done quite a bit of troubleshooting, but haven't managed to write a patch so far. As far as I can tell, inserting a flavor or aggregate to the new tables fail due to the datetime fields including a timezone. There exists code for stripping away the timezone in nova/db/sqlalchemy/api.py (convert_objects_related_datetimes) - but the timezone reappears in nova/objects/flavor.py ** 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/1696417 Title: nova-manage db online_data_migrations can fail when upgrading to newton under certain conditions Status in OpenStack Compute (nova): New Bug description: Reproduceable under conditions: * Mitaka upgraded to Newton * online_data_migrations have not yet migrated flavors and/or aggregates from the nova database, to the nova-api database * One or more of the datetime-fields (created_at, updated_at, deleted_at) are set. ** Because a custom flavor has been created ** Because a flavor has been updated ** Because a flavor has been deleted (deleted flavors are probably not relevant, as the new table have no deleted flag, it just removes them altogether) Steps to reproduce: * Run 'nova-manage db online_data_migrations' It throws an error message like: Error attempting to run Workaround: * Set created_at,updated_at and deleted_at to NULL * Run migration I have done quite a bit of troubleshooting, but haven't managed to write a patch so far. As far as I can tell, inserting a flavor or aggregate to the new tables fail due to the datetime fields including a timezone. There exists code for stripping away the timezone in nova/db/sqlalchemy/api.py (convert_objects_related_datetimes) - but the timezone reappears in nova/objects/flavor.py To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1696417/+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 1668542] Re: nova.conf - az configuration options in Configuration Reference
Reviewed: https://review.openstack.org/438887 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=4814cfb9daeb7c66d9b2701faa506f42a593ba94 Submitter: Jenkins Branch:master commit 4814cfb9daeb7c66d9b2701faa506f42a593ba94 Author: John Garbutt Date: Tue Feb 28 09:54:21 2017 + Fix default_availability_zone docs The default_availability_zone description incorrectly mentioned about the VM that is being booted. To save confusion in the future between default_availability_zone and default_schedule_zone, I have moved them into the same file. default_schedule_zone didn't previous define what None meant, that has also been corrected in this change. Change-Id: I370e1309f7b2e01ad76d5345c6fe5d0443942fec Closes-Bug: #1668542 Co-Authored-By: Stephen Finucane ** 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/1668542 Title: nova.conf - az configuration options in Configuration Reference Status in OpenStack Compute (nova): Fix Released Status in openstack-manuals: Triaged Bug description: This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes: - [X] This doc is inaccurate in this way: __see below - [ ] This is a doc addition request. - [ ] I have a fix to the document that I can paste below including example: input and output. If you have a troubleshooting or support issue, use the following resources: - Ask OpenStack: http://ask.openstack.org - The mailing list: http://lists.openstack.org - IRC: 'openstack' channel on Freenode The descriptions of default_availability_zone and default_schedule_zone are confusing, they seem to serve the same purpose and it is not clear how they differ. Looking at the code a bit, the text for default_schedule_zone is even wrong, it does not affect the scheduler (at least not directly), but is being used in the "create server" call in the API in case that the original request did not specify an availability_zone. The default_availability_zone in contrast seems to be used to evaluate what the az for a compute host will be if it is not being set by other means. It would be nice if someone from Nova team could confirm this before we start updating the docs. --- Release: 0.9 on 2017-02-28 05:45 SHA: f8b8c1c2f797d927274c6b005dffb4acb18b3a6e Source: https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/config-reference/source/compute/config-options.rst URL: https://docs.openstack.org/draft/config-reference/compute/config-options.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1668542/+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 1696410] [NEW] (openstack) server list Unexpected API Error
Public bug reported: (openstack) server list Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible. (HTTP 500) (Request-ID: req-81cc918b-3ce8-42de-996f-38609e5d058f) the following is nova-api.log: 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions [req-4ac89295-a118-4259-98c8-415cf5da26ba 7ae91d7b6e334c55bee81317b7aae048 78a9778adb624324a46970407072b6b7 - default default] Unexpected exception in API method 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions Traceback (most recent call last): 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/extensions.py", line 338, in wrapped 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions return f(*args, **kwargs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 181, in wrapper 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/validation/__init__.py", line 181, in wrapper 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions return func(*args, **kwargs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 214, in detail 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions servers = self._get_servers(req, is_detail=True) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/api/openstack/compute/servers.py", line 357, in _get_servers 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions sort_keys=sort_keys, sort_dirs=sort_dirs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2469, in get_all 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions sort_dirs=sort_dirs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/compute/api.py", line 2609, in _get_instances_by_filters 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions expected_attrs=fields, sort_keys=sort_keys, sort_dirs=sort_dirs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 184, in wrapper 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions result = fn(cls, context, *args, **kwargs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/objects/instance.py", line 1220, in get_by_filters 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions use_slave=use_slave, sort_keys=sort_keys, sort_dirs=sort_dirs) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/nova/db/sqlalchemy/api.py", line 235, in wrapper 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions with reader_mode.using(context): 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions return self.gen.next() 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 944, in _transaction_scope 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions allow_async=self._allow_async) as resource: 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions return self.gen.next() 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 558, in _session 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions bind=self.connection, mode=self.mode) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 317, in _create_session 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions self._start() 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py", line 403, in _start 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions engine_args, maker_args) 2017-06-07 20:09:05.739 3066 ERROR nova.api.openstack.extensions File "/usr/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginef
[Yahoo-eng-team] [Bug 1696403] [NEW] Pep8 fails due to six 1.10.0
Public bug reported: 2017-06-07 09:29:49.968889 | Traceback (most recent call last): 2017-06-07 09:29:49.968921 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/bin/pylint", line 11, in 2017-06-07 09:29:49.968933 | sys.exit(run_pylint()) 2017-06-07 09:29:49.968974 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/__init__.py", line 23, in run_pylint 2017-06-07 09:29:49.968986 | Run(sys.argv[1:]) 2017-06-07 09:29:49.969025 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 1332, in __init__ 2017-06-07 09:29:49.969037 | linter.check(args) 2017-06-07 09:29:49.969074 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 747, in check 2017-06-07 09:29:49.969090 | self._do_check(files_or_modules) 2017-06-07 09:29:49.969129 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 869, in _do_check 2017-06-07 09:29:49.969152 | self.check_astroid_module(ast_node, walker, rawcheckers, tokencheckers) 2017-06-07 09:29:49.969193 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 946, in check_astroid_module 2017-06-07 09:29:49.969206 | walker.walk(ast_node) 2017-06-07 09:29:49.969245 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/utils.py", line 874, in walk 2017-06-07 09:29:49.969255 | self.walk(child) 2017-06-07 09:29:49.969294 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/utils.py", line 871, in walk 2017-06-07 09:29:49.969304 | cb(astroid) 2017-06-07 09:29:49.969349 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/checkers/imports.py", line 249, in visit_import 2017-06-07 09:29:49.969368 | importedmodnode = self.get_imported_module(node, name) 2017-06-07 09:29:49.969411 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/checkers/imports.py", line 288, in get_imported_module 2017-06-07 09:29:49.969428 | return importnode.do_import_module(modname) 2017-06-07 09:29:49.969469 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/astroid/mixins.py", line 119, in do_import_module 2017-06-07 09:29:49.969484 | relative_only=level and level >= 1) 2017-06-07 09:29:49.969525 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/astroid/scoped_nodes.py", line 415, in import_module 2017-06-07 09:29:49.969542 | return MANAGER.ast_from_module_name(modname) 2017-06-07 09:29:49.969584 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/astroid/manager.py", line 161, in ast_from_module_name 2017-06-07 09:29:49.969592 | raise e 2017-06-07 09:29:49.969620 | astroid.exceptions.AstroidImportError: Failed to import module six.moves.urllib.parse with error: 2017-06-07 09:29:49.969636 | No module named six.moves.urllib.parse. 2017-06-07 09:29:50.688358 | ERROR: InvocationError: '/bin/sh ./tools/coding-checks.sh --pylint ' 2017-06-07 09:29:50.688923 | ___ summary 2017-06-07 09:29:50.688975 | ERROR: pep8: commands failed ** Affects: neutron Importance: Undecided Status: New ** Description changed: - 2017-06-07 11:29:07.751893 | Traceback (most recent call last): - 2017-06-07 11:29:07.751925 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/bin/pylint", line 11, in - 2017-06-07 11:29:07.751938 | sys.exit(run_pylint()) - 2017-06-07 11:29:07.751979 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/__init__.py", line 23, in run_pylint - 2017-06-07 11:29:07.751992 | Run(sys.argv[1:]) - 2017-06-07 11:29:07.752033 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 1332, in __init__ - 2017-06-07 11:29:07.752046 | linter.check(args) - 2017-06-07 11:29:07.752085 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 747, in check - 2017-06-07 11:29:07.752103 | self._do_check(files_or_modules) - 2017-06-07 11:29:07.752143 | File "/home/jenkins/workspace/gate-neutron-pep8-ubuntu-xenial/.tox/pep8/local/lib/python2.7/site-packages/pylint/lint.py", line 869, in _do_check - 2
[Yahoo-eng-team] [Bug 1696376] [NEW] logging resource ut failures
Public bug reported:
logging resource unit tests including
test_create_firewall_log_diff_log_res_diff_tenant_same_firewall
are failing on gate.
eg. http://logs.openstack.org/87/199387/75/check/gate-networking-
midonet-python27-ubuntu-xenial/48614e7/testr_results.html.gz
ft3.1:
midonet.neutron.tests.unit.test_extension_logging_resource.LoggingResourceTestCase.test_create_firewall_log_diff_log_res_diff_tenant_same_firewall_StringException:
pythonlogging:'': {{{
WARNING [neutron.quota.resource_registry] floatingip is already registered
WARNING [neutron.quota.resource_registry] router is already registered
WARNING [neutron.quota.resource_registry] firewall is already registered
WARNING [neutron.quota.resource_registry] firewall_policy is already registered
WARNING [neutron.quota.resource_registry] firewall_rule is already registered
WARNING [neutron.quota.resource_registry] firewall_log is already registered
ERROR [neutron.api.v2.resource] create failed: No details.
Traceback (most recent call last):
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/resource.py",
line 93, in resource
result = method(request=request, **args)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 435, in create
return self._create(request, body, **kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 94, in wrapped
setattr(e, '_RETRY_EXCEEDED', True)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 90, in wrapped
return f(*args, **kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_db/api.py",
line 150, in wrapper
ectxt.value = e.inner_exc
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_db/api.py",
line 138, in wrapper
return f(*args, **kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 129, in wrapped
LOG.debug("Retry wrapper got retriable exception: %s", e)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 125, in wrapped
return f(*dup_args, **dup_kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 548, in _create
obj = do_create(body)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 530, in do_create
request.context, reservation.reservation_id)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 523, in do_create
return obj_creator(request.context, **kwargs)
File
"/home/jenkins/workspace/gat
[Yahoo-eng-team] [Bug 1696376] [NEW] logging resource ut failures
You have been subscribed to a public bug:
logging resource unit tests including
test_create_firewall_log_diff_log_res_diff_tenant_same_firewall
are failing on gate.
eg. http://logs.openstack.org/87/199387/75/check/gate-networking-
midonet-python27-ubuntu-xenial/48614e7/testr_results.html.gz
ft3.1:
midonet.neutron.tests.unit.test_extension_logging_resource.LoggingResourceTestCase.test_create_firewall_log_diff_log_res_diff_tenant_same_firewall_StringException:
pythonlogging:'': {{{
WARNING [neutron.quota.resource_registry] floatingip is already registered
WARNING [neutron.quota.resource_registry] router is already registered
WARNING [neutron.quota.resource_registry] firewall is already registered
WARNING [neutron.quota.resource_registry] firewall_policy is already registered
WARNING [neutron.quota.resource_registry] firewall_rule is already registered
WARNING [neutron.quota.resource_registry] firewall_log is already registered
ERROR [neutron.api.v2.resource] create failed: No details.
Traceback (most recent call last):
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/resource.py",
line 93, in resource
result = method(request=request, **args)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 435, in create
return self._create(request, body, **kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 94, in wrapped
setattr(e, '_RETRY_EXCEEDED', True)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 90, in wrapped
return f(*args, **kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_db/api.py",
line 150, in wrapper
ectxt.value = e.inner_exc
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_db/api.py",
line 138, in wrapper
return f(*args, **kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 129, in wrapped
LOG.debug("Retry wrapper got retriable exception: %s", e)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/db/api.py",
line 125, in wrapped
return f(*dup_args, **dup_kwargs)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 548, in _create
obj = do_create(body)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 530, in do_create
request.context, reservation.reservation_id)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 220, in __exit__
self.force_reraise()
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/excutils.py",
line 196, in force_reraise
six.reraise(self.type_, self.value, self.tb)
File
"/home/jenkins/workspace/gate-networking-midonet-python27-ubuntu-xenial/.tmp/tmp.NahFG7mu4Z/openstack/neutron/neutron/api/v2/base.py",
line 523, in do_create
return obj_creator(request.context, **kwargs)
File
"/home/
