[Yahoo-eng-team] [Bug 1801306] [NEW] Race conditions in neutron_tempest_plugin/scenario/test_security_groups.py
Public bug reported: I found a couple of race conditions in neutron-tempest-plugin affecting recular CI build when executing test jobs with neutron-tempest-plugin test suite. These race conditions are mostly because two test case wrongly modify default security group causing random failures in other scenario test cases or also failing themself. 1) Test case test_default_sec_grp_scenarios shouldn't change default security group rule at below lines: https://github.com/openstack/neutron-tempest-plugin/blob/cf38b77328dbf94f1323f96f68aa77124a6f4a7b/neutron_tempest_plugin/scenario/test_security_groups.py#L109-L112 This could caouse other tests to fail. Modifying default resources should be forbidden. There is no difference between default security group and another group, therefore the test makes no sense at all. Tests that do some changes on resources should create its own target resources. 2) Test case test_protocol_number_rule list for security groups and takes the first one, then it changes it at line https://github.com/openstack/neutron-tempest-plugin/blob/cf38b77328dbf94f1323f96f68aa77124a6f4a7b/neutron_tempest_plugin/scenario/test_security_groups.py#L147-L149 The problem here is that the first security group that is taken could be the default security group instead of the one created by the test. This would cause a failure in the same test and even worst in another test later. ** Affects: neutron Importance: Undecided Assignee: Federico Ressi (fressi-redhat) Status: In Progress ** Changed in: neutron Assignee: (unassigned) => Federico Ressi (fressi-redhat) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1801306 Title: Race conditions in neutron_tempest_plugin/scenario/test_security_groups.py Status in neutron: In Progress Bug description: I found a couple of race conditions in neutron-tempest-plugin affecting recular CI build when executing test jobs with neutron- tempest-plugin test suite. These race conditions are mostly because two test case wrongly modify default security group causing random failures in other scenario test cases or also failing themself. 1) Test case test_default_sec_grp_scenarios shouldn't change default security group rule at below lines: https://github.com/openstack/neutron-tempest-plugin/blob/cf38b77328dbf94f1323f96f68aa77124a6f4a7b/neutron_tempest_plugin/scenario/test_security_groups.py#L109-L112 This could caouse other tests to fail. Modifying default resources should be forbidden. There is no difference between default security group and another group, therefore the test makes no sense at all. Tests that do some changes on resources should create its own target resources. 2) Test case test_protocol_number_rule list for security groups and takes the first one, then it changes it at line https://github.com/openstack/neutron-tempest-plugin/blob/cf38b77328dbf94f1323f96f68aa77124a6f4a7b/neutron_tempest_plugin/scenario/test_security_groups.py#L147-L149 The problem here is that the first security group that is taken could be the default security group instead of the one created by the test. This would cause a failure in the same test and even worst in another test later. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1801306/+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 1794450] Re: When creating a server instance with an IPv4 and an IPv6 addresses, the IPv6 is not assigned
I was finally able to ping between two VMs using IPv6 subnet by doing
below:
1) Add below parameters when creating IPv6 subnet:
{
'enable_dhcp': true,
'ipv6_ra_mode':'slaac',
'ipv6_address_mode':'slaac',
# ...
}
2) Add below rule to security group assigned to VMs ports:
{
'protocol': 'icmp',
'direction': 'ingress',
'remote_ip_prefix': '::/0',
'ethertype': 'IPv6'
}
Cheers for your help.
** Changed in: nova
Status: New => Invalid
** Changed in: neutron
Status: New => 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/1794450
Title:
When creating a server instance with an IPv4 and an IPv6 addresses,
the IPv6 is not assigned
Status in neutron:
Invalid
Status in OpenStack Compute (nova):
Invalid
Bug description:
This is expected behaviour:
Given:
G1) A tenant network with two subnets (one for IPV4 and one for IPv6)
G2) A port attached to the network with two fixed IPs (one for IPv4 and one
for IPv6)
G3) A server VM instance created with the port with its two fixed IPs
When:
W1) Server instance is booted
Then:
T1) Server instance receives from cloud init the IPv4 address correctly on
the first interface and set it up
T2) Server instance receives from cloud init the IPv6 address correctly on
the first interface and set it up
The observed behavior differs in T2:
T2) Server instance receives from cloud init the wrong IPv6 on the first
interface and set it up the wrong IP
These are the IPs of the server when it is created:
"addresses": {
"tempest-loginable-619471459": [
{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:81:72:35",
"version": 4, "addr": "10.1.0.35", "OS-EXT-IPS:type": "fixed"},
{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:81:72:35",
"version": 6, "addr": "2003:0:0:2::2", "OS-EXT-IPS:type": "fixed"}
]
}
These are the actual IPs assigned to the VM:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1400 qdisc pfifo_fast state UP
group default qlen 1000
link/ether fa:16:3e:81:72:35 brd ff:ff:ff:ff:ff:ff
inet 10.1.0.35/28 brd 10.1.0.47 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe81:7235/64 scope link
valid_lft forever preferred_lft forever
These traces has been extracted from the instance log:
[ 331.846900] cloud-init[1014]: Cloud-init v. 18.2 running 'init' at Tue, 25
Sep 2018 19:13:18 +. Up 262.77 seconds.
[ 331.986855] cloud-init[1014]: ci-info:
+++Net device
info
[ 332.026098] cloud-init[1014]: ci-info:
++--+--+-+---+---+
[ 332.052076] cloud-init[1014]: ci-info: | Device | Up |
Address| Mask | Scope | Hw-Address|
[ 332.117348] cloud-init[1014]: ci-info:
++--+--+-+---+---+
[ 332.137446] cloud-init[1014]: ci-info: | ens3 | True |
10.1.0.35 | 255.255.255.240 | . | fa:16:3e:81:72:35 |
[ 332.166719] cloud-init[1014]: ci-info: | ens3 | True |
fe80::f816:3eff:fe81:7235/64 |.| link | fa:16:3e:81:72:35 |
[ 332.197524] cloud-init[1014]: ci-info: | lo | True |
127.0.0.1 |255.0.0.0| . | . |
[ 332.223152] cloud-init[1014]: ci-info: | lo | True |
::1/128|.| host | . |
[ 332.258243] cloud-init[1014]: ci-info:
++--+--+-+---+---+
[ 332.282758] cloud-init[1014]: ci-info:
+++Route IPv4 info+++
[ 332.318255] cloud-init[1014]: ci-info:
+---+-+---+-+---+---+
[ 332.343051] cloud-init[1014]: ci-info: | Route | Destination |
Gateway | Genmask | Interface | Flags |
[ 332.369270] cloud-init[1014]: ci-info:
+---+-+---+-+---+---+
[ 332.394200] cloud-init[1014]: ci-info: | 0 | 0.0.0.0 |
10.1.0.33 | 0.0.0.0 |ens3 | UG |
[ 332.418340] cloud-init[1014]: ci-info: | 1 |10.1.0.32|
0.0.0.0 | 255.255.255.240 |ens3 | U |
[ 332.442581] cloud-init[1014]: ci-info: | 2
[Yahoo-eng-team] [Bug 1794450] [NEW] When creating a server instance with an IPv4 and an IPv6 addresses, the IPv6 is not assigned
Public bug reported:
This is expected behaviour:
Given:
G1) A tenant network with two subnets (one for IPV4 and one for IPv6)
G2) A port attached to the network with two fixed IPs (one for IPv4 and one
for IPv6)
G3) A server VM instance created with the port with its two fixed IPs
When:
W1) Server instance is booted
Then:
T1) Server instance receives from cloud init the IPv4 address correctly on
the first interface and set it up
T2) Server instance receives from cloud init the IPv6 address correctly on
the first interface and set it up
The observed behavior differs in T2:
T2) Server instance receives from cloud init the wrong IPv6 on the first
interface and set it up the wrong IP
These are the IPs of the server when it is created:
"addresses": {
"tempest-loginable-619471459": [
{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:81:72:35",
"version": 4, "addr": "10.1.0.35", "OS-EXT-IPS:type": "fixed"},
{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:81:72:35",
"version": 6, "addr": "2003:0:0:2::2", "OS-EXT-IPS:type": "fixed"}
]
}
These are the actual IPs assigned to the VM:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1400 qdisc pfifo_fast state UP
group default qlen 1000
link/ether fa:16:3e:81:72:35 brd ff:ff:ff:ff:ff:ff
inet 10.1.0.35/28 brd 10.1.0.47 scope global ens3
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe81:7235/64 scope link
valid_lft forever preferred_lft forever
These traces has been extracted from the instance log:
[ 331.846900] cloud-init[1014]: Cloud-init v. 18.2 running 'init' at Tue, 25
Sep 2018 19:13:18 +. Up 262.77 seconds.
[ 331.986855] cloud-init[1014]: ci-info:
+++Net device
info
[ 332.026098] cloud-init[1014]: ci-info:
++--+--+-+---+---+
[ 332.052076] cloud-init[1014]: ci-info: | Device | Up |
Address| Mask | Scope | Hw-Address|
[ 332.117348] cloud-init[1014]: ci-info:
++--+--+-+---+---+
[ 332.137446] cloud-init[1014]: ci-info: | ens3 | True |
10.1.0.35 | 255.255.255.240 | . | fa:16:3e:81:72:35 |
[ 332.166719] cloud-init[1014]: ci-info: | ens3 | True |
fe80::f816:3eff:fe81:7235/64 |.| link | fa:16:3e:81:72:35 |
[ 332.197524] cloud-init[1014]: ci-info: | lo | True |
127.0.0.1 |255.0.0.0| . | . |
[ 332.223152] cloud-init[1014]: ci-info: | lo | True |
::1/128|.| host | . |
[ 332.258243] cloud-init[1014]: ci-info:
++--+--+-+---+---+
[ 332.282758] cloud-init[1014]: ci-info:
+++Route IPv4 info+++
[ 332.318255] cloud-init[1014]: ci-info:
+---+-+---+-+---+---+
[ 332.343051] cloud-init[1014]: ci-info: | Route | Destination |
Gateway | Genmask | Interface | Flags |
[ 332.369270] cloud-init[1014]: ci-info:
+---+-+---+-+---+---+
[ 332.394200] cloud-init[1014]: ci-info: | 0 | 0.0.0.0 |
10.1.0.33 | 0.0.0.0 |ens3 | UG |
[ 332.418340] cloud-init[1014]: ci-info: | 1 |10.1.0.32|
0.0.0.0 | 255.255.255.240 |ens3 | U |
[ 332.442581] cloud-init[1014]: ci-info: | 2 | 169.254.169.254 |
10.1.0.33 | 255.255.255.255 |ens3 | UGH |
[ 332.463209] cloud-init[1014]: ci-info:
+---+-+---+-+---+---+
This bug has been see when writing this test case for neutron-tempest-plugin:
https://review.openstack.org/#/c/586040/21
https://review.openstack.org/#/c/586040/21/neutron_tempest_plugin/scenario/test_loginable.py
The logs of the problem can be found here:
http://logs.openstack.org/40/586040/21/check/neutron-tempest-plugin-scenario-linuxbridge/28228b0/
http://logs.openstack.org/40/586040/21/check/neutron-tempest-plugin-scenario-linuxbridge/28228b0/testr_results.html.gz
** Affects: neutron
Importance: Undecided
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Also affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, whi
[Yahoo-eng-team] [Bug 1540873] Re: Error: Service n-xvnc is not running
I tested, it fixed it. ** No longer affects: devstack -- 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/1540873 Title: Error: Service n-xvnc is not running Status in OpenStack Compute (nova): Fix Released Bug description: When stacking I am getting below error many times since a pair of days: 2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running' 2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running 2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']' 2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can be found with screen, with ./rejoin-stack.sh' 2016-02-02 11:07:08,278 | + local exitcode=0 2016-02-02 11:07:08,278 | [Call Trace] 2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check 2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die 2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 More details about the above errors can be found with screen, with ./rejoin-stack.sh 2016-02-02 11:07:08,279 | Error on exit This is new. I am not sure witch repository between devstack, nova and neutron introduced it. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1540873/+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 1540873] Re: Error: Service n-xvnc is not running
I suspect the problem appeared when the change was merged: https://review.openstack.org/#/c/235398/ This should fix it: https://review.openstack.org/#/c/274889/ ** No longer affects: neutron -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1540873 Title: Error: Service n-xvnc is not running Status in devstack: New Status in OpenStack Compute (nova): New Bug description: When stacking I am getting below error many times since a pair of days: 2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running' 2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running 2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']' 2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can be found with screen, with ./rejoin-stack.sh' 2016-02-02 11:07:08,278 | + local exitcode=0 2016-02-02 11:07:08,278 | [Call Trace] 2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check 2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die 2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 More details about the above errors can be found with screen, with ./rejoin-stack.sh 2016-02-02 11:07:08,279 | Error on exit This is new. I am not sure witch repository between devstack, nova and neutron introduced it. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1540873/+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 1540873] Re: Error: Service n-xvnc is not running
** No longer affects: tempest -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1540873 Title: Error: Service n-xvnc is not running Status in devstack: New Status in neutron: New Status in OpenStack Compute (nova): New Bug description: When stacking I am getting below error many times since a pair of days: 2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running' 2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running 2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']' 2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can be found with screen, with ./rejoin-stack.sh' 2016-02-02 11:07:08,278 | + local exitcode=0 2016-02-02 11:07:08,278 | [Call Trace] 2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check 2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die 2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 More details about the above errors can be found with screen, with ./rejoin-stack.sh 2016-02-02 11:07:08,279 | Error on exit This is new. I am not sure witch repository between devstack, nova and neutron introduced it. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1540873/+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 1540873] [NEW] Error: Service n-xvnc is not running
Public bug reported: When stacking I am getting below error many times since a pair of days: 2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running' 2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running 2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']' 2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can be found with screen, with ./rejoin-stack.sh' 2016-02-02 11:07:08,278 | + local exitcode=0 2016-02-02 11:07:08,278 | [Call Trace] 2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check 2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die 2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 More details about the above errors can be found with screen, with ./rejoin-stack.sh 2016-02-02 11:07:08,279 | Error on exit This is new. I am not sure witch repository between devstack, nova and neutron introduced it. ** Affects: devstack Importance: Undecided Status: New ** Affects: neutron Importance: Undecided Status: New ** Affects: nova Importance: Undecided Status: New ** Affects: tempest Importance: Undecided Status: New ** Also affects: nova Importance: Undecided Status: New ** Also affects: neutron Importance: Undecided Status: New ** Also affects: tempest Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova). https://bugs.launchpad.net/bugs/1540873 Title: Error: Service n-xvnc is not running Status in devstack: New Status in neutron: New Status in OpenStack Compute (nova): New Status in tempest: New Bug description: When stacking I am getting below error many times since a pair of days: 2016-02-02 11:07:08,277 | + echo 'Error: Service n-xvnc is not running' 2016-02-02 11:07:08,278 | Error: Service n-xvnc is not running 2016-02-02 11:07:08,278 | + '[' -n /opt/stack/status/stack/n-xvnc.failure ']' 2016-02-02 11:07:08,278 | + die 1642 'More details about the above errors can be found with screen, with ./rejoin-stack.sh' 2016-02-02 11:07:08,278 | + local exitcode=0 2016-02-02 11:07:08,278 | [Call Trace] 2016-02-02 11:07:08,278 | ./stack.sh:1353:service_check 2016-02-02 11:07:08,279 | /opt/stack/devstack/functions-common:1642:die 2016-02-02 11:07:08,279 | [ERROR] /opt/stack/devstack/functions-common:1642 More details about the above errors can be found with screen, with ./rejoin-stack.sh 2016-02-02 11:07:08,279 | Error on exit This is new. I am not sure witch repository between devstack, nova and neutron introduced it. To manage notifications about this bug go to: https://bugs.launchpad.net/devstack/+bug/1540873/+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 1537377] Re: sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table
It looks like one of the last change in neutron fixed it. Probably one
of these two:
https://review.openstack.org/#/c/271918/
https://review.openstack.org/#/c/272082/
** Changed in: neutron
Status: New => Fix Released
** Changed in: networking-odl
Status: New => 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/1537377
Title:
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such
table
Status in networking-odl:
Fix Released
Status in neutron:
Fix Released
Bug description:
When running too in project networking-old I most of tests py27 fail
with errors like the one below:
2016-01-23 16:49:16,515 | {2}
networking_odl.tests.unit.ml2.test_driver.TestODLShim.test_update_port_postcommit
[14.353879s] ... FAILED
2016-01-23 16:49:16,515 |
2016-01-23 16:49:16,516 | Captured traceback:
2016-01-23 16:49:16,516 | ~~~
2016-01-23 16:49:16,516 | Traceback (most recent call last):
2016-01-23 16:49:16,516 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/fixtures/fixture.py",
line 125, in cleanUp
2016-01-23 16:49:16,516 | return
self._cleanups(raise_errors=raise_first)
2016-01-23 16:49:16,516 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/fixtures/callmany.py",
line 88, in __call__
2016-01-23 16:49:16,517 | reraise(error[0], error[1], error[2])
2016-01-23 16:49:16,517 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/fixtures/callmany.py",
line 82, in __call__
2016-01-23 16:49:16,517 | cleanup(*args, **kwargs)
2016-01-23 16:49:16,517 | File
"/opt/stack/networking-odl/.tox/py27/src/neutron/neutron/tests/unit/testlib_api.py",
line 76, in clear_tables
2016-01-23 16:49:16,517 | conn.execute(table.delete())
2016-01-23 16:49:16,517 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 914, in execute
2016-01-23 16:49:16,518 | return meth(self, multiparams, params)
2016-01-23 16:49:16,518 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/sql/elements.py",
line 323, in _execute_on_connection
2016-01-23 16:49:16,518 | return
connection._execute_clauseelement(self, multiparams, params)
2016-01-23 16:49:16,518 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1010, in _execute_clauseelement
2016-01-23 16:49:16,518 | compiled_sql, distilled_params
2016-01-23 16:49:16,519 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1146, in _execute_context
2016-01-23 16:49:16,519 | context)
2016-01-23 16:49:16,519 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1337, in _handle_dbapi_exception
2016-01-23 16:49:16,519 | util.raise_from_cause(newraise, exc_info)
2016-01-23 16:49:16,519 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py",
line 200, in raise_from_cause
2016-01-23 16:49:16,519 | reraise(type(exception), exception,
tb=exc_tb)
2016-01-23 16:49:16,520 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1139, in _execute_context
2016-01-23 16:49:16,520 | context)
2016-01-23 16:49:16,520 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py",
line 450, in do_execute
2016-01-23 16:49:16,520 | cursor.execute(statement, parameters)
2016-01-23 16:49:16,520 | sqlalchemy.exc.OperationalError:
(sqlite3.OperationalError) no such table: floatingipdnses [SQL: u'DELETE FROM
floatingipdnses']
2016-01-23 16:49:16,521 |
2016-01-23 16:49:16,521 |
2016-01-23 16:49:16,521 | Captured pythonlogging:
2016-01-23 16:49:16,521 | ~~~
2016-01-23 16:49:16,521 | WARNING [neutron.agent.securitygroups_rpc]
Driver configuration doesn't match with enable_security_group
2016-01-23 16:49:16,521 | WARNING [neutron.api.extensions] Extension dvr
not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
extraroute not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
flavors not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
ext-gw-mode not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
l3-ha not supported by any of loaded
[Yahoo-eng-team] [Bug 1537377] Re: sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table
** Summary changed:
- Extension path 'neutron/tests/unit/extensions' doesn't exist!
+ sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such table
** Description changed:
- When running too I errors like the one below:
+ When running too in project networking-old I most of tests py27 fail
+ with errors like the one below:
2016-01-23 16:49:16,515 | {2}
networking_odl.tests.unit.ml2.test_driver.TestODLShim.test_update_port_postcommit
[14.353879s] ... FAILED
- 2016-01-23 16:49:16,515 |
+ 2016-01-23 16:49:16,515 |
2016-01-23 16:49:16,516 | Captured traceback:
2016-01-23 16:49:16,516 | ~~~
2016-01-23 16:49:16,516 | Traceback (most recent call last):
2016-01-23 16:49:16,516 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/fixtures/fixture.py",
line 125, in cleanUp
2016-01-23 16:49:16,516 | return
self._cleanups(raise_errors=raise_first)
2016-01-23 16:49:16,516 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/fixtures/callmany.py",
line 88, in __call__
2016-01-23 16:49:16,517 | reraise(error[0], error[1], error[2])
2016-01-23 16:49:16,517 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/fixtures/callmany.py",
line 82, in __call__
2016-01-23 16:49:16,517 | cleanup(*args, **kwargs)
2016-01-23 16:49:16,517 | File
"/opt/stack/networking-odl/.tox/py27/src/neutron/neutron/tests/unit/testlib_api.py",
line 76, in clear_tables
2016-01-23 16:49:16,517 | conn.execute(table.delete())
2016-01-23 16:49:16,517 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 914, in execute
2016-01-23 16:49:16,518 | return meth(self, multiparams, params)
2016-01-23 16:49:16,518 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/sql/elements.py",
line 323, in _execute_on_connection
2016-01-23 16:49:16,518 | return
connection._execute_clauseelement(self, multiparams, params)
2016-01-23 16:49:16,518 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1010, in _execute_clauseelement
2016-01-23 16:49:16,518 | compiled_sql, distilled_params
2016-01-23 16:49:16,519 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1146, in _execute_context
2016-01-23 16:49:16,519 | context)
2016-01-23 16:49:16,519 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1337, in _handle_dbapi_exception
2016-01-23 16:49:16,519 | util.raise_from_cause(newraise, exc_info)
2016-01-23 16:49:16,519 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py",
line 200, in raise_from_cause
2016-01-23 16:49:16,519 | reraise(type(exception), exception,
tb=exc_tb)
2016-01-23 16:49:16,520 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py",
line 1139, in _execute_context
2016-01-23 16:49:16,520 | context)
2016-01-23 16:49:16,520 | File
"/opt/stack/networking-odl/.tox/py27/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py",
line 450, in do_execute
2016-01-23 16:49:16,520 | cursor.execute(statement, parameters)
2016-01-23 16:49:16,520 | sqlalchemy.exc.OperationalError:
(sqlite3.OperationalError) no such table: floatingipdnses [SQL: u'DELETE FROM
floatingipdnses']
- 2016-01-23 16:49:16,521 |
- 2016-01-23 16:49:16,521 |
+ 2016-01-23 16:49:16,521 |
+ 2016-01-23 16:49:16,521 |
2016-01-23 16:49:16,521 | Captured pythonlogging:
2016-01-23 16:49:16,521 | ~~~
2016-01-23 16:49:16,521 | WARNING [neutron.agent.securitygroups_rpc]
Driver configuration doesn't match with enable_security_group
2016-01-23 16:49:16,521 | WARNING [neutron.api.extensions] Extension dvr
not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
extraroute not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
flavors not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
ext-gw-mode not supported by any of loaded plugins
2016-01-23 16:49:16,522 | WARNING [neutron.api.extensions] Extension
l3-ha not supported by any of loaded plugins
2016-01-23 16:49:16,523 | WARNING [neutron.api.extensions] Extension
l3_agent_scheduler not supported by any of loaded plugins
2016-01-23 16:49:16,523 | WARNING [neutron.api.extensions] Extension
metering not supported by any of loaded plugins
2016-01-23 16:49:16,523 | WARNING [n
[Yahoo-eng-team] [Bug 1526710] Re: NotSupportedError: MySQL cannot rename indexes
** Changed in: glance
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1526710
Title:
NotSupportedError: MySQL cannot rename indexes
Status in Glance:
Invalid
Bug description:
When stacking with branch stable/liberty of devstack, on a control host I had
below error.
I am using a clean Ubuntu 14.04 LTS just updated.
2015-12-16 07:50:32.262 | 2015-12-16 07:50:32.262 INFO migrate.versioning.api
[-] 0 -> 1...
2015-12-16 07:50:32.272 | 2015-12-16 07:50:32.272 INFO
glance.db.sqlalchemy.migrate_repo.schema [-] creating table images
2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api
[-] 1 -> 2...
2015-12-16 07:50:32.303 | 2015-12-16 07:50:32.303 INFO
glance.db.sqlalchemy.migrate_repo.schema [-] creating table image_properties
2015-12-16 07:50:32.350 | 2015-12-16 07:50:32.350 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.351 | 2015-12-16 07:50:32.351 INFO migrate.versioning.api
[-] 2 -> 3...
2015-12-16 07:50:32.374 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.376 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api
[-] 3 -> 4...
2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api
[-] 4 -> 5...
2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.398 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.399 INFO migrate.versioning.api
[-] 5 -> 6...
2015-12-16 07:50:32.404 | 2015-12-16 07:50:32.404 CRITICAL glance [-]
NotSupportedError: MySQL cannot rename indexes
2015-12-16 07:50:32.406 |
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance Traceback
(most recent call last):
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/bin/glance-manage", line 10, in
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance
sys.exit(main())
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 314, in main
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance return
CONF.command.action_fn()
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 170, in sync
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance
CONF.command.current_version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 115, in sync
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line
79, in db_sync
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance migration
= versioning_api.upgrade(engine, repository, version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186,
in upgrade
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance return
_migrate(url, repository, version, upgrade=True, err=err, **opts)
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance File
"", line 2, in _migrate
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py",
line 160, in with_engine
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance return
f(*a, **kw)
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 366,
in _migrate
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance
schema.runchange(ver, change, changeset.step)
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 93,
in runchange
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance
change.run(self.engine, step)
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/script/py.py", line
148, in run
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance
script_func(engine)
2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions/006_key_to_name.py",
line 96, in upgrade
2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance
index.rename('ix_image_properties_image_id_name')
2015-12-16 07:50:32.413 | 2015
[Yahoo-eng-team] [Bug 1530338] [NEW] ImportError: No module named enabled
Public bug reported: When deploying horizon using devstack I realised that one python module that is actually provided and listed in git repo, it is also marked to be ignored in .gitignored file. $ git ls-files openstack_dashboard/local/enabled/ openstack_dashboard/local/enabled/_50_settings.py.example openstack_dashboard/local/enabled/__init__.py openstack_dashboard.local.enabled is imported as in shown below log and therefore its __init__.py file should not be ignored as here: https://github.com/openstack/horizon/commit/28e14b71418bd73d67aee190a1106ec49c4b558e Log file of the failure I got: 2015-12-31 13:00:16.041 | Traceback (most recent call last): 2015-12-31 13:00:16.042 | File "/opt/stack/horizon/manage.py", line 23, in 2015-12-31 13:00:16.042 | execute_from_command_line(sys.argv) 2015-12-31 13:00:16.043 | File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 354, in execute_from_command_line 2015-12-31 13:00:16.043 | utility.execute() 2015-12-31 13:00:16.043 | File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 303, in execute 2015-12-31 13:00:16.044 | settings.INSTALLED_APPS 2015-12-31 13:00:16.044 | File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 48, in __getattr__ 2015-12-31 13:00:16.045 | self._setup(name) 2015-12-31 13:00:16.045 | File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 44, in _setup 2015-12-31 13:00:16.046 | self._wrapped = Settings(settings_module) 2015-12-31 13:00:16.046 | File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 92, in __init__ 2015-12-31 13:00:16.046 | mod = importlib.import_module(self.SETTINGS_MODULE) 2015-12-31 13:00:16.047 | File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module 2015-12-31 13:00:16.047 | __import__(name) 2015-12-31 13:00:16.048 | File "/opt/stack/horizon/openstack_dashboard/settings.py", line 346, in 2015-12-31 13:00:16.048 | import openstack_dashboard.local.enabled 2015-12-31 13:00:16.049 | ImportError: No module named enabled ** Affects: horizon Importance: Undecided Assignee: Federico Ressi (federico-ressi-9) Status: In Progress -- 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/1530338 Title: ImportError: No module named enabled Status in OpenStack Dashboard (Horizon): In Progress Bug description: When deploying horizon using devstack I realised that one python module that is actually provided and listed in git repo, it is also marked to be ignored in .gitignored file. $ git ls-files openstack_dashboard/local/enabled/ openstack_dashboard/local/enabled/_50_settings.py.example openstack_dashboard/local/enabled/__init__.py openstack_dashboard.local.enabled is imported as in shown below log and therefore its __init__.py file should not be ignored as here: https://github.com/openstack/horizon/commit/28e14b71418bd73d67aee190a1106ec49c4b558e Log file of the failure I got: 2015-12-31 13:00:16.041 | Traceback (most recent call last): 2015-12-31 13:00:16.042 | File "/opt/stack/horizon/manage.py", line 23, in 2015-12-31 13:00:16.042 | execute_from_command_line(sys.argv) 2015-12-31 13:00:16.043 | File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 354, in execute_from_command_line 2015-12-31 13:00:16.043 | utility.execute() 2015-12-31 13:00:16.043 | File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 303, in execute 2015-12-31 13:00:16.044 | settings.INSTALLED_APPS 2015-12-31 13:00:16.044 | File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 48, in __getattr__ 2015-12-31 13:00:16.045 | self._setup(name) 2015-12-31 13:00:16.045 | File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 44, in _setup 2015-12-31 13:00:16.046 | self._wrapped = Settings(settings_module) 2015-12-31 13:00:16.046 | File "/usr/local/lib/python2.7/dist-packages/django/conf/__init__.py", line 92, in __init__ 2015-12-31 13:00:16.046 | mod = importlib.import_module(self.SETTINGS_MODULE) 2015-12-31 13:00:16.047 | File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module 2015-12-31 13:00:16.047 | __import__(name) 2015-12-31 13:00:16.048 | File "/opt/stack/horizon/openstack_dashboard/settings.py", line 346, in 2015-12-31 13:00:16.048 | import openstack_dashboard.local.enabled 2015-12-31 13:00:16.049 | ImportError: No module named enabled To manage notifications a
[Yahoo-eng-team] [Bug 1526710] Re: NotSupportedError: MySQL cannot rename indexes
** No longer affects: devstack
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1526710
Title:
NotSupportedError: MySQL cannot rename indexes
Status in Glance:
New
Bug description:
When stacking with branch stable/liberty of devstack, on a control host I had
below error.
I am using a clean Ubuntu 14.04 LTS just updated.
2015-12-16 07:50:32.262 | 2015-12-16 07:50:32.262 INFO migrate.versioning.api
[-] 0 -> 1...
2015-12-16 07:50:32.272 | 2015-12-16 07:50:32.272 INFO
glance.db.sqlalchemy.migrate_repo.schema [-] creating table images
2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api
[-] 1 -> 2...
2015-12-16 07:50:32.303 | 2015-12-16 07:50:32.303 INFO
glance.db.sqlalchemy.migrate_repo.schema [-] creating table image_properties
2015-12-16 07:50:32.350 | 2015-12-16 07:50:32.350 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.351 | 2015-12-16 07:50:32.351 INFO migrate.versioning.api
[-] 2 -> 3...
2015-12-16 07:50:32.374 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.376 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api
[-] 3 -> 4...
2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api
[-] 4 -> 5...
2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.398 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.399 INFO migrate.versioning.api
[-] 5 -> 6...
2015-12-16 07:50:32.404 | 2015-12-16 07:50:32.404 CRITICAL glance [-]
NotSupportedError: MySQL cannot rename indexes
2015-12-16 07:50:32.406 |
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance Traceback
(most recent call last):
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/bin/glance-manage", line 10, in
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance
sys.exit(main())
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 314, in main
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance return
CONF.command.action_fn()
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 170, in sync
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance
CONF.command.current_version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 115, in sync
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line
79, in db_sync
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance migration
= versioning_api.upgrade(engine, repository, version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186,
in upgrade
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance return
_migrate(url, repository, version, upgrade=True, err=err, **opts)
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance File
"", line 2, in _migrate
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py",
line 160, in with_engine
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance return
f(*a, **kw)
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 366,
in _migrate
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance
schema.runchange(ver, change, changeset.step)
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 93,
in runchange
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance
change.run(self.engine, step)
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/script/py.py", line
148, in run
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance
script_func(engine)
2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions/006_key_to_name.py",
line 96, in upgrade
2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance
index.rename('ix_image_properties_image_id_name')
2015-12-16 07:50:32.413 | 2015-12-16 07:50:32.404 TRACE glance
[Yahoo-eng-team] [Bug 1526710] [NEW] NotSupportedError: MySQL cannot rename indexes
Public bug reported:
When stacking with branch stable/liberty of devstack, on a control host I had
below error.
I am using a clean Ubuntu 14.04 LTS just updated.
2015-12-16 07:50:32.262 | 2015-12-16 07:50:32.262 INFO migrate.versioning.api
[-] 0 -> 1...
2015-12-16 07:50:32.272 | 2015-12-16 07:50:32.272 INFO
glance.db.sqlalchemy.migrate_repo.schema [-] creating table images
2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.293 | 2015-12-16 07:50:32.293 INFO migrate.versioning.api
[-] 1 -> 2...
2015-12-16 07:50:32.303 | 2015-12-16 07:50:32.303 INFO
glance.db.sqlalchemy.migrate_repo.schema [-] creating table image_properties
2015-12-16 07:50:32.350 | 2015-12-16 07:50:32.350 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.351 | 2015-12-16 07:50:32.351 INFO migrate.versioning.api
[-] 2 -> 3...
2015-12-16 07:50:32.374 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.376 | 2015-12-16 07:50:32.374 INFO migrate.versioning.api
[-] 3 -> 4...
2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.387 | 2015-12-16 07:50:32.387 INFO migrate.versioning.api
[-] 4 -> 5...
2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.398 INFO migrate.versioning.api
[-] done
2015-12-16 07:50:32.399 | 2015-12-16 07:50:32.399 INFO migrate.versioning.api
[-] 5 -> 6...
2015-12-16 07:50:32.404 | 2015-12-16 07:50:32.404 CRITICAL glance [-]
NotSupportedError: MySQL cannot rename indexes
2015-12-16 07:50:32.406 |
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance Traceback (most
recent call last):
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/bin/glance-manage", line 10, in
2015-12-16 07:50:32.406 | 2015-12-16 07:50:32.404 TRACE glance
sys.exit(main())
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 314, in main
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance return
CONF.command.action_fn()
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 170, in sync
2015-12-16 07:50:32.407 | 2015-12-16 07:50:32.404 TRACE glance
CONF.command.current_version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/cmd/manage.py", line 115, in sync
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/oslo_db/sqlalchemy/migration.py", line
79, in db_sync
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance migration =
versioning_api.upgrade(engine, repository, version)
2015-12-16 07:50:32.408 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 186,
in upgrade
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance return
_migrate(url, repository, version, upgrade=True, err=err, **opts)
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance File
"", line 2, in _migrate
2015-12-16 07:50:32.409 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/util/__init__.py",
line 160, in with_engine
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance return f(*a,
**kw)
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/api.py", line 366,
in _migrate
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance
schema.runchange(ver, change, changeset.step)
2015-12-16 07:50:32.410 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/schema.py", line 93,
in runchange
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance
change.run(self.engine, step)
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/versioning/script/py.py", line
148, in run
2015-12-16 07:50:32.411 | 2015-12-16 07:50:32.404 TRACE glance
script_func(engine)
2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance File
"/opt/stack/glance/glance/db/sqlalchemy/migrate_repo/versions/006_key_to_name.py",
line 96, in upgrade
2015-12-16 07:50:32.412 | 2015-12-16 07:50:32.404 TRACE glance
index.rename('ix_image_properties_image_id_name')
2015-12-16 07:50:32.413 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/migrate/changeset/schema.py", line 688,
in rename
2015-12-16 07:50:32.413 | 2015-12-16 07:50:32.404 TRACE glance
engine._run_visitor(visitorcallable, self, connection, **kwargs)
2015-12-16 07:50:32.413 | 2015-12-16 07:50:32.404 TRACE glance File
"/usr/local/lib/python2.7/dist-packages/sqlalchemy/engi
[Yahoo-eng-team] [Bug 1523716] Re: oslo.utils upgrade breaks unit tests
** Also affects: neutron Importance: Undecided Status: New ** Also affects: networking-odl 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/1523716 Title: oslo.utils upgrade breaks unit tests Status in Ceilometer: New Status in networking-odl: New Status in neutron: New Status in oslo.utils: In Progress Bug description: Upgraded oslo.utils (3.1.0) is breaking ceilometer unit tests: https://jenkins07.openstack.org/job/gate-ceilometer- python34/897/console Stack Trace: 2015-12-07 20:17:19.296 | __import__(module_str) 2015-12-07 20:17:19.296 | File "ceilometer/notification.py", line 24, in 2015-12-07 20:17:19.296 | from ceilometer import coordination 2015-12-07 20:17:19.296 | File "ceilometer/coordination.py", line 20, in 2015-12-07 20:17:19.297 | import tooz.coordination 2015-12-07 20:17:19.297 | File "/home/jenkins/workspace/gate-ceilometer-python27/.tox/py27/local/lib/python2.7/site-packages/tooz/coordination.py", line 21, in 2015-12-07 20:17:19.297 | from oslo_utils import netutils 2015-12-07 20:17:19.297 | File "/home/jenkins/workspace/gate-ceilometer-python27/.tox/py27/local/lib/python2.7/site-packages/oslo_utils/netutils.py", line 25, in 2015-12-07 20:17:19.297 | import netifaces 2015-12-07 20:17:19.297 | ImportError: No module named netifaces To manage notifications about this bug go to: https://bugs.launchpad.net/ceilometer/+bug/1523716/+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
