Openstack Fresh Install Train - Neutron

asked 2020-06-30 20:38:33 -0500

EddyNava gravatar image

updated 2020-06-30 20:41:12 -0500

I was following the deployment guide for Train installation - I was able to install Keystone, Glance, Placement, Nova, Heat and Horizon, but when following the guide to install Neutron at the point of populating the database Mysql lost connection.

su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \
  --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron

oslo_db.exception.DBError: (pymysql.err.InternalError) (1832, "Cannot change column 'network_id': used in a foreign key constraint 'subnets_ibfk_1'") [SQL: 'ALTER TABLE subnets MODIFY network_id VARCHAR(36) NOT NULL'] (Background on this error at: http://sqlalche.me/e/2j85)

I found this article https://ask.openstack.org/en/question...

So I upgraded from mariadb 10.1 to mariadb 10.4 and did the upgrade of the databases and got everything to work, then tried again to do the neutron population

su -s /bin/sh -c "neutron-db-manage --config-file /etc/neutron/neutron.conf \
  --config-file /etc/neutron/plugins/ml2/ml2_conf.ini upgrade head" neutron

I got another error within mysql

jul  1 01:18:17 openstack-controller1 mysqld[19040]: This could be because you hit a bug. It is also possible that this binary
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: or one of the libraries it was linked against is corrupt, improperly built,
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: or misconfigured. This error can also be caused by malfunctioning hardware.
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: To report this bug, see https://mariadb.com/kb/en/reporting-bugs
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: We will try our best to scrape up some info that will hopefully help
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: diagnose the problem, but since we have already crashed,
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: something is definitely wrong and this may fail.
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: Server version: 10.4.13-MariaDB-1:10.4.13+maria~bionic-log
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: key_buffer_size=134217728
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: read_buffer_size=1073741824
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: max_used_connections=187
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: max_threads=35002
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: thread_count=196
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: It is possible that mysqld could use up to
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 36846621323 K  bytes of memory
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: Hope that’s ok; if not, decrease some variables in the equation.
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: Thread pointer: 0x7f00a4000c08
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: Attempting backtrace. You can use the following information to find out
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: where mysqld died. If you see no messages after this, something went
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: terribly wrong...
Jul  1 01:18:17 openstack-controller1 mysqld[19040]: stack_bottom = 0x7f0218ba4dd8 thread_stack 0x49000
Jul  1 01 ...
(more)
edit retag flag offensive close merge delete

Comments

To me it sounds as if your package versions don't match, try to make your environment consistent.

eblock gravatar imageeblock ( 2020-07-01 02:01:12 -0500 )edit