[Yahoo-eng-team] [Bug 1603307] Re: horizon plugin gives the KeyError
** Also affects: murano Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1603307 Title: horizon plugin gives the KeyError Status in OpenStack Dashboard (Horizon): In Progress Status in Murano: In Progress Bug description: horizon master with murano-dashboard, open the murano-dashboard, give the error: File "/opt/openstack/horizon/.tox/venv/lib/python2.7/site-packages/django/dispatch/dispatcher.py", line 189, in send response = receiver(signal=self, sender=sender, **named) File "/opt/openstack/horizon/horizon/templatetags/angular.py", line 36, in update_angular_template_hash theme = context['THEME'] # current theme being compressed KeyError: 'THEME' To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1603307/+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 1603307] [NEW] horizon plugin gives the KeyError
You have been subscribed to a public bug: horizon master with murano-dashboard, open the murano-dashboard, give the error: File "/opt/openstack/horizon/.tox/venv/lib/python2.7/site-packages/django/dispatch/dispatcher.py", line 189, in send response = receiver(signal=self, sender=sender, **named) File "/opt/openstack/horizon/horizon/templatetags/angular.py", line 36, in update_angular_template_hash theme = context['THEME'] # current theme being compressed KeyError: 'THEME' ** Affects: horizon Importance: Undecided Assignee: Rob Cresswell (robcresswell) Status: In Progress -- horizon plugin gives the KeyError https://bugs.launchpad.net/bugs/1603307 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). -- 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 1593745] Re: Suspended or migrated instances may have a wrong time on restore
Reviewed: https://review.openstack.org/316116 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0376da0627b022bc6aeb3e423250f9e29181f9ab Submitter: Jenkins Branch:master commit 0376da0627b022bc6aeb3e423250f9e29181f9ab Author: Vladik Romanovsky Date: Thu May 12 19:33:33 2016 -0400 libvirt: update guest time after suspend When an instance is resumed from suspension or a migration, the guest's clock might get a large delay between the current and the suspension time. In some cases, NTP might not be able to resynchronize the guest time and will result in a skewed clock. In order to address the issue, this patch will try to set the guest time after it is resumed. This operation will require the guest agent to be configured and running in order to be able to run. However, this operation will not be disruptive. This code is similar to a change that has been commited to oVirt. https://gerrit.ovirt.org/#/c/50426 Closes-Bug: #1593745 Change-Id: I2732af50aab238502ccdc067f62290fd962c8c64 ** 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/1593745 Title: Suspended or migrated instances may have a wrong time on restore Status in OpenStack Compute (nova): Fix Released Bug description: When a VM is resumed from suspension and/or migrated, its clock continues from the time of suspension, i.e. it's delayed. Running the ntpd services on the instances would not help, as ntpd can only correct minor time difference. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1593745/+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 1584347] Re: Flows can't generate when restarted ovs-agent
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1584347
Title:
Flows can't generate when restarted ovs-agent
Status in neutron:
Expired
Bug description:
I deleted ovs bridge named 'br-int' by 'ovs-vsctl del-br br-int'. Then
I restart ovs-agent. Bridge 'br-int' was created by ovs-agent. But
flows can't generate by ovs-agent.
When I execute 'ovs-vsctl show', this is output:
[root@server-233 ~]# ovs-vsctl show
7b1afcdf-e1ca-4917-b97b-a53103b44dc3
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-int
fail_mode: secure
Port "tap1c3f7bf4-46"
Interface "tap1c3f7bf4-46"
type: internal
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
Port "int-ovsbr3"
Interface "int-ovsbr3"
type: patch
options: {peer=nonexistent-peer}
Bridge "ovsbr3"
Port "phy-ovsbr3"
Interface "phy-ovsbr3"
type: patch
options: {peer=nonexistent-peer}
Port "ovsbr3"
Interface "ovsbr3"
type: internal
Bridge br-tun
fail_mode: secure
Port br-tun
Interface br-tun
type: internal
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Port "qg-e84ab4c4-1a"
Interface "qg-e84ab4c4-1a"
type: internal
Port "fg-17319993-76"
Interface "fg-17319993-76"
type: internal
Port "p3p1.102"
Interface "p3p1.102"
ovs_version: "2.4.0"
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1584347/+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 1604645] Re: prompt is not exact when no have default service provider of LOADBALANCERV2
Reviewed: https://review.openstack.org/344591 Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=d1c7ab6ea3d4d2e3653a04963a4155c4bc449f41 Submitter: Jenkins Branch:master commit d1c7ab6ea3d4d2e3653a04963a4155c4bc449f41 Author: ahdj007 Date: Wed Jul 20 15:02:47 2016 +0800 Replace service type "LOADBALANCER" to "LOADBALANCERV2" When it does not have a default service provider of LOADBALANCERV2, the prompting is "Service type LOADBALANCER does not have a default service provider". It should be "Service type LOADBALANCERV2 does not have a default service provider". Change-Id: Ibae4fe7d2f774957518d203dc039dc5f8538c804 Closes-Bug: #1604645 ** 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/1604645 Title: prompt is not exact when no have default service provider of LOADBALANCERV2 Status in neutron: Fix Released Bug description: service_plugins =neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2 [root@controller dongjuan(keystone_admin)]# neutron lbaas-loadbalancer-create --name lb1 37102792-f240-4324-8c00-60eba192fff6 Service type LOADBALANCER does not have a default service provider [root@controller dongjuan(keystone_admin)]# it should be Service type LOADBALANCERV2 does not have a default service provider To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1604645/+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 1605444] [NEW] Should check null key when set key-value pair in property
Public bug reported: root@controller01:~# glance image-update ubuntu-14.04-server-amd64 --property = +---+--+ | Property | Value| +---+--+ | Property '' | None | | Property 'vmware_adaptertype' | lsiLogic | | Property 'vmware_disktype'| streamOptimized | | checksum | 7b26c526f6f7c8ab874ad55b2698dee0 | | container_format | bare | | created_at| 2016-07-21T07:37:42.00 | | deleted | False| | deleted_at| None | | disk_format | vmdk | | id| 2fb0b8a1-1634-499d-95ee-2451ec23893e | | is_public | True | | min_disk | 5| | min_ram | 512 | | name | ubuntu-14.04-server-amd64| | owner | 5b53ee384ebc4212b4086241e1075dea | | protected | False| | size | 971606528| | status| active | | updated_at| 2016-07-22T02:25:46.00 | | virtual_size | None | +---+--+ The null key set success as the result. But null key is meaningless to the user which also belong to the invalid input in other components, like cinder and nova flavor as below: root@controller01:~# nova flavor-key m1.tiny set = ERROR (CommandError): Invalid key: "". Keys may only contain letters, numbers, spaces, underscores, periods, colons and hyphens. So for the consistent openstack UE and error handling, glance cli site better to add the null key check. ** Affects: glance Importance: Undecided Assignee: QiangTang (qtang) Status: New ** Changed in: glance Assignee: (unassigned) => QiangTang (qtang) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to Glance. https://bugs.launchpad.net/bugs/1605444 Title: Should check null key when set key-value pair in property Status in Glance: New Bug description: root@controller01:~# glance image-update ubuntu-14.04-server-amd64 --property = +---+--+ | Property | Value| +---+--+ | Property '' | None | | Property 'vmware_adaptertype' | lsiLogic | | Property 'vmware_disktype'| streamOptimized | | checksum | 7b26c526f6f7c8ab874ad55b2698dee0 | | container_format | bare | | created_at| 2016-07-21T07:37:42.00 | | deleted | False| | deleted_at| None | | disk_format | vmdk | | id| 2fb0b8a1-1634-499d-95ee-2451ec23893e | | is_public | True | | min_disk | 5| | min_ram | 512 | | name | ubuntu-14.04-server-amd64| | owner | 5b53ee384ebc4212b4086241e1075dea | | protected | False| | size | 971606528| | status| active | | updated_at| 2016-07-22T02:25:46.00 | | virtual_size | None | +---+--+ The null key set success as the result. But null key is meaningless to the user which also belong to the invalid input in other components, like cinder and nova flavor as below: root@controller01:~# nova flavor-key m1.tiny set = ERROR (CommandError): Invalid key: "". Keys may only contain letters, numbers, spaces, underscores, perio
[Yahoo-eng-team] [Bug 1605423] Re: linux gate jobs are broken with ovs-vsctl missing error
** Project changed: neutron => devstack -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1605423 Title: linux gate jobs are broken with ovs-vsctl missing error Status in devstack: Confirmed Bug description: http://logs.openstack.org/12/341212/11/check/gate-tempest-dsvm- neutron-linuxbridge/ff71298/logs/devstacklog.txt.gz Started after https://review.openstack.org/#/c/343072/ merged. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1605423/+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 1605423] [NEW] linux gate jobs are broken with ovs-vsctl missing error
Public bug reported: http://logs.openstack.org/12/341212/11/check/gate-tempest-dsvm-neutron- linuxbridge/ff71298/logs/devstacklog.txt.gz Started after https://review.openstack.org/#/c/343072/ merged. ** Affects: neutron Importance: Critical Assignee: Kevin Benton (kevinbenton) Status: Confirmed ** Tags: gate-failure ** Tags added: gate-failure ** Changed in: neutron Status: New => Confirmed ** Changed in: neutron Importance: Undecided => Critical ** Changed in: neutron Assignee: (unassigned) => Kevin Benton (kevinbenton) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1605423 Title: linux gate jobs are broken with ovs-vsctl missing error Status in neutron: Confirmed Bug description: http://logs.openstack.org/12/341212/11/check/gate-tempest-dsvm- neutron-linuxbridge/ff71298/logs/devstacklog.txt.gz Started after https://review.openstack.org/#/c/343072/ merged. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605423/+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 1540983] Re: Gate failures for neutron in test_dualnet_multi_prefix_slaac
http://logs.openstack.org/83/339283/16/check/gate-tempest-dsvm-neutron- dvr/df8047b/logs/ ** Changed in: neutron Status: Expired => Confirmed ** Changed in: neutron Importance: Undecided => Critical -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1540983 Title: Gate failures for neutron in test_dualnet_multi_prefix_slaac Status in neutron: Confirmed Status in OpenStack-Gate: Expired Bug description: 24 hits in 7 days for logstash query : message:"in test_dualnet_multi_prefix_slaac" AND voting:1 2016-02-02 14:35:49.054 | Captured traceback: 2016-02-02 14:35:49.054 | ~~~ 2016-02-02 14:35:49.054 | Traceback (most recent call last): 2016-02-02 14:35:49.054 | File "tempest/test.py", line 113, in wrapper 2016-02-02 14:35:49.055 | return f(self, *func_args, **func_kwargs) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 246, in test_dualnet_multi_prefix_slaac 2016-02-02 14:35:49.055 | dualnet=True) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 155, in _prepare_and_test 2016-02-02 14:35:49.055 | sshv4_1, ips_from_api_1, sid1 = self.prepare_server(networks=net_list) 2016-02-02 14:35:49.055 | File "tempest/scenario/test_network_v6.py", line 128, in prepare_server 2016-02-02 14:35:49.055 | username=username) 2016-02-02 14:35:49.056 | File "tempest/scenario/manager.py", line 390, in get_remote_client 2016-02-02 14:35:49.056 | linux_client.validate_authentication() 2016-02-02 14:35:49.056 | File "tempest/common/utils/linux/remote_client.py", line 63, in validate_authentication 2016-02-02 14:35:49.056 | self.ssh_client.test_connection_auth() 2016-02-02 14:35:49.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 172, in test_connection_auth 2016-02-02 14:35:49.056 | connection = self._get_ssh_connection() 2016-02-02 14:35:49.056 | File "/opt/stack/new/tempest/.tox/full/local/lib/python2.7/site-packages/tempest_lib/common/ssh.py", line 87, in _get_ssh_connection 2016-02-02 14:35:49.057 | password=self.password) 2016-02-02 14:35:49.057 | tempest_lib.exceptions.SSHTimeout: Connection to the 172.24.5.141 via SSH timed out. 2016-02-02 14:35:49.057 | User: cirros, Password: None To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1540983/+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 1512880] Re: Failed cold migration with SR-IOV
Reviewed: https://review.openstack.org/242573
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=dfdae01bd03f522ffab7876b253ec41641934702
Submitter: Jenkins
Branch:master
commit dfdae01bd03f522ffab7876b253ec41641934702
Author: Ludovic Beliveau
Date: Fri Nov 6 12:22:16 2015 -0500
Update binding:profile for SR-IOV ports
The libvirt driver relies on the network information for configuring the
SR-IOV interfaces (binding:vnic_type). The network information is specified
when creating a Neutron port (binding:profile - which contain the PCI
address
of the device).
During a migration, the Neutron port information needs to be updated based
on
the allocated PCI device on the migrated node.
Co-Authored-By: Moshe Levi
Closes-Bug: #1512880
Change-Id: I7423907ef33648669decc561fc3461415b877ba6
** 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/1512880
Title:
Failed cold migration with SR-IOV
Status in OpenStack Compute (nova):
Fix Released
Bug description:
Cold migration of an instance that has an SR-IOV interface fails to
migrate because on migrated compute's nova is trying to use the PCI
device/address that has been allocated from the incoming compute.
Obviously this is failing since the PCI device is not present on the
migrated compute.
See the error "libvirtError: Device :83:10.6 not found: could not
access /sys/bus/pci/devices/:83:10.6/config: No such file or
directory" in the log in the attachment.
Nova should allocate a new PCI device based the hardware configuration
of the compute where the instance is being migrated and this PCI
device should be use to create the instance XML.
Nova version:
commit 2397d636ff6ea3767fe62ee681d609fce4fc98ca
Author: OpenStack Proposal Bot
Date: Tue Oct 27 06:30:34 2015 +
Imported Translations from Zanata
For more information about this automatic import see:
https://wiki.openstack.org/wiki/Translations/Infrastructure
Change-Id: I38f537e37972e5ddae13d388021412d85f6be898
Devstack setup:
* One server configured with controller and compute functions
* Intel 10G port is configured with 8 VFs: $ echo 8 >
/sys/bus/pci/devices/\:85\:00.0/sriov_numvfs
* /etc/nova/nova.conf: pci_passthrough_whitelist =
{"address":"*:85:10.*","physical_network":"default"}
* One server configured with compute function only
* Intel 10G port is configured with 8 VFs: $ echo 8 >
/sys/bus/pci/devices/\:83\:00.0/sriov_numvfs
* /etc/nova/nova.conf: pci_passthrough_whitelist =
{"address":"*:83:10.*","physical_network":"default"}
* Note that it is important for this test that the PCI addresses for the
SR-IOV interfaces are different. We want to validate that new PCI devices are
claimed/allocated on the incoming compute.
Reproduce steps:
1) Boot an instance with an SR-IOV interface:
$ NETID=`neutron net-list | grep default | awk '{print $2}'`
$ neutron port-create $NETID --binding:vnic-type direct --name p-direct
$ PORTID=`neutron port-list | grep "p-direct" | awk '{print $2}'`
$ nova boot test --image=ubuntu --nic port-id=$PORTID --flavor=m1.small
2) Migrate the instance to the other compute:
$ nova migrate test
Expected result:
The instance is successfully migrated on the other server.
Actual result:
The instance failed to migrate. Instance is stuck in error. See log
in attachment for more information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1512880/+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 1605384] [NEW] Opening a "Create" form in a new window shows repeated titles and scrollbars
Public bug reported: How to reproduce: 1. Go to Identity->*, Project->Images, Project-Volumes, etc. 2. Open in a new tab/window any of the "Create" forms, e.g. Open in a new window the "Create User" form. 3. See two titles with the very same content. 4. Observe there are two scrollbars. This is because the form is enclosed in a div with max-height. Affects non-angular modals. ** Affects: horizon Importance: Undecided Status: New ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1605384/+attachment/4704947/+files/createuser.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/1605384 Title: Opening a "Create" form in a new window shows repeated titles and scrollbars Status in OpenStack Dashboard (Horizon): New Bug description: How to reproduce: 1. Go to Identity->*, Project->Images, Project-Volumes, etc. 2. Open in a new tab/window any of the "Create" forms, e.g. Open in a new window the "Create User" form. 3. See two titles with the very same content. 4. Observe there are two scrollbars. This is because the form is enclosed in a div with max-height. Affects non-angular modals. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1605384/+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 1605374] [NEW] Modal closes when pressing ESC and dropdown is expanded
Public bug reported: How to reproduce: 1. Open a modal window that has a dropdown component (not select element) 2. Expand the dropdown 3. Press ESC key 4. See how the whole modal closes Expected result: Pressing the ESC key when a dropdown is expanded should only close the dropdown and not the modal itself. This event shouldn't be propagated to parent elements, try closing any other dropdown that is not inside of a modal and see expected result. Actual result: The modal window catches the event and closes itself. ** Affects: horizon Importance: Undecided Status: New ** Tags: ux -- 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/1605374 Title: Modal closes when pressing ESC and dropdown is expanded Status in OpenStack Dashboard (Horizon): New Bug description: How to reproduce: 1. Open a modal window that has a dropdown component (not select element) 2. Expand the dropdown 3. Press ESC key 4. See how the whole modal closes Expected result: Pressing the ESC key when a dropdown is expanded should only close the dropdown and not the modal itself. This event shouldn't be propagated to parent elements, try closing any other dropdown that is not inside of a modal and see expected result. Actual result: The modal window catches the event and closes itself. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1605374/+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 1480896] Re: Newly added project disappears intermittently from the project list dropdown
** Changed in: horizon Status: Incomplete => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1480896 Title: Newly added project disappears intermittently from the project list dropdown Status in OpenStack Dashboard (Horizon): Invalid Bug description: When I create a new project via the dashboard and add the current user as a user of the project, the new project is immediately shown in the project list in the header bar. However on subsequent requests to the dashboard, the newly added project intermittent disappears (and reappears) from the dropdown. Once logged out and logged it again, the newly added project appears permanently. To reproduce the issue, after adding the project, try accessing the dashboard url (any dashboard/panel) in multiple browser tabs simultaneously. The newly added project will fail to appear in the dropdown in some of the tabs. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1480896/+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 1605336] Re: Neutron loadbalancer VIP port fails to create
** Tags removed: trove ** Also affects: neutron Importance: Undecided Status: New ** Project changed: neutron => f5openstackcommunitylbaas ** Description changed: When trying to create a Loadbalancer (v1) VIP with the command: - neutron lb-vip-create --address 10.97.0.254 --name vip-97 \ - --protocol-port 22 --protocol TCP --subnet-id subnet-97 hapool-97 + ``` + neutron lb-vip-create --address 10.97.0.254 --name vip-97 \ + --protocol-port 22 --protocol TCP --subnet-id subnet-97 hapool-97 + ``` Where subnet-97 is a subnet to tenant-97, which have 'dns_domain' set to an existing domain. The domain works - creating an instance + floating IP on that will register the set dns_name in the domain. However, the lb-vip-create will fail with - Request Failed: internal server error while processing your request. - Neutron server returns request_ids: ['req-ee6a68f1-ed8a-4f22-9dea-646fb97ff795'] + Request Failed: internal server error while processing your request. + Neutron server returns request_ids: ['req-ee6a68f1-ed8a-4f22-9dea-646fb97ff795'] and the log will say: - ==> /var/log/neutron/neutron-server.log <== - 2016-07-21 18:08:54.940 7926 INFO neutron.wsgi [req-cc53af04-89fc-482c-8a4f-0a3f5cc2e614 4b0e25c70d2b4ad6ba4c50250f2f0b0b 04ee0e71babe4fd7aa16c3f64a8fca89 - - -] 10.0.4.1 - - [21/Jul/2016 18:08:54] "GET /v2.0/lb/pools.json?fields=id&name=hapool-97 HTTP/1.1" 200 257 0.070421 - 2016-07-21 18:08:55.027 7926 INFO neutron.wsgi [req-e95bbb13-c38e-4cdf-afc5-9bba3351b8ff 4b0e25c70d2b4ad6ba4c50250f2f0b0b 04ee0e71babe4fd7aa16c3f64a8fca89 - - -] 10.0.4.1 - - [21/Jul/2016 18:08:55] "GET /v2.0/subnets.json?fields=id&name=subnet-97 HTTP/1.1" 200 259 0.081731 - 2016-07-21 18:08:55.037 7926 INFO neutron.quota [req-ee6a68f1-ed8a-4f22-9dea-646fb97ff795 4b0e25c70d2b4ad6ba4c50250f2f0b0b 04ee0e71babe4fd7aa16c3f64a8fca89 - - -] Loaded quota_driver: . - 2016-07-21 18:08:55.494 7926 INFO neutron.plugins.ml2.managers [req-ee6a68f1-ed8a-4f22-9dea-646fb97ff795 4b0e25c70d2b4ad6ba4c50250f2f0b0b 04ee0e71babe4fd7aa16c3f64a8fca89 - - -] Extension driver 'dns' failed in process_create_port - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource [req-ee6a68f1-ed8a-4f22-9dea-646fb97ff795 4b0e25c70d2b4ad6ba4c50250f2f0b0b 04ee0e71babe4fd7aa16c3f64a8fca89 - - -] create failed - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource Traceback (most recent call last): - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py", line 84, in resource - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource result = method(request=request, **args) - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 410, in create - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource return self._create(request, body, **kwargs) - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_db/api.py", line 148, in wrapper - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 221, in __exit__ - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource self.force_reraise() - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 197, in force_reraise - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_db/api.py", line 138, in wrapper - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource return f(*args, **kwargs) - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 521, in _create - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource obj = do_create(body) - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 503, in do_create - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource request.context, reservation.reservation_id) - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 221, in __exit__ - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource self.force_reraise() - 2016-07-21 18:08:55.719 7926 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 197, in force_reraise - 2016-07-21 18:08:55.719 792
[Yahoo-eng-team] [Bug 1604714] Re: search data once when magic-search has inited
Reviewed: https://review.openstack.org/344692
Committed:
https://git.openstack.org/cgit/openstack/horizon/commit/?id=fb4b08ffc7277bfef7b513f6576bbb689c14e8c4
Submitter: Jenkins
Branch:master
commit fb4b08ffc7277bfef7b513f6576bbb689c14e8c4
Author: majik
Date: Wed Jul 20 17:55:16 2016 +0800
fix magic search bug
Two same requests are sent when magic-search is on load.
One is right, but another is called by the search event.
The second one should not happen.
The initial data of currentServerSearchParams in stMagicSearch is wrong,
which should be {magicSearchQuery: ""} instead of {}.
Change-Id: Ia1e28e848daabe5685cb7a01c80ca1296131e616
Closes-Bug: #1604714
** 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/1604714
Title:
search data once when magic-search has inited
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
When the page which containers hz-resource-table(magic-search) is on
load, it sends get the same data twice. One is right, but another is
called by the search event. The second one should not happen.
I find it out that the initial data of currentServerSearchParams in
stMagicSearch is incorrect.
Initial currentServerSearchParams is {}, however, which should be
{magicSearchQuery: ""}.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1604714/+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 1605278] Re: Merge python-django 1:1.9.8-1 (main) from Debian unstable (main)
** Also affects: maas Importance: Undecided Status: New ** Also affects: horizon Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1605278 Title: Merge python-django 1:1.9.8-1 (main) from Debian unstable (main) Status in OpenStack Dashboard (Horizon): New Status in MAAS: New Status in python-django package in Ubuntu: Confirmed Bug description: Please merge python-django 1:1.9.8-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * SECURITY UPDATE: XSS in admin's add/change related popup - debian/patches/CVE-2016-6186.patch: change to text in django/contrib/admin/static/admin/js/admin/RelatedObjectLookups.js, django/views/debug.py, added to tests in tests/admin_views/admin.py, tests/admin_views/models.py, tests/admin_views/tests.py. - CVE-2016-6186 * Backport b1afebf882db5296cd9dcea26ee66d5250922e53 for ticket 26204 from upstream (1.8.10) to allow dashes in TLDs again (in the URL validator.) LP: #1528710 * Backport b1afebf882db5296cd9dcea26ee66d5250922e53 for ticket 26204 from upstream (1.8.10) to allow dashes in TLDs again (in the URL validator.) LP: #1528710 * SECURITY REGRESSION: is_safe_url() with non-unicode url (LP: #1553251) - debian/patches/CVE-2016-2512-regression.patch: updated to final upstream fix. - CVE-2016-2512 * SECURITY REGRESSION: is_safe_url() with non-unicode url (LP: #1553251) - debian/patches/CVE-2016-2512-regression.patch: force url to unicode in django/utils/http.py, added test to tests/utils_tests/test_http.py. - CVE-2016-2512 * SECURITY UPDATE: malicious redirect and possible XSS attack via user-supplied redirect URLs containing basic auth - debian/patches/CVE-2016-2512.patch: prevent spoofing in django/utils/http.py, added test to tests/utils_tests/test_http.py. - CVE-2016-2512 * SECURITY UPDATE: user enumeration through timing difference on password hasher work factor upgrade - debian/patches/CVE-2016-2513.patch: fix timing in django/contrib/auth/hashers.py, added note to docs/topics/auth/passwords.txt, added tests to tests/auth_tests/test_hashers.py. - CVE-2016-2513 * Merge from Debian unstable. Remaining changes: - debian/patches/pymysql-replacement.patch: Use pymysql as drop in replacement for MySQLdb. - debian/control: Drop python-mysqldb in favor of python-pymysql. * Dropped changes: - debian/patches/99_skip_tests_due_python35.diff: no longer required, python 3.5 is now officially supported in 1.8.6+. All of that was applied in the new Debian version except for the pymysql replacement. Changelog entries since current yakkety version 1.8.7-1ubuntu6: python-django (1:1.9.8-1) unstable; urgency=high * New upstream security release: https://www.djangoproject.com/weblog/2016/jul/18/security-releases/ - CVE-2016-6186: XSS in admin's add/change related popup -- Luke Faraone Tue, 19 Jul 2016 14:15:24 + python-django (1:1.9.7-2) unstable; urgency=medium * Re-upload 1.9.7 to unstable with epoch. -- Chris Lamb Sun, 26 Jun 2016 09:58:19 +0200 python-django (1.10~beta1-1) unstable; urgency=medium [ Chris Lamb ] * New upstream beta release. * Drop fix-25761-add-traceback-attribute.patch; applied upstream. [ Raphaël Hertzog ] * Remove obsolete /etc/bash_completion.d/django_bash_completion on upgrade. Closes: #801744 -- Chris Lamb Sat, 25 Jun 2016 19:17:49 +0200 python-django (1.9.7-1) unstable; urgency=medium [ Raphaël Hertzog ] * New upstream bugfix release. * Bump python-sphinx build dependency to >= 1.3. Closes: #824108 * Drop build dependency on locales. C.UTF-8 that we currently use is part of libc-bin. [ Chris Lamb ] * Remove duplicated "of of" in python-django's README.Debian. -- Raphaël Hertzog Tue, 14 Jun 2016 00:05:22 +0200 python-django (1.9.6-1) unstable; urgency=medium * New upstream bugfix release. -- Chris Lamb Sat, 07 May 2016 07:01:17 +0100 python-django (1.9.5-2) unstable; urgency=medium * Drop the dir_to_symlink transition that was only really needed for upgrades between versions 1.9~rc2 and 1.9.4. Closes: #821789 -- Raphaël Hertzog Wed, 20 Apr 2016 17:47:05 +0200 python-django (1.9.5-1) unstable; urgency=medium * New upstream bugfix release: https://docs.djangoproject.com/en/1.9/releases/1.9.5/ * Fix the DEP-8 test suite (django-admin --with python3 failing because ./manage.py does not have a good shebang). * Update Standards-Version to 3.9.8. * Add some lintian overrides. * Tweak Vcs-
[Yahoo-eng-team] [Bug 1494140] Re: Alignment is not well in project table Inline editing
We've decided to remove inline edit functionality from Horizon. It doesn't provide much advantage over regular edit, and breaks often/ is a pain to maintain. ** Changed in: horizon Assignee: qiaomin032 (chen-qiaomin) => (unassigned) ** Changed in: horizon Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1494140 Title: Alignment is not well in project table Inline editing Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Reproduce the bug: Click the inline edit pencil icon in "Enabled" cell of the project table in identity project panel, you will see the checkbox and the label not align well. This issue will affect later table inline edit. Please see the attached picture for more detail. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1494140/+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 1569185] Re: update_cell() in user table should be refactored
We've decided to remove inline edit functionality from Horizon. It doesn't provide much advantage over regular edit, and breaks often/ is a pain to maintain. ** Changed in: horizon Status: In Progress => Won't Fix ** Changed in: horizon Milestone: next => None ** Changed in: horizon Assignee: Wang Bo (chestack) => (unassigned) -- 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/1569185 Title: update_cell() in user table should be refactored Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: update_cell() is called by inline edit user. 1. should only update the changed cell instead of whole user data 2. there is no project column in table so it will never be updated remove 'project' to unnecessary api call. ref: https://github.com/openstack/horizon/blob/master/openstack_dashboard/api/keystone.py#L420 3. avoid set email to empty string. ref: https://bugs.launchpad.net/horizon/+bug/1265805 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1569185/+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 1537615] Re: Inline edit in Metadata Definitions causes table shift
We've decided to remove inline edit functionality from Horizon. It doesn't provide much advantage over regular edit, and breaks often/ is a pain to maintain. ** Changed in: horizon Status: Confirmed => Won't Fix ** Changed in: horizon Milestone: next => None -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1537615 Title: Inline edit in Metadata Definitions causes table shift Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Using the inline edit in the Metadata Definitions panel table causes the table to jump slightly. Probably a padding or margin issue. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1537615/+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 1567405] Re: no warning message for invalid email with inline user edit
We've decided to remove inline edit functionality from Horizon. It doesn't provide much advantage over regular edit, and breaks often/ is a pain to maintain. ** Changed in: horizon Status: Confirmed => Won't Fix ** Changed in: horizon Milestone: next => None ** Changed in: horizon Assignee: Erik Neeley (erikneeley) => (unassigned) -- 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/1567405 Title: no warning message for invalid email with inline user edit Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Environment: - upstream Steps: - Login as admin - Go to "Identity" -> "Users" - Move cursor to user e-mail and click icon "edit" - Type "test@email:" to e-mail field and click icon "save" Expected result: - Warning message that e-mail has invalid format Actual result: - No notifications. Just e-mail is still in edit mode To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1567405/+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 1519589] Re: missing inline enable/disable for Users
We've decided to remove inline edit functionality from Horizon. It doesn't provide much advantage over regular edit, and breaks often/ is a pain to maintain. ** Changed in: horizon Status: In Progress => Won't Fix ** Changed in: horizon Milestone: next => None ** Changed in: horizon Assignee: Liyingjun (liyingjun) => (unassigned) -- 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/1519589 Title: missing inline enable/disable for Users Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: Admin - Identity - Users You can do inline change of User name, Description, Email, but you can't do that with Enabled field. For example. this work's fine in Admin - Identity - Projects. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1519589/+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 1519579] Re: dash as NULL value of description disappears after edit
** 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/1519579
Title:
dash as NULL value of description disappears after edit
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
In tables with 'Description' column you can modify this value by
inline tick or Edit button. In case the default, current value of this
field is empty, it's often displayed as dash ('-'). When you touch
content of this field - save empty string again, as result the new
value is not dash anymore, but empty string as was given.
This inconsistent behavior is case for example (as Admin) Identity -
Users, but *works* in Project - Compute - Volumes, volumes tab.
It makes inconsistency between default-empty-value and user-input-
empty-value.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1519579/+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 1359399] Re: [Bootstrap] Broken table inline edits
We've decided to remove inline edit functionality from Horizon. It doesn't provide much advantage over regular edit, and breaks often/ is a pain to maintain. ** Changed in: horizon Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1359399 Title: [Bootstrap] Broken table inline edits Status in OpenStack Dashboard (Horizon): Won't Fix Bug description: After the bootstrap patch, inline table edit is missing a couple of features: 1. Cell used to turn green with a check mark before fading out when edits was successful 2. Error icon no longer shows up in the text area if an server returns a 400 I am sure more bugs will surface with more testing. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1359399/+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 1605343] [NEW] [rfe] update CIDR for subnet
Public bug reported: Currently, updating subnet CIDR is blocked by validation from API side. By the way, PD code is already updating CIDRs so far. Unlocking CIDR updating requires: 1. Accept CIRD and optionally allocation pools and gateway_ip. 2. If new allocation pool is not provided, and old pool is not fit into CIRD, then fail. Same for GW. 3. Re-allocate IP if they're out of new allocation pool. ** Affects: neutron Importance: Undecided Status: New ** Tags: rfe -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1605343 Title: [rfe] update CIDR for subnet Status in neutron: New Bug description: Currently, updating subnet CIDR is blocked by validation from API side. By the way, PD code is already updating CIDRs so far. Unlocking CIDR updating requires: 1. Accept CIRD and optionally allocation pools and gateway_ip. 2. If new allocation pool is not provided, and old pool is not fit into CIRD, then fail. Same for GW. 3. Re-allocate IP if they're out of new allocation pool. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605343/+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 1605090] Re: AssertionError: 0 == 0 : No IPv4 addresses found on gate-tempest-dsvm-neutron-linuxbridge
Reviewed: https://review.openstack.org/345253
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=e7e8a4e9385d35a622c27b4787f91f1a928628e3
Submitter: Jenkins
Branch:master
commit e7e8a4e9385d35a622c27b4787f91f1a928628e3
Author: Kevin Benton
Date: Wed Jul 20 19:07:49 2016 -0700
Don't interrupt device loop for missing device
If a device is removed in the middle of
treat_devices_added_updated it can cause failures which
will force all of the other unaffected devices to be
reprocessed. When they are reprocessed it will cause
the ports on the server side to go back into BUILD which
can cause failures in tests expecting ACTIVE ports.
This patch adds an exception catcher that examines if the
port is still present. If it's missing, it suppresses the
exception since the device will be treated as a removed
device on the next iteration.
Closes-Bug: #1605090
Change-Id: Ia774a7c1578f5aca71f3b706e47819b3fdc1cce2
** 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/1605090
Title:
AssertionError: 0 == 0 : No IPv4 addresses found on gate-tempest-dsvm-
neutron-linuxbridge
Status in neutron:
Fix Released
Bug description:
http://logs.openstack.org/73/345173/1/check/gate-tempest-dsvm-neutron-
linuxbridge/2730807/logs/testr_results.html.gz
Traceback (most recent call last):
File "tempest/test.py", line 106, in wrapper
return f(self, *func_args, **func_kwargs)
File "tempest/scenario/test_network_basic_ops.py", line 649, in
test_preserve_preexisting_port
self._setup_network_and_servers(boot_with_port=True)
File "tempest/scenario/test_network_basic_ops.py", line 123, in
_setup_network_and_servers
floating_ip = self.create_floating_ip(server)
File "tempest/scenario/manager.py", line 868, in create_floating_ip
port_id, ip4 = self._get_server_port_id_and_ip4(thing)
File "tempest/scenario/manager.py", line 847, in _get_server_port_id_and_ip4
"No IPv4 addresses found in: %s" % ports)
File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/case.py",
line 845, in assertNotEqual
raise self.failureException(msg)
AssertionError: 0 == 0 : No IPv4 addresses found in: [{u'updated_at':
u'2016-07-21T06:43:05', u'device_id': u'fc965435-3ac5-479c-a348-183c8067f016',
u'created_at': u'2016-07-21T06:42:56', u'tenant_id':
u'728b1d7ba78644738ab1c63b76a53718', u'extra_dhcp_opts': [], u'name':
u'tempest-port-quotatest-52370911', u'binding:vif_details': {u'port_filter':
True}, u'binding:host_id': u'ubuntu-trusty-ovh-gra1-2709194', u'device_owner':
u'compute:None', u'description': u'', u'security_groups':
[u'0bea87ad-beb8-4cf8-b627-6c7f406df3cf'], u'binding:vif_type': u'bridge',
u'mac_address': u'fa:16:3e:f0:d0:2d', u'binding:vnic_type': u'normal',
u'port_security_enabled': True, u'network_id':
u'ced37114-d483-48a4-a0e1-40c338839d54', u'allowed_address_pairs': [],
u'admin_state_up': True, u'id': u'f53c19ec-de16-440a-b1b0-e45e30cc891b',
u'fixed_ips': [{u'ip_address': u'10.100.0.6', u'subnet_id':
u'c5fb097f-6c95-4ce4-9584-de90e70e1dee'}], u'binding:profile': {}, u'status':
u'BUILD'}]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1605090/+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 1605339] [NEW] LaunchInstance NG : Redundant label "Delete Volume on Instance Delete"
Public bug reported:
Master release :
openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/source/source.html
--- _old_source.html2016-07-21 19:09:20.271671469 +0200
+++ source.html 2016-07-21 19:17:25.669747936 +0200
@@ -34,19 +34,6 @@
-
-
-
- Delete Volume on Instance Delete
-
-{$ ::option.label $}
-
-
-
-
** Affects: horizon
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1605339
Title:
LaunchInstance NG : Redundant label "Delete Volume on Instance Delete"
Status in OpenStack Dashboard (Horizon):
New
Bug description:
Master release :
openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/source/source.html
--- _old_source.html2016-07-21 19:09:20.271671469 +0200
+++ source.html 2016-07-21 19:17:25.669747936 +0200
@@ -34,19 +34,6 @@
-
-
-
- Delete Volume on Instance Delete
-
-{$ ::option.label $}
-
-
-
-
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1605339/+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 1515550] Re: in dashboard, can not create a network with the attribute shared
** Changed in: horizon Status: Confirmed => 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/1515550 Title: in dashboard,can not create a network with the attribute shared Status in OpenStack Dashboard (Horizon): Fix Released Bug description: In dashboard web interface,when you create networks,there's no "shared" attribute to choose,however,only use cli command to create a network which is shared To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1515550/+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 1605338] [NEW] Flat Provider Network doesn't work if server have IPv6
Public bug reported: Hey guys, I believe that the following problem: https://ask.openstack.org/en/question/92057/after-creating-selfservice- subnet-neutron-linux-bridge-log-shows-error-rtnetlink-answers- permission-denied/ https://ask.openstack.org/en/question/68190/how-do-i-resolve-rtnetlink- permission-denied-error-encountered-while-running-stacksh/ ...is a bug on OpenStack on Ubuntu Xenial. I faced this problem last night and the workaround (disabling IPv6) works. Now, "ip -6" shows nothing, I can create neutron networks / subnets, no "RTNETLINK answers: Permission denied" anymore. Cheers! Thiago ** 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/1605338 Title: Flat Provider Network doesn't work if server have IPv6 Status in neutron: New Bug description: Hey guys, I believe that the following problem: https://ask.openstack.org/en/question/92057/after-creating- selfservice-subnet-neutron-linux-bridge-log-shows-error-rtnetlink- answers-permission-denied/ https://ask.openstack.org/en/question/68190/how-do-i-resolve- rtnetlink-permission-denied-error-encountered-while-running-stacksh/ ...is a bug on OpenStack on Ubuntu Xenial. I faced this problem last night and the workaround (disabling IPv6) works. Now, "ip -6" shows nothing, I can create neutron networks / subnets, no "RTNETLINK answers: Permission denied" anymore. Cheers! Thiago To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605338/+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 1280522] Re: Replace assertEqual(None, *) with assertIsNone in tests
Reviewed: https://review.openstack.org/340645 Committed: https://git.openstack.org/cgit/openstack/taskflow/commit/?id=38c58123caa559104f0ad7cfd52dd6373792398f Submitter: Jenkins Branch:master commit 38c58123caa559104f0ad7cfd52dd6373792398f Author: weiweigu Date: Tue Jul 12 11:41:52 2016 +0800 Replace assertEqual(None, *) with assertIsNone in tests Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. Change-Id: I74452af6d840bcf612fd3bb2521db9134460dd63 Closes-Bug: #1280522 ** Changed in: taskflow Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to anvil. https://bugs.launchpad.net/bugs/1280522 Title: Replace assertEqual(None, *) with assertIsNone in tests Status in Anchor: Fix Released Status in anvil: New Status in bifrost: Fix Released Status in Blazar: In Progress Status in Cinder: Fix Released Status in congress: Fix Released Status in Designate: Fix Released Status in dox: New Status in DragonFlow: New Status in Freezer: New Status in Glance: Fix Released Status in glance_store: Fix Released Status in heat: Fix Released Status in heat-cfntools: Fix Released Status in Heat Translator: Fix Released Status in OpenStack Dashboard (Horizon): Fix Released Status in Ironic: Fix Released Status in ironic-python-agent: Fix Released Status in OpenStack Identity (keystone): Fix Released Status in keystoneauth: Fix Released Status in kolla-mesos: Fix Released Status in Manila: Fix Released Status in networking-brocade: New Status in networking-cisco: Fix Released Status in OpenStack Compute (nova): Fix Released Status in octavia: Fix Released Status in ooi: Fix Released Status in os-brick: Fix Released Status in os-client-config: Fix Released Status in oslo.messaging: Fix Released Status in python-barbicanclient: Fix Released Status in python-ceilometerclient: Fix Released Status in python-cinderclient: Fix Released Status in python-congressclient: Fix Released Status in python-cueclient: Fix Released Status in python-designateclient: Fix Released Status in python-glanceclient: Fix Released Status in python-heatclient: Fix Released Status in python-ironicclient: Fix Released Status in python-manilaclient: Fix Released Status in python-neutronclient: Fix Released Status in python-openstackclient: Fix Released Status in OpenStack SDK: Fix Released Status in python-swiftclient: Fix Released Status in python-troveclient: Fix Released Status in Python client library for Zaqar: Fix Released Status in Quark: Money Reinvented: New Status in Sahara: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in Solum: Fix Released Status in Stackalytics: Fix Released Status in OpenStack Object Storage (swift): Invalid Status in taskflow: Fix Released Status in tempest: Fix Released Status in OpenStack DBaaS (Trove): Fix Released Status in tuskar: Fix Released Status in watcher: Fix Released Status in zaqar: Fix Released Status in designate package in Ubuntu: Fix Released Status in python-tuskarclient package in Ubuntu: Fix Committed Bug description: Replace assertEqual(None, *) with assertIsNone in tests to have more clear messages in case of failure. To manage notifications about this bug go to: https://bugs.launchpad.net/anchor/+bug/1280522/+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 1595440] Re: neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time
The fact that we don't just rename the agent but introduce an extension does not make the bug invalid. Moving back to Confirmed. ** Changed in: neutron Status: Invalid => Confirmed -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1595440 Title: neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time Status in neutron: Confirmed Bug description: In distributions, it's not possible to ship twice a daemon in /usr/bin with 2 different packages. This means that /usr/bin/neutron-l3-agent in neutron-fwaas is clashing with /usr/bin/neutron-l3-agent from python-neutron. In Debian, we will rename /usr/bin/neutron-l3-agent as /usr/bin/neutron-fwaas-l3-agent. Please do the same upstream. Full explanations on why this is a problem is available here: http://lists.openstack.org/pipermail/openstack-dev/2016-June/097956.html I'm available on IRC if you want to discuss the problem as well. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1595440/+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 1595440] Re: neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time
** Changed in: neutron Status: In Progress => Invalid -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1595440 Title: neutron-fwaas ships /usr/bin/neutron-l3-agent a 2nd time Status in neutron: Invalid Bug description: In distributions, it's not possible to ship twice a daemon in /usr/bin with 2 different packages. This means that /usr/bin/neutron-l3-agent in neutron-fwaas is clashing with /usr/bin/neutron-l3-agent from python-neutron. In Debian, we will rename /usr/bin/neutron-l3-agent as /usr/bin/neutron-fwaas-l3-agent. Please do the same upstream. Full explanations on why this is a problem is available here: http://lists.openstack.org/pipermail/openstack-dev/2016-June/097956.html I'm available on IRC if you want to discuss the problem as well. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1595440/+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 1597699] Re: cc_mcollective.py fails on Ubuntu16.04
This bug was fixed in the package cloud-init - 0.7.7~bzr1256-0ubuntu1~16.04.1 --- cloud-init (0.7.7~bzr1256-0ubuntu1~16.04.1) xenial-proposed; urgency=medium * New upstream snapshot. - distros/debian.py: fix eni renderer to not render .link files - fixes for execution in python2.6. - ConfigDrive: fix writing of 'injected' files and legacy networking (LP: #1602373) - improvements to /etc/network/interfaces rendering including rendering of 'lo' devices and sorting attributes within a interface section. - fix mcollective module that was completely broken if using python3 (LP: #1597699) -- Scott Moser Fri, 15 Jul 2016 13:27:04 -0400 ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1597699 Title: cc_mcollective.py fails on Ubuntu16.04 Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Released Bug description: Begin SRU Template [Impact] mcollective usage via cloud-init is not possible. [Test Case] launch instance with cloud-config containing 'mcollective' entry. $ cat >user-data <<"EOF" #cloud-config mcollective: conf: main_collective: mcollective collectives: mcollective libdir: /usr/share/mcollective/plugins logfile: /var/log/mcollective.log loglevel: debug daemonize: 1 direct_addressing: 1 ttl: 4294957 securityprovider: psk plugin.psk: unset identity: 2 connector: rabbitmq plugin.rabbitmq.vhost: mcollective plugin.rabbitmq.pool.size: 1 plugin.rabbitmq.pool.1.host: 10.10.0.2 plugin.rabbitmq.pool.1.port: 61613 plugin.rabbitmq.pool.1.user: mcollective plugin.rabbitmq.pool.1.password: ScwpVo8egrZ0OmT6sRmp9zEA plugin.rabbitmq.heartbeat_interval: 30 factsource: yaml plugin.yaml: /etc/mcollective/facts.yaml EOF $ keyname=brickies; image=$image; $ openstack server create \ --key-name=$keyname --flavor=m1.small \ --image=$image --user-data=user-data mcollective-test0 # then ssh in and a.) verify mcollective package is installed $ dpkg-query --show mcollective mcollective 2.6.0+dfsg-2.1 b.) verify mcollective service is running $ systemctl status mcollective c.) grep WARN /var/log/cloud-init.log && echo FAIL [Regression Potential] low to none. This has been unfortunately broken since wily. [Other Info] End SRU Template How to reproduce: #cat /etc/issue.net Ubuntu 16.04 LTS #( cd /var/lib/cloud/ && rm -rf * ) #cloud-init -d init #grep ^mcollective: -A25 instance/user-data.txt mcollective: conf: main_collective: mcollective collectives: mcollective libdir: /usr/share/mcollective/plugins logfile: /var/log/mcollective.log loglevel: debug daemonize: 1 direct_addressing: 1 ttl: 4294957 securityprovider: psk plugin.psk: unset identity: 2 connector: rabbitmq plugin.rabbitmq.vhost: mcollective plugin.rabbitmq.pool.size: 1 plugin.rabbitmq.pool.1.host: 10.10.0.2 plugin.rabbitmq.pool.1.port: 61613 plugin.rabbitmq.pool.1.user: mcollective plugin.rabbitmq.pool.1.password: ScwpVo8egrZ0OmT6sRmp9zEA plugin.rabbitmq.heartbeat_interval: 30 factsource: yaml plugin.yaml: /etc/mcollective/facts.yaml #cloud-init -d single --name mcollective The log will contain Jun 30 08:26:43 node-2 [CLOUDINIT] util.py[DEBUG]: Running module mcollective () failed#012Traceback (most recent call last):#012 File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 739, in _run_modules#012freq=freq)#012 File "/usr/lib/python3/dist- packages/cloudinit/cloud.py", line 70, in run#012return self._runners.run(name, functor, args, freq, clear_on_fail)#012 File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 199, in run#012results = functor(*args)#012 File "/usr/lib/python3/dist- packages/cloudinit/config/cc_mcollective.py", line 83, in handle#012 mcollective_config.write(contents)#012 File "/usr/lib/python3/dist- packages/configobj.py", line 2126, in write#012 outfile.write(output_bytes)#012TypeError: string argument expected, got 'bytes' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1597699/+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 1602373] Re: cloud-init doesn't always land files that one expects
This bug was fixed in the package cloud-init -
0.7.7~bzr1256-0ubuntu1~16.04.1
---
cloud-init (0.7.7~bzr1256-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* New upstream snapshot.
- distros/debian.py: fix eni renderer to not render .link files
- fixes for execution in python2.6.
- ConfigDrive: fix writing of 'injected' files and legacy networking
(LP: #1602373)
- improvements to /etc/network/interfaces rendering including rendering
of 'lo' devices and sorting attributes within a interface section.
- fix mcollective module that was completely broken if using python3
(LP: #1597699)
-- Scott Moser Fri, 15 Jul 2016 13:27:04 -0400
** Changed in: cloud-init (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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/1602373
Title:
cloud-init doesn't always land files that one expects
Status in cloud-init:
Fix Committed
Status in cloud-init package in Ubuntu:
Fix Released
Status in cloud-init source package in Xenial:
Fix Released
Bug description:
Begin SRU Template
[Impact]
Injected files functionality of OpenStack's config drive is broken.
[Test Case]
== Reproduce broken functionality ==
$ echo "hi mom" > my-file.txt
$ cat > "user-data" <<"EOF"
#!/bin/sh
logfile=/run/my.log
file="/my-file.txt"
if [ -e "$file" ]; then
( echo "=== PASS: file $file " ; cat $file ) | tee -a $logfile
exit 0
else
echo "=== FAIL: no file $file " | tee -a $logfile
exit 0
fi
EOF
openstack server create --key-name=brickies --flavor=m1.small \
--config-drive=1 --image=$img \
--user-data=user-data --file=/my-file.txt=my-file.txt \
injected-file0
The launched system will have a file in /run/my.log that shows 'FAIL'
and will not have /my-file.txt on disk.
== See Fix ==
# enable proposed
$ cat > enable-proposed <<"EOF"
#!/bin/sh
set -e
rel=$(lsb_release -sc)
awk '$1 == "deb" && $2 ~ /ubuntu.com/ {
printf("%s %s %s-proposed main universe\n", $1, $2, rel); exit(0) };
' "rel=$rel" /etc/apt/sources.list |
tee /etc/apt/sources.list.d/proposed.list
EOF
$ sudo sh ./enable-proposed
$ sudo apt-get update
$ sudo apt-get install cloud-init
# Remove /var/lib/cloud and /var/log/cloud-init* to remove state
# and indicate this is a new instance on reboot
$ sudo rm -Rf /var/lib/cloud /var/log/cloud-init*
$ sudo reboot
Now ssh back in after reboot, you should
a.) have /my-file.txt
b.) see PASS in /run/my.log
c.) see mention of the 'injected file' in /var/log/cloud-init.log
[Regression Potential]
Regression potential on Ubuntu should be very small.
End SRU Template
Trove launches instances using the servers.create() API with some
files. Trove provides a dictionary of files that it wants on the
instance and most of the time this works. Nova passes them to the
launched VM as metadata on config drive.
Sometimes though, it doesn't.
When injection fails, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/7566d8fef4b6e813cca77e5e3b1f1d5a
When injection succeeds, I see a cloud-init.log that looks like this:
https://gist.github.com/amrith/50d9e3050d88ec51e13b0a510bd718c3
Observe that the one that succeeds properly injects three files:
/etc/injected_files (which is something I added just for debugging)
/etc/trove/conf.d/... two files here ...
On a machine where this injection failed:
root@m10:/tmp/zz/openstack/content# ls -l /etc/trove
total 4
drwxr-xr-x 2 amrith root 4096 Jul 12 16:55 conf.d
root@m10:/tmp/zz/openstack/content# ls -l /etc/trove/conf.d/
total 4
root@m10:/tmp/zz/openstack/content#
Clearly, no files made it over. Yet, the files are definitely there on
the config drive ...
I've mounted the config drive.
root@m10:/tmp/zz/openstack/content# mount | grep zz
/dev/sr0 on /tmp/zz type iso9660 (ro,relatime)
root@m10:/tmp/zz/openstack/content# cd /tmp/zz
root@m10:/tmp/zz# find .
.
./ec2
./ec2/2009-04-04
./ec2/2009-04-04/meta-data.json
./ec2/latest
./ec2/latest/meta-data.json
./openstack
./openstack/2012-08-10
./openstack/2012-08-10/meta_data.json
./openstack/2013-04-04
./openstack/2013-04-04/meta_data.json
./openstack/2013-10-17
./openstack/2013-10-17/meta_data.json
./openstack/2013-10-17/vendor_data.json
./openstack/2015-10-15
./openstack/2015-10-15/meta_data.json
./openstack/2015-10-15/network_data.json
./openstack/2015-10-15/vendor_data.json
./openstack/2016-06-30
./openstack/2016-06-30/meta_data.json
./openstack/2016-06-30/network_data.json
./openstack/2016-06-30/vendor_data.json
./openstack/content
./openstack/content/
./openstack/content/0001
./openstack/content/0002
./openstack/latest
./openstack/latest/meta_data.json
./
[Yahoo-eng-team] [Bug 1600530] Re: Part 2 of engine DB facade breaks metadata agent
** 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/1600530 Title: Part 2 of engine DB facade breaks metadata agent Status in neutron: Fix Released Bug description: On devstack, tip of tree master: Commit [1] breaks metadata agent on compute nodes with the following error: 2016-07-09 16:49:52.427 ^[[01;31mCRITICAL neutron [^[[01;36mreq-ded33b76-bd78-4ce6-916e-53d8eedfc1d3 ^[[00;36mNone None^[[01;31m] ^[[01;35m^[[01;31mArgumentError: Could not parse rfc1738 URL from string ''^M ^[[00m^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00mTraceback (most recent call last):^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/bin/neutron-metadata-agent", line 10, in ^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m sys.exit(main())^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/cmd/eventlet/agents/metadata.py", line 17, in main^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m metadata_agent.main()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/agent/metadata_agent.py", line 41, in main^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m proxy.run()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/agent/metadata/agent.py", line 298, in run^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m mode=self._get_socket_mode())^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/agent/linux/utils.py", line 372, in start^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m self._launch(application, workers=workers)^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/wsgi.py", line 206, in _launch^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m api.dispose()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/db/api.py", line 110, in dispose^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m get_engine().pool.dispose()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/opt/stack/neutron/neutron/db/api.py", line 106, in get_engine^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00mreturn context_manager.get_legacy_facade().get_engine()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 636, in get_legacy_facade^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00mreturn self._factory.get_legacy_facade()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 256, in get_legacy_facade^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m self._start()^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 338, in _start^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m engine_args, maker_args)^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/enginefacade.py", line 362, in _setup_for_connection^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m sql_connection=sql_connection, **engine_kwargs)^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/engines.py", line 112, in create_engine^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00murl = sqlalchemy.engine.url.make_url(sql_connection)^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/url.py", line 186, in make_url^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00mreturn _parse_rfc1738_args(name_or_url)^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m File "/usr/local/lib/python2.7/dist-packages/sqlalchemy/engine/url.py", line 235, in _parse_rfc1738_args^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m"Could not parse rfc1738 URL from string '%s'" % name)^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00mArgumentError: Could not parse rfc1738 URL from string ''^M ^[[01;31m2016-07-09 16:49:52.427 TRACE neutron ^[[01;35m^[[00m^M Reverting commit [1] allows metadata agent to start [1] https://review.openstack.org/312393 T
[Yahoo-eng-team] [Bug 1605285] [NEW] StaleDataError on ha_router_agent_port_bindings update
Public bug reported: Stacktrace: http://paste.openstack.org/show/539055/ There are a number of currently opened bugs that might deal with this, but they are clouded with information that might not be relevant. I will wade through them in the upcoming days to see if I can find something similar to the stack (though at first glance I didn't). Also, this happened on stable/mitaka. It's interesting to see if this also happens on master. it reproduced while running rally's create_and_delete_routers with high (=10) concurrency. ** 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/1605285 Title: StaleDataError on ha_router_agent_port_bindings update Status in neutron: New Bug description: Stacktrace: http://paste.openstack.org/show/539055/ There are a number of currently opened bugs that might deal with this, but they are clouded with information that might not be relevant. I will wade through them in the upcoming days to see if I can find something similar to the stack (though at first glance I didn't). Also, this happened on stable/mitaka. It's interesting to see if this also happens on master. it reproduced while running rally's create_and_delete_routers with high (=10) concurrency. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605285/+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 1605282] [NEW] Transaction rolled back while creating HA router
Public bug reported: The stacktrace can be found here: http://paste.openstack.org/show/539052/ This was discovered while running the create_and_delete_router rally test with a high (~10) concurrency number. I encountered this on stable/mitaka so it's interesting to see if this reproduces on master. ** 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/1605282 Title: Transaction rolled back while creating HA router Status in neutron: New Bug description: The stacktrace can be found here: http://paste.openstack.org/show/539052/ This was discovered while running the create_and_delete_router rally test with a high (~10) concurrency number. I encountered this on stable/mitaka so it's interesting to see if this reproduces on master. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605282/+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 1605277] [NEW] [IPAM] 'Internal' ipam driver does not allow to delete all pools on subnet update
Public bug reported: During investigation UT test failure 'test_port_update_deferred_allocation_no_ips' in [1] I found that attempt to update subnet providing blank ([]) allocation pools leads to silent ignoring this action on ipam driver side. Reference ipam driver skips processing of the update request because of condition "if not subnet_request.allocation_pools" in [2], which is too strict and does not allow to clean up allocation pools on subnet update. It is a because cleaning up allocation pools is a valid user action and built-in ipam implementation allows to do it. Expected behavior: Reference ipam driver should work the same as a built-in implementation and should allow to remove 'allocation_pools' on subnet update. [1] http://logs.openstack.org/23/181023/89/check/gate-neutron-python27/2071f1d/testr_results.html.gz [2] https://github.com/openstack/neutron/blob/38a080aca37197ff9c5464a3bc9981e684decee6/neutron/ipam/drivers/neutrondb_ipam/driver.py#L294 ** 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/1605277 Title: [IPAM] 'Internal' ipam driver does not allow to delete all pools on subnet update Status in neutron: New Bug description: During investigation UT test failure 'test_port_update_deferred_allocation_no_ips' in [1] I found that attempt to update subnet providing blank ([]) allocation pools leads to silent ignoring this action on ipam driver side. Reference ipam driver skips processing of the update request because of condition "if not subnet_request.allocation_pools" in [2], which is too strict and does not allow to clean up allocation pools on subnet update. It is a because cleaning up allocation pools is a valid user action and built-in ipam implementation allows to do it. Expected behavior: Reference ipam driver should work the same as a built-in implementation and should allow to remove 'allocation_pools' on subnet update. [1] http://logs.openstack.org/23/181023/89/check/gate-neutron-python27/2071f1d/testr_results.html.gz [2] https://github.com/openstack/neutron/blob/38a080aca37197ff9c5464a3bc9981e684decee6/neutron/ipam/drivers/neutrondb_ipam/driver.py#L294 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605277/+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 1605271] [NEW] Enable multinode grenade gate for Linuxbridge
Public bug reported: OVS is covered in gate, we should do the same for Linuxbridge. ** Affects: neutron Importance: Wishlist Assignee: Ihar Hrachyshka (ihar-hrachyshka) Status: In Progress ** Tags: linuxbridge ** Changed in: neutron Importance: Undecided => Wishlist ** Tags added: linuxbridge ** Changed in: neutron Status: New => In Progress ** Changed in: neutron Assignee: (unassigned) => Ihar Hrachyshka (ihar-hrachyshka) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1605271 Title: Enable multinode grenade gate for Linuxbridge Status in neutron: In Progress Bug description: OVS is covered in gate, we should do the same for Linuxbridge. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605271/+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 1605264] [NEW] Return date lacks gw_port_id when setting router gateway port.
Public bug reported: Return date lacks gw_port_id when setting router gateway port. This column is defined in db code, but lost in API extension attributes file. ** Affects: neutron Importance: Undecided Assignee: hujin (hujin) Status: New ** Changed in: neutron Assignee: (unassigned) => hujin (hujin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1605264 Title: Return date lacks gw_port_id when setting router gateway port. Status in neutron: New Bug description: Return date lacks gw_port_id when setting router gateway port. This column is defined in db code, but lost in API extension attributes file. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605264/+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 1531337] Re: Update xstatic-jsencrypt package
** Changed in: horizon Status: In Progress => Invalid ** Changed in: horizon Milestone: newton-3 => None ** Changed in: horizon Assignee: Rajat Vig (rajatv) => (unassigned) -- 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/1531337 Title: Update xstatic-jsencrypt package Status in OpenStack Dashboard (Horizon): Invalid Bug description: XStatic-JSEncrypt needs to be updated to 2.1.0 https://github.com/travist/jsencrypt/tree/v2.1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1531337/+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 1531313] Re: Update xstatic-rickshaw package
** Changed in: horizon Milestone: newton-3 => newton-2 ** 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/1531313 Title: Update xstatic-rickshaw package Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Update the XStatic Package for Rickshaw from 1.5.0 to 1.5.1 https://github.com/shutterstock/rickshaw To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1531313/+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 1603146] Re: create network with subnet broken for non admins
** Changed in: horizon Status: Fix Committed => 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/1603146 Title: create network with subnet broken for non admins Status in OpenStack Dashboard (Horizon): Fix Released Bug description: https://bugs.launchpad.net/horizon/+bug/1398845 Broke network creation for normal users, that also want to create a subnet. The policy check is not the correct one to use, as there is no existing network to check ownership against. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1603146/+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 1583419] Re: Make dict.keys() PY3 compatible
Reviewed: https://review.openstack.org/341946
Committed:
https://git.openstack.org/cgit/openstack/watcher/commit/?id=cd60336e209e8900d28e06c167977ba21a07038c
Submitter: Jenkins
Branch:master
commit cd60336e209e8900d28e06c167977ba21a07038c
Author: weiweigu
Date: Thu Jul 14 13:45:47 2016 +0800
Fix dict.keys() PY3 compatible
The dict.keys()[0] will raise a TypeError in PY3,
as dict.keys() doesn't return a list any more in PY3
but a view of list.
Change-Id: If15a153c9db9b654e761f8ad50d5d66a427efa4e
Closes-Bug: #1583419
** Changed in: watcher
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/1583419
Title:
Make dict.keys() PY3 compatible
Status in Cinder:
Fix Released
Status in neutron:
Fix Released
Status in python-cinderclient:
Fix Released
Status in python-manilaclient:
Fix Released
Status in python-troveclient:
Fix Released
Status in Rally:
Fix Released
Status in tacker:
Fix Released
Status in watcher:
Fix Released
Bug description:
In PY3, dict.keys() will return a view of list but not a list anymore, i.e.
$ python3.4
Python 3.4.3 (default, Mar 31 2016, 20:42:37)
>>> body={"11":"22"}
>>> body[body.keys()[0]]
Traceback (most recent call last):
File "", line 1, in
TypeError: 'dict_keys' object does not support indexing
so for py3 compatible we should change it as follows:
>>> body[list(body.keys())[0]]
'22'
To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1583419/+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 1603268] Re: Unstable grenade multinode job
Seems like grafana dashboard shows that the issue went away, and the job is now on par with other multinode jobs in terms of rate of failures in check queue. Closing the bug. ** 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/1603268 Title: Unstable grenade multinode job Status in neutron: Fix Released Bug description: Grafana is showing the gate-grenade-dsvm-neutron-multinode being unstable since July 12th [1,2]. The issue seems related to Grenade verify phase getting stalled [3]. Probably MTU related as the SSH times out. 2016-07-09 10:16:00.716 | ++ /opt/stack/new/grenade/projects/70_cinder/resources.sh:verify_noapi:177 : resource_get cinder cinder_server_ip 2016-07-09 10:16:00.717 | ++ /opt/stack/new/grenade/inc/plugin:resource_get:137 : local project=cinder 2016-07-09 10:16:00.718 | ++ /opt/stack/new/grenade/inc/plugin:resource_get:138 : local key=cinder_server_ip 2016-07-09 10:16:00.720 | +++ /opt/stack/new/grenade/inc/plugin:resource_get:139 : iniget /opt/stack/save/grenade_db.ini cinder cinder_server_ip 2016-07-09 10:16:00.733 | ++ /opt/stack/new/grenade/inc/plugin:resource_get:139 : local value=172.24.5.51 2016-07-09 10:16:00.734 | ++ /opt/stack/new/grenade/inc/plugin:resource_get:140 : echo 172.24.5.51 2016-07-09 10:16:00.737 | + /opt/stack/new/grenade/projects/70_cinder/resources.sh:verify_noapi:177 : local server_ip=172.24.5.51 2016-07-09 10:16:00.739 | + /opt/stack/new/grenade/projects/70_cinder/resources.sh:verify_noapi:178 : ping_check_public 172.24.5.51 30 2016-07-09 10:16:00.740 | + /opt/stack/new/grenade/functions:ping_check_public:56 : local ip=172.24.5.51 2016-07-09 10:16:00.741 | + /opt/stack/new/grenade/functions:ping_check_public:57 : local boot_timeout=30 2016-07-09 10:16:00.743 | + /opt/stack/new/grenade/functions:ping_check_public:58 : local expected=True 2016-07-09 10:16:00.745 | + /opt/stack/new/grenade/functions:ping_check_public:59 : local check_command= 2016-07-09 10:16:00.746 | + /opt/stack/new/grenade/functions:ping_check_public:60 : [[ True = \T\r\u\e ]] 2016-07-09 10:16:00.747 | + /opt/stack/new/grenade/functions:ping_check_public:61 : check_command='while ! ping -c1 -w1 172.24.5.51; do sleep 1; done' 2016-07-09 10:16:00.749 | + /opt/stack/new/grenade/functions:ping_check_public:65 : timeout 30 sh -c 'while ! ping -c1 -w1 172.24.5.51; do sleep 1; done' 2016-07-09 10:16:00.755 | PING 172.24.5.51 (172.24.5.51) 56(84) bytes of data. 2016-07-09 10:16:00.755 | 64 bytes from 172.24.5.51: icmp_seq=1 ttl=63 time=2.81 ms 2016-07-09 10:16:00.755 | 2016-07-09 10:16:00.755 | --- 172.24.5.51 ping statistics --- 2016-07-09 10:16:00.755 | 1 packets transmitted, 1 received, 0% packet loss, time 0ms 2016-07-09 10:16:00.755 | rtt min/avg/max/mdev = 2.811/2.811/2.811/0.000 ms 2016-07-09 10:16:00.757 | + /opt/stack/new/grenade/projects/70_cinder/resources.sh:verify_noapi:181 : timeout 30 ssh -v -o ConnectTimeout=10 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -i /opt/stack/save/cinder_key.pem cirros@172.24.5.51 sync 2016-07-09 10:16:00.761 | OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 2016-07-09 10:16:00.762 | debug1: Reading configuration data /etc/ssh/ssh_config 2016-07-09 10:16:00.762 | debug1: /etc/ssh/ssh_config line 19: Applying options for * 2016-07-09 10:16:00.762 | debug1: Connecting to 172.24.5.51 [172.24.5.51] port 22. 2016-07-09 10:16:00.763 | debug1: fd 3 clearing O_NONBLOCK 2016-07-09 10:16:00.763 | debug1: Connection established. 2016-07-09 10:16:00.764 | debug1: identity file /opt/stack/save/cinder_key.pem type -1 2016-07-09 10:16:00.764 | debug1: identity file /opt/stack/save/cinder_key.pem-cert type -1 2016-07-09 10:16:00.764 | debug1: Enabling compatibility mode for protocol 2.0 2016-07-09 10:16:00.764 | debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.7 2016-07-09 10:16:00.770 | debug1: Remote protocol version 2.0, remote software version dropbear_2012.55 2016-07-09 10:16:00.770 | debug1: no match: dropbear_2012.55 2016-07-09 10:16:00.770 | debug1: SSH2_MSG_KEXINIT sent 2016-07-09 10:16:00.773 | debug1: SSH2_MSG_KEXINIT received 2016-07-09 10:16:00.773 | debug1: kex: server->client aes128-ctr hmac-md5 none 2016-07-09 10:16:00.773 | debug1: kex: client->server aes128-ctr hmac-md5 none 2016-07-09 10:16:00.774 | debug1: sending SSH2_MSG_KEXDH_INIT == 2016-07-09 10:16:00.774 | debug1: expecting SSH2_MSG_KEXDH_REPLY 2016-07-09 10:16:30.760 | + /opt/stack/new/grenade/projects/70_cinder/resources.sh:verify_noapi:1 : exit_trap == 2016-07-09 10:16:30.762 | + /opt/stack/new/grenade/functions:exit_trap:103 : local r=124 2016-07-09 10:16:30.763
[Yahoo-eng-team] [Bug 1605201] [NEW] OperationalError:'SAVEPOINT sa_savepoint_1 does not exist' during Rally boot_and_delete_server_with_secgroups
Public bug reported: Scale environment 45 compute node, 3 controller, Mitaka. During execution of Rally test boot_and_delete_server_with_secgroups error appeared in logs 2016-07-03 08:05:02.314 21792 INFO neutron.plugins.ml2.db [req-0d9d3031-0698-4a24-9ce0-4c886d641c91 ea3ede1f05e348e7853e9f 42c9426830 dc754a03f8de4b468396f8bc3d4a94ee - - -] Added segment af70f885-39df-4c2b-adfc-225d81c8c03c of type vxlan for ne twork 967af409-e2f4-418a-8919-a7e4a2133996 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource [req-1e786fea-0a7b-4613-9914-bda50be6028e d044072ee7c447bb922d 778565b329e2 715ca0f3f5a74733a49133c4d2202939 - - -] create failed 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource Traceback (most recent call last): 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/resour ce.py", line 84, in resource 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource result = method(request=request, **args) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.p y", line 410, in create 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource return self._create(request, body, **kwargs) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_db/api.py", line 148, in wrapper 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource ectxt.value = e.inner_exc 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.p y", line 220, in __exit__ 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource self.force_reraise() 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.p y", line 196, in force_reraise 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_db/api.py", line 138, in wrapper 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource return f(*args, **kwargs) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.p 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.p y", line 521, in _create 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource obj = do_create(body) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.p y", line 503, in do_create 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource request.context, reservation.reservation_id) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.p y", line 220, in __exit__ 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource self.force_reraise() 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.p y", line 196, in force_reraise 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource six.reraise(self.type_, self.value, self.tb) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.p y", line 496, in do_create 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource return obj_creator(request.context, **kwargs) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/p lugin.py", line 696, in create_network 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource result, mech_context = self._create_network_db(context, ne twork) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/p lugin.py", line 659, in _create_network_db 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource self._ensure_default_security_group(context, tenant_id) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/db/securitygr oups_db.py", line 709, in _ensure_default_security_group 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource return self._create_default_security_group(context, tenant _id) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/db/securitygr oups_db.py", line 720, in _create_default_security_group 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource context, security_group, default_sg=True) 2016-07-03 08:05:02.316 21787 ERROR neutron.api.v2.resource File "/usr/lib/python2.7/dist-packages/neutron/db/securitygr oups_db.py", line 189, in create_security_group 2016-07-03 08:05:02.316 21787
[Yahoo-eng-team] [Bug 1286099] Re: UpdateProjectQuotas doesn't pay attention on disabled_quotas
Reviewed: https://review.openstack.org/215277 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=baca29144b5f3e771e780d86210c11e85d8351ed Submitter: Jenkins Branch:master commit baca29144b5f3e771e780d86210c11e85d8351ed Author: Timur Sufiev Date: Fri Aug 21 13:22:03 2015 +0300 Pay attention to Nova disabled quotas defined in a config file Since Nova doesn't currently provide an API call to indicate whether its quotas are disabled, we could use a parameter named 'enable_quotas' within 'OPENSTACK_HYPERVISOR_FEATURES' setting for this purpose. This allows to avoid errors while trying to update quotas which are disabled on service side. Also make disabled_quotas collection to be a set instead of a list - this removes duplicate fields that appear due to some possible quota overlaps between Nova and Neutron. Also, since we dropped out python2.6 support fancy set literals and dict comprehensions can be used. Co-Authored-By: Paul Karikh Closes-Bug: #1286099 Change-Id: I10923f147e4c323aba8bbcc130d2016ad6725e86 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1286099 Title: UpdateProjectQuotas doesn't pay attention on disabled_quotas Status in OpenStack Dashboard (Horizon): Fix Released Status in OpenStack Compute (nova): Fix Released Bug description: Environment: - OpenStack Havana release (2013.2.1) - Neutron Steps to reproduce: - Go to admin -> projects - Try to update project quotas - Update fails with "Error: Modified project information and members, but unable to modify project quotas." Workaround: Comment out "security_group", "security_group_rule" in NEUTRON_QUOTA_FIELDS (openstack_dashboard/usage/quotas.py) In neutron/server.log: 2014-02-28 11:45:03.145 34093 ERROR neutron.api.v2.resource [-] update failed 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource Traceback (most recent call last): 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource File "/usr/lib/python2.6/site-packages/neutron/api/v2/resource.py", line 84, in resource 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource result = method(request=request, **args) 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource File "/usr/lib/python2.6/site-packages/neutron/extensions/quotasv2.py", line 107, in update 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource EXTENDED_ATTRIBUTES_2_0[RESOURCE_COLLECTION]) 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource File "/usr/lib/python2.6/site-packages/neutron/api/v2/base.py", line 555, in prepare_request_body 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource Controller._verify_attributes(res_dict, attr_info) 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource File "/usr/lib/python2.6/site-packages/neutron/api/v2/base.py", line 602, in _verify_attributes 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource raise webob.exc.HTTPBadRequest(msg) 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource HTTPBadRequest: Unrecognized attribute(s) 'security_group_rule, security_group' 2014-02-28 11:45:03.145 34093 TRACE neutron.api.v2.resource To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1286099/+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 1544861] Re: LBaaS: connection limit does not work with HA Proxy
Reviewed: https://review.openstack.org/341806 Committed: https://git.openstack.org/cgit/openstack/neutron-lbaas/commit/?id=56b8a621509af9688e6fcaa98e511702d68ba0b2 Submitter: Jenkins Branch:master commit 56b8a621509af9688e6fcaa98e511702d68ba0b2 Author: Dustin Lundquist Date: Wed Jul 13 13:54:44 2016 -0700 haproxy ns driver: set global haproxy maxconn Haproxy uses two separate maxconn values: the maxconn setting in the global context is used to adjust file descriptor limits and allocate resources, while the maxconn setting in the frontend context controls if additional connections are accepted on that frontend. This patch adds a maxconn to the global context equal to the sum of the connection limit on each listener. Change-Id: I950abaed780d7df33f0ab5c682bf583aa581889f Closes-Bug: 1544861 ** 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/1544861 Title: LBaaS: connection limit does not work with HA Proxy Status in neutron: Fix Released Bug description: connection limit does not work with HA Proxy. It sets at frontend section like: frontend 75a12b66-9d2a-4a68-962e-ec9db8c3e2fb option httplog capture cookie JSESSIONID len 56 bind 192.168.10.20:80 mode http default_backend fb8ba6e3-71a4-47dd-8a83-2978bafea6e7 maxconn 5 option forwardfor But above configuration does not work. It should be set at global section like: global daemon user nobody group haproxy log /dev/log local0 log /dev/log local1 notice stats socket /var/lib/neutron/lbaas/fb8ba6e3-71a4-47dd-8a83-2978bafea6e7/sock mode 0666 level user maxconn 5 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1544861/+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 1600777] Re: Displays all activated baremetal nodes in nova hypervisor-list
** Project changed: fuel-plugin-contrail => nova -- 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/1600777 Title: Displays all activated baremetal nodes in nova hypervisor-list Status in OpenStack Compute (nova): New Bug description: We are provisioning baremetal(Ironic) nodes as instances, when we try to check the nova hypervisor-list it is listing all the nodes which are in activated state and also when we check the nova hypervisor- stats the disk_available_least is showing in negative value though there are servers in available state. stack@helion-cp1-c1-m1-mgmt:~$ nova hypervisor-stats +--+---+ | Property | Value | +--+---+ | count| 131 | | current_workload | 0 | | disk_available_least | -9040 | | free_disk_gb | 720 | | free_ram_mb | 36864 | | local_gb | 720 | | local_gb_used| 0 | | memory_mb| 36864 | | memory_mb_used | 0 | | running_vms | 122 | | vcpus| 18| | vcpus_used | 0 | +--+---+ stack@helion-cp1-c1-m1-mgmt:~$ nova hypervisor-list +-+--+---+-+ | ID | Hypervisor hostname | State | Status | +-+--+---+-+ | 1 | bd334756-4033-4dea-8a73-8d24df5c7043 | up| enabled | | 7 | 69e3fbda-b0a7-4439-ba8f-f9ecedc9c70e | up| enabled | | 10 | 5b2619eb-d0c3-4144-82d3-72f2c926a03a | up| enabled | | 13 | a29266ec-b820-4a03-bd39-a4e057cf2620 | up| enabled | | 16 | f10c3922-a7f9-44ec-a3f6-b6930de2ab00 | up| enabled | | 19 | 72602da2-76cd-4ace-966a-554e73a5f5a8 | up| enabled | | 22 | 5237fddf-a7b2-44e4-949b-6d3fd50f7c13 | up| enabled | | 25 | 240ade58-5ae5-46b7-9854-c8f92353c6f2 | up| enabled | | 28 | 1ac39438-6eef-4625-8916-0d5f70a38d75 | up| enabled | | 31 | 85e0d313-5e79-46ef-8497-dd527584f916 | up| enabled | | 34 | de4e172b-19e1-4f3c-9865-a3c6e68d292c | up| enabled | | 37 | dd5453a3-52fb-420d-81f2-6cb84fbbb241 | up| enabled | | 40 | 8da2a739-0910-40e2-bca7-102fb56a31d5 | up| enabled | | 43 | b99abcf8-7c0b-476e-aadf-60c1a3adfd49 | up| enabled | | 46 | 5016fa3e-d7e2-4e34-bed2-73abeaca466a | up| enabled | | 49 | 46796e87-8f3b-4638-8866-1d6ce2e91077 | up| enabled | | 52 | 27d35b26-ac65-40cb-a5ef-ace06ea3877f | up| enabled | | 55 | e241014a-2c3e-4884-90ae-e94af4cfaff4 | up| enabled | | 58 | 156ccbb7-5a82-4161-8b21-aaa647fc0f26 | up| enabled | To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1600777/+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 1595786] Re: Make string.letters PY3 compatible
** Changed in: fuel-plugin-contrail 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/1595786 Title: Make string.letters PY3 compatible Status in Fuel Contrail plugin: Fix Released Status in Fuel Plugins: Fix Committed Status in OpenStack Compute (nova): In Progress Status in python-novaclient: Fix Released Status in OpenStack Search (Searchlight): Fix Released Status in OpenStack Object Storage (swift): Fix Released Bug description: String.letters and related.Lowercase and.Uppercase are removed, please switch to string.ascii_letters, etc. as: https://github.com/openstack/nova/blob/04f2d81bb4d1e26482b613ab799bb38ce304e143/nova/tests/unit/api/openstack/compute/test_console_output.py#L102 To manage notifications about this bug go to: https://bugs.launchpad.net/fuel-plugin-contrail/+bug/1595786/+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 1600777] [NEW] Displays all activated baremetal nodes in nova hypervisor-list
You have been subscribed to a public bug: We are provisioning baremetal(Ironic) nodes as instances, when we try to check the nova hypervisor-list it is listing all the nodes which are in activated state and also when we check the nova hypervisor-stats the disk_available_least is showing in negative value though there are servers in available state. stack@helion-cp1-c1-m1-mgmt:~$ nova hypervisor-stats +--+---+ | Property | Value | +--+---+ | count| 131 | | current_workload | 0 | | disk_available_least | -9040 | | free_disk_gb | 720 | | free_ram_mb | 36864 | | local_gb | 720 | | local_gb_used| 0 | | memory_mb| 36864 | | memory_mb_used | 0 | | running_vms | 122 | | vcpus| 18| | vcpus_used | 0 | +--+---+ stack@helion-cp1-c1-m1-mgmt:~$ nova hypervisor-list +-+--+---+-+ | ID | Hypervisor hostname | State | Status | +-+--+---+-+ | 1 | bd334756-4033-4dea-8a73-8d24df5c7043 | up| enabled | | 7 | 69e3fbda-b0a7-4439-ba8f-f9ecedc9c70e | up| enabled | | 10 | 5b2619eb-d0c3-4144-82d3-72f2c926a03a | up| enabled | | 13 | a29266ec-b820-4a03-bd39-a4e057cf2620 | up| enabled | | 16 | f10c3922-a7f9-44ec-a3f6-b6930de2ab00 | up| enabled | | 19 | 72602da2-76cd-4ace-966a-554e73a5f5a8 | up| enabled | | 22 | 5237fddf-a7b2-44e4-949b-6d3fd50f7c13 | up| enabled | | 25 | 240ade58-5ae5-46b7-9854-c8f92353c6f2 | up| enabled | | 28 | 1ac39438-6eef-4625-8916-0d5f70a38d75 | up| enabled | | 31 | 85e0d313-5e79-46ef-8497-dd527584f916 | up| enabled | | 34 | de4e172b-19e1-4f3c-9865-a3c6e68d292c | up| enabled | | 37 | dd5453a3-52fb-420d-81f2-6cb84fbbb241 | up| enabled | | 40 | 8da2a739-0910-40e2-bca7-102fb56a31d5 | up| enabled | | 43 | b99abcf8-7c0b-476e-aadf-60c1a3adfd49 | up| enabled | | 46 | 5016fa3e-d7e2-4e34-bed2-73abeaca466a | up| enabled | | 49 | 46796e87-8f3b-4638-8866-1d6ce2e91077 | up| enabled | | 52 | 27d35b26-ac65-40cb-a5ef-ace06ea3877f | up| enabled | | 55 | e241014a-2c3e-4884-90ae-e94af4cfaff4 | up| enabled | | 58 | 156ccbb7-5a82-4161-8b21-aaa647fc0f26 | up| enabled | ** Affects: nova Importance: Undecided Status: New -- Displays all activated baremetal nodes in nova hypervisor-list https://bugs.launchpad.net/bugs/1600777 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). -- 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 1604842] Re: Should hide expand while we haven't setTemplateUrl
Reviewed: https://review.openstack.org/344819 Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=0eb0bd2cb0d8aa13db59d4a1879901470daa5d56 Submitter: Jenkins Branch:master commit 0eb0bd2cb0d8aa13db59d4a1879901470daa5d56 Author: jing.liuqing Date: Wed Jul 20 21:01:03 2016 +0800 [TrivialFix] Hide expand in angular table if we haven't setSummaryTemplateUrl Closes-Bug: #1604842 Change-Id: I5f2aa263834c8e45025e0a148ee54aa730dfef03 ** 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/1604842 Title: Should hide expand while we haven't setTemplateUrl Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Now if we haven't setSummaryTemplateUrl while register ResourceType, and if we visit the ResourceType angular table, it will always send a bunch of get requests. horizon/static/framework/widgets/table/hz-detail-row.directive.js in the file, while haven't setSummaryTemplateUrl, the templateUrl and angular.isUndefined(templateUrl) will be false, it won't use the default templateUrl(basePath + 'table/hz-detail-row.html') horizon/static/framework/widgets/table/hz-resource-table.controller.js and expand value should be the same with the boolean of templateUrl(ctrl.resourceType.summaryTemplateUrl) To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1604842/+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 1586268] Re: Unit test: self.assertNotEqual in unit.test_base.BaseTest.test_eq does not work in PY2
Reviewed: https://review.openstack.org/337445
Committed:
https://git.openstack.org/cgit/openstack/python-smaugclient/commit/?id=7b16de4908371cad5c1544551132eac34758315f
Submitter: Jenkins
Branch:master
commit 7b16de4908371cad5c1544551132eac34758315f
Author: yuyafei
Date: Tue Jul 5 15:37:56 2016 +0800
Add __ne__ built-in function
In Python 3 __ne__ by default delegates to __eq__ and inverts the
result, but in Python 2 they urge you to define __ne__ when you
define __eq__ for it to work properly [1].There are no implied
relationships among the comparison operators. The truth of x==y
does not imply that x!=y is false. Accordingly, when defining
__eq__(), one should also define __ne__() so that the operators
will behave as expected.
[1]https://docs.python.org/2/reference/datamodel.html#object.__ne__
Change-Id: Iae22095146e64081f362601665284b43d0056f48
Closes-Bug: #1586268
** Changed in: python-smaugclient
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/1586268
Title:
Unit test: self.assertNotEqual in unit.test_base.BaseTest.test_eq
does not work in PY2
Status in Ceilometer:
Fix Released
Status in daisycloud-core:
New
Status in heat:
New
Status in OpenStack Dashboard (Horizon):
New
Status in keystonemiddleware:
New
Status in neutron:
In Progress
Status in OpenStack Compute (nova):
In Progress
Status in python-barbicanclient:
New
Status in python-ceilometerclient:
Fix Released
Status in python-cinderclient:
Fix Released
Status in python-congressclient:
In Progress
Status in python-glanceclient:
In Progress
Status in python-heatclient:
Fix Released
Status in python-keystoneclient:
In Progress
Status in python-manilaclient:
New
Status in python-muranoclient:
Fix Released
Status in python-novaclient:
Fix Released
Status in python-smaugclient:
Fix Released
Status in python-troveclient:
In Progress
Status in tempest:
In Progress
Bug description:
Version: master(20160527)
In case cinderclient.tests.unit.test_base.BaseTest.test_eq
self.assertNotEqual does not work.
Class base.Resource defines __eq__() built-in function, but does not define
__ne__() built-in function, so self.assertEqual works but self.assertNotEqual
does not work at all in this test case.
steps:
1 Clone code of python-cinderclient from master.
2 Modify the case of unit test: cinderclient/tests/unit/test_base.py
line50--line62.
def test_eq(self):
# Two resources with same ID: never equal if their info is not equal
r1 = base.Resource(None, {'id': 1, 'name': 'hi'})
r2 = base.Resource(None, {'id': 1, 'name': 'hello'})
self.assertNotEqual(r1, r2)
# Two resources with same ID: equal if their info is equal
r1 = base.Resource(None, {'id': 1, 'name': 'hello'})
r2 = base.Resource(None, {'id': 1, 'name': 'hello'})
# self.assertEqual(r1, r2)
self.assertNotEqual(r1, r2)
# Two resoruces of different types: never equal
r1 = base.Resource(None, {'id': 1})
r2 = volumes.Volume(None, {'id': 1})
self.assertNotEqual(r1, r2)
# Two resources with no ID: equal if their info is equal
r1 = base.Resource(None, {'name': 'joe', 'age': 12})
r2 = base.Resource(None, {'name': 'joe', 'age': 12})
# self.assertEqual(r1, r2)
self.assertNotEqual(r1, r2)
Modify self.assertEqual(r1, r2) to self.assertNotEqual(r1, r2).
3 Run unit test, and return success.
After that, I make a test:
class Resource(object):
def __init__(self, person):
self.person = person
def __eq__(self, other):
return self.person == other.person
r1 = Resource("test")
r2 = Resource("test")
r3 = Resource("test_r3")
r4 = Resource("test_r4")
print r1 != r2
print r1 == r2
print r3 != r4
print r3 == r4
The result is :
True
True
True
False
Whether r1 is precisely the same to r2 or not, self.assertNotEqual(r1,
r2) return true.So I think self.assertNotEqual doesn't work at all in
python2 and should be modified.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1586268/+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 1605121] [NEW] duplicated test case exist in neutron repo and tempest repo
Public bug reported: according to https://etherpad.openstack.org/p/neutron-tempest-defork, some tests cases are moved from neutron to tempest. test cases "test_dhcp_stateful_fixedips_outrange" has been added in tempest while still exists in neutron repo. ** Affects: neutron Importance: Undecided Assignee: bin Yu (froyo-bin) Status: New ** Changed in: neutron Assignee: (unassigned) => bin Yu (froyo-bin) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1605121 Title: duplicated test case exist in neutron repo and tempest repo Status in neutron: New Bug description: according to https://etherpad.openstack.org/p/neutron-tempest-defork, some tests cases are moved from neutron to tempest. test cases "test_dhcp_stateful_fixedips_outrange" has been added in tempest while still exists in neutron repo. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1605121/+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 1595938] Re: npm-run-tests produces false positives
** Changed in: horizon Status: Fix Committed => 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/1595938 Title: npm-run-tests produces false positives Status in OpenStack Dashboard (Horizon): Fix Released Bug description: Although both unit tests and coverage check failed at http://logs.openstack.org/56/317456/15/check/gate-horizon-npm-run- test/95b7281/console.html#_2016-06-24_08_52_28_100671 the overall result of test job was positive. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1595938/+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 1605084] Re: [RFE] About page tab must be available on Dashboard of OpenStack
** Project changed: puppet-horizon => horizon -- 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/1605084 Title: [RFE] "About page" tab should be available on Dashboard of OpenStack Status in OpenStack Dashboard (Horizon): New Bug description: About page or tab is not available. It should be available as it will give the user which version it is using. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1605084/+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 1605084] [NEW] [RFE] About page tab must be available on Dashboard of OpenStack
You have been subscribed to a public bug: About page or tab is not available. It should be available as it will give the user which version it is using. ** Affects: horizon Importance: Undecided Status: New ** Tags: about page -- [RFE] About page tab must be available on Dashboard of OpenStack https://bugs.launchpad.net/bugs/1605084 You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). -- 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 1605090] [NEW] AssertionError: 0 == 0 : No IPv4 addresses found on gate-tempest-dsvm-neutron-linuxbridge
Public bug reported:
http://logs.openstack.org/73/345173/1/check/gate-tempest-dsvm-neutron-
linuxbridge/2730807/logs/testr_results.html.gz
Traceback (most recent call last):
File "tempest/test.py", line 106, in wrapper
return f(self, *func_args, **func_kwargs)
File "tempest/scenario/test_network_basic_ops.py", line 649, in
test_preserve_preexisting_port
self._setup_network_and_servers(boot_with_port=True)
File "tempest/scenario/test_network_basic_ops.py", line 123, in
_setup_network_and_servers
floating_ip = self.create_floating_ip(server)
File "tempest/scenario/manager.py", line 868, in create_floating_ip
port_id, ip4 = self._get_server_port_id_and_ip4(thing)
File "tempest/scenario/manager.py", line 847, in _get_server_port_id_and_ip4
"No IPv4 addresses found in: %s" % ports)
File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/case.py",
line 845, in assertNotEqual
raise self.failureException(msg)
AssertionError: 0 == 0 : No IPv4 addresses found in: [{u'updated_at':
u'2016-07-21T06:43:05', u'device_id': u'fc965435-3ac5-479c-a348-183c8067f016',
u'created_at': u'2016-07-21T06:42:56', u'tenant_id':
u'728b1d7ba78644738ab1c63b76a53718', u'extra_dhcp_opts': [], u'name':
u'tempest-port-quotatest-52370911', u'binding:vif_details': {u'port_filter':
True}, u'binding:host_id': u'ubuntu-trusty-ovh-gra1-2709194', u'device_owner':
u'compute:None', u'description': u'', u'security_groups':
[u'0bea87ad-beb8-4cf8-b627-6c7f406df3cf'], u'binding:vif_type': u'bridge',
u'mac_address': u'fa:16:3e:f0:d0:2d', u'binding:vnic_type': u'normal',
u'port_security_enabled': True, u'network_id':
u'ced37114-d483-48a4-a0e1-40c338839d54', u'allowed_address_pairs': [],
u'admin_state_up': True, u'id': u'f53c19ec-de16-440a-b1b0-e45e30cc891b',
u'fixed_ips': [{u'ip_address': u'10.100.0.6', u'subnet_id':
u'c5fb097f-6c95-4ce4-9584-de90e70e1dee'}], u'binding:profile': {}, u'status':
u'BUILD'}]
** Affects: neutron
Importance: High
Assignee: Kevin Benton (kevinbenton)
Status: Confirmed
** Tags: gate-failure
** Changed in: neutron
Status: New => Confirmed
** Changed in: neutron
Importance: Undecided => High
** Tags added: gate-failure
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1605090
Title:
AssertionError: 0 == 0 : No IPv4 addresses found on gate-tempest-dsvm-
neutron-linuxbridge
Status in neutron:
Confirmed
Bug description:
http://logs.openstack.org/73/345173/1/check/gate-tempest-dsvm-neutron-
linuxbridge/2730807/logs/testr_results.html.gz
Traceback (most recent call last):
File "tempest/test.py", line 106, in wrapper
return f(self, *func_args, **func_kwargs)
File "tempest/scenario/test_network_basic_ops.py", line 649, in
test_preserve_preexisting_port
self._setup_network_and_servers(boot_with_port=True)
File "tempest/scenario/test_network_basic_ops.py", line 123, in
_setup_network_and_servers
floating_ip = self.create_floating_ip(server)
File "tempest/scenario/manager.py", line 868, in create_floating_ip
port_id, ip4 = self._get_server_port_id_and_ip4(thing)
File "tempest/scenario/manager.py", line 847, in _get_server_port_id_and_ip4
"No IPv4 addresses found in: %s" % ports)
File
"/opt/stack/new/tempest/.tox/tempest/local/lib/python2.7/site-packages/unittest2/case.py",
line 845, in assertNotEqual
raise self.failureException(msg)
AssertionError: 0 == 0 : No IPv4 addresses found in: [{u'updated_at':
u'2016-07-21T06:43:05', u'device_id': u'fc965435-3ac5-479c-a348-183c8067f016',
u'created_at': u'2016-07-21T06:42:56', u'tenant_id':
u'728b1d7ba78644738ab1c63b76a53718', u'extra_dhcp_opts': [], u'name':
u'tempest-port-quotatest-52370911', u'binding:vif_details': {u'port_filter':
True}, u'binding:host_id': u'ubuntu-trusty-ovh-gra1-2709194', u'device_owner':
u'compute:None', u'description': u'', u'security_groups':
[u'0bea87ad-beb8-4cf8-b627-6c7f406df3cf'], u'binding:vif_type': u'bridge',
u'mac_address': u'fa:16:3e:f0:d0:2d', u'binding:vnic_type': u'normal',
u'port_security_enabled': True, u'network_id':
u'ced37114-d483-48a4-a0e1-40c338839d54', u'allowed_address_pairs': [],
u'admin_state_up': True, u'id': u'f53c19ec-de16-440a-b1b0-e45e30cc891b',
u'fixed_ips': [{u'ip_address': u'10.100.0.6', u'subnet_id':
u'c5fb097f-6c95-4ce4-9584-de90e70e1dee'}], u'binding:profile': {}, u'status':
u'BUILD'}]
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1605090/+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
