Devstack - yet more problems on install
Following on from the last email about br-ex causing everything to baulk, I manually created the br-ex using brctl addbr br-ex and got past that hurdle. But now falling over with another one ERROR oslo_db.sqlalchemy.exc_filters InternalError: (1071, u'Specified key was too long; max key length is 767 bytes') ERROR oslo_db.sqlalchemy.exc_filters Error during database migration: (pymysql.err.InternalError) (1071, u'Specified key was too long; max key length is 767 bytes') [SQL: u'\nALTER TABLE quota_usages CHANGE COLUMN resource resource VARCHAR(300)'] (Background on this error at: http://sqlalche.me/e/2j85) Base OS is CentOS 7.5. I've found this which looks similar - https://review.openstack.org/#/c/626146/ - but I've no idea how to apply it to my Devstack installation. I'd appreciate some assistance please. David
But now falling over with another one
ERROR oslo_db.sqlalchemy.exc_filters InternalError: (1071, u'Specified key was too long; max key length is 767 bytes') ERROR oslo_db.sqlalchemy.exc_filters Error during database migration: (pymysql.err.InternalError) (1071, u'Specified key was too long; max key length is 767 bytes') [SQL: u'\nALTER TABLE quota_usages CHANGE COLUMN resource resource VARCHAR(300)'] (Background on this error at: http://sqlalche.me/e/2j85)
Base OS is CentOS 7.5.
I've found this which looks similar - https://review.openstack.org/#/c/626146/ - but I've no idea how to apply it to my Devstack installation.
Yep, you found the right patch. That is a known issue right now and we should hopefully have the fix merged very shortly. In the meantime, you could add this to your local.conf: CINDER_BRANCH=refs/changes/46/626146/3 With that, devstack will pull down that version of the code and you should be able to get by this failure until we merge the fix. As of this moment, there is just a pep8 error that is preventing that from merging. That will not impact the ability to actually run the code. Once that merges you can take that line out of the local.conf file to just get the current code from master. Hope that helps. Sean
Thanks, but yet another different error now. Seems to be this: .ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] No datapath_id on bridge br-int Agent terminated!: RuntimeError: No datapath_id on bridge br-int Tearing my hair out here. David Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", l ine 331, in iter Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib raise retry_exc.reraise() Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", l ine 168, in reraise Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib raise self Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib RetryError: RetryError[<Future at 0x7fd1031b6250 state=finished r eturned list>] Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.plugin s.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] No datapath_id on bridge b r-int Agent terminated!: RuntimeError: No datapath_id on bridge br-int Dec 20 11:34:28 localhost systemd[1]: devstack@q-agt.service: main process exite d, code=exited, status=1/FAILURE Dec 20 11:34:28 localhost systemd[1]: Unit devstack@q-agt.service entered failed state. Dec 20 11:34:28 localhost systemd[1]: devstack@q-agt.service failed. +functions-common:service_check:1 exit_trap +./stack.sh:exit_trap:522 local r=3 ++./stack.sh:exit_trap:523 jobs -p +./stack.sh:exit_trap:523 jobs= +./stack.sh:exit_trap:526 [[ -n '' ]] +./stack.sh:exit_trap:532 '[' -f /tmp/tmp.YgbuTdLJS4 ']' +./stack.sh:exit_trap:533 rm /tmp/tmp.YgbuTdLJS4 +./stack.sh:exit_trap:537 kill_spinner +./stack.sh:kill_spinner:432 '[' '!' -z '' ']' +./stack.sh:exit_trap:539 [[ 3 -ne 0 ]] +./stack.sh:exit_trap:540 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:542 type -p generate-subunit +./stack.sh:exit_trap:543 generate-subunit 1545304664 1078 fail +./stack.sh:exit_trap:545 [[ -z /opt/stack/logs/screen ]] +./stack.sh:exit_trap:548 /home/stack/devstack/tools/worlddump. -----Original Message----- From: Sean McGinnis <sean.mcginnis@gmx.com> Sent: 19 December 2018 22:02 To: Lake, David (PG/R - Elec Electronic Eng) <d.lake@surrey.ac.uk> Cc: openstack@lists.openstack.org; openstack-dev@lists.openstack.org Subject: Re: Devstack - yet more problems on install
But now falling over with another one
ERROR oslo_db.sqlalchemy.exc_filters InternalError: (1071, u'Specified key was too long; max key length is 767 bytes') ERROR oslo_db.sqlalchemy.exc_filters Error during database migration: (pymysql.err.InternalError) (1071, u'Specified key was too long; max key length is 767 bytes') [SQL: u'\nALTER TABLE quota_usages CHANGE COLUMN resource resource VARCHAR(300)'] (Background on this error at: http://sqlalche.me/e/2j85)
Base OS is CentOS 7.5.
I've found this which looks similar - https://review.openstack.org/#/c/626146/ - but I've no idea how to apply it to my Devstack installation.
Yep, you found the right patch. That is a known issue right now and we should hopefully have the fix merged very shortly. In the meantime, you could add this to your local.conf: CINDER_BRANCH=refs/changes/46/626146/3 With that, devstack will pull down that version of the code and you should be able to get by this failure until we merge the fix. As of this moment, there is just a pep8 error that is preventing that from merging. That will not impact the ability to actually run the code. Once that merges you can take that line out of the local.conf file to just get the current code from master. Hope that helps. Sean
On 12/20/18 8:16 AM, d.lake@surrey.ac.uk wrote:
Thanks, but yet another different error now. Seems to be this:
.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] No datapath_id on bridge br-int Agent terminated!: RuntimeError: No datapath_id on bridge br-int
Tearing my hair out here.
What other customizations have you done in local.conf? I created a 'stack' yesterday (without any extra changes in local.conf) and didn't see the error you describe. This command should print the datapatch information fyi: sudo ovs-appctl dpif/show -Brian
Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", l ine 331, in iter Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib raise retry_exc.reraise() Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib File "/usr/lib/python2.7/site-packages/tenacity/__init__.py", l ine 168, in reraise Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib raise self Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib RetryError: RetryError[<Future at 0x7fd1031b6250 state=finished r eturned list>] Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.agent. common.ovs_lib Dec 20 11:34:28 localhost neutron-openvswitch-agent[70126]: ERROR neutron.plugin s.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-] No datapath_id on bridge b r-int Agent terminated!: RuntimeError: No datapath_id on bridge br-int Dec 20 11:34:28 localhost systemd[1]: devstack@q-agt.service: main process exite d, code=exited, status=1/FAILURE Dec 20 11:34:28 localhost systemd[1]: Unit devstack@q-agt.service entered failed state. Dec 20 11:34:28 localhost systemd[1]: devstack@q-agt.service failed. +functions-common:service_check:1 exit_trap +./stack.sh:exit_trap:522 local r=3 ++./stack.sh:exit_trap:523 jobs -p +./stack.sh:exit_trap:523 jobs= +./stack.sh:exit_trap:526 [[ -n '' ]] +./stack.sh:exit_trap:532 '[' -f /tmp/tmp.YgbuTdLJS4 ']' +./stack.sh:exit_trap:533 rm /tmp/tmp.YgbuTdLJS4 +./stack.sh:exit_trap:537 kill_spinner +./stack.sh:kill_spinner:432 '[' '!' -z '' ']' +./stack.sh:exit_trap:539 [[ 3 -ne 0 ]] +./stack.sh:exit_trap:540 echo 'Error on exit' Error on exit +./stack.sh:exit_trap:542 type -p generate-subunit +./stack.sh:exit_trap:543 generate-subunit 1545304664 1078 fail +./stack.sh:exit_trap:545 [[ -z /opt/stack/logs/screen ]] +./stack.sh:exit_trap:548 /home/stack/devstack/tools/worlddump.
-----Original Message----- From: Sean McGinnis <sean.mcginnis@gmx.com> Sent: 19 December 2018 22:02 To: Lake, David (PG/R - Elec Electronic Eng) <d.lake@surrey.ac.uk> Cc: openstack@lists.openstack.org; openstack-dev@lists.openstack.org Subject: Re: Devstack - yet more problems on install
But now falling over with another one
ERROR oslo_db.sqlalchemy.exc_filters InternalError: (1071, u'Specified key was too long; max key length is 767 bytes') ERROR oslo_db.sqlalchemy.exc_filters Error during database migration: (pymysql.err.InternalError) (1071, u'Specified key was too long; max key length is 767 bytes') [SQL: u'\nALTER TABLE quota_usages CHANGE COLUMN resource resource VARCHAR(300)'] (Background on this error at: http://sqlalche.me/e/2j85)
Base OS is CentOS 7.5.
I've found this which looks similar - https://review.openstack.org/#/c/626146/ - but I've no idea how to apply it to my Devstack installation.
Yep, you found the right patch. That is a known issue right now and we should hopefully have the fix merged very shortly.
In the meantime, you could add this to your local.conf:
CINDER_BRANCH=refs/changes/46/626146/3
With that, devstack will pull down that version of the code and you should be able to get by this failure until we merge the fix. As of this moment, there is just a pep8 error that is preventing that from merging. That will not impact the ability to actually run the code.
Once that merges you can take that line out of the local.conf file to just get the current code from master.
Hope that helps.
Sean
participants (3)
-
Brian Haley
-
d.lake＠surrey.ac.uk
-
Sean McGinnis