Hi Andy, On 15.09.2017 14:14, Andy Wojnarek wrote:
I did not run the database migration, I was running through the OpenSuSE Implementation guide for Ocata – since there isn’t one for Pike yet:
Not sure, but I think the new guide is at https://docs.openstack.org/install-guide/ .
There isn’t anything there for a neutron db sync during the controller portion of the guide. How does one get involved with OpenSuSE OpenStack documentation? I’d like to contribute.
At the end of every openstack doc, there is a bug report symbol to report issues. I guess a good start for new documentation contributors is https://docs.openstack.org/contributor-guide/ Best, Tom
Thanks for the link, I’ll run the DB migration/sync.
Thanks, Andrew Wojnarek | Sr. Systems Engineer | ATS Group, LLC mobile 717.856.6901 | andy.wojnarek@TheATSGroup.com Galileo Performance Explorer Blog <http://galileosuite.com/blog/> Offers Deep Insights for Server/Storage Systems
On 9/15/17, 5:20 AM, "Thomas Bechtold" <tbechtold@suse.com> wrote:
Hi Andy,
On 15.09.2017 04:25, Andy Wojnarek wrote: > I’m trying to submit a bug, but on https://bugzilla.opensuse.org/, but there does not seem to be a component for OpenStack under any of the products.
Indeed. I requested a new component and it should be available in the next 24 hours.
> I’m testing a fresh install of Pike on 42.3, and I’m getting neutron database errors: > > 2017-09-14 22:17:47.431 24052 ERROR oslo_messaging.rpc.server DBError: (pymysql.err.InternalError) (1054, u"Unknown column 'subnets.project_id' in 'field list'") [SQL: u'SELECT subnets.project_id AS subnets_project_id, subnets.id AS subnets_id, subnets.name AS subnets_name, subnets.network_id AS subnets_network_id, subnets.segment_id AS subnets_segment_id, subnets.subnetpool_id AS subnets_subnetpool_id, subnets.ip_version AS subnets_ip_version, subnets.cidr AS subnets_cidr, subnets.gateway_ip AS subnets_gateway_ip, subnets.enable_dhcp AS subnets_enable_dhcp, subnets.ipv6_ra_mode AS subnets_ipv6_ra_mode, subnets.ipv6_address_mode AS subnets_ipv6_address_mode, subnets.standard_attr_id AS subnets_standard_attr_id, standardattributes_1.id AS standardattributes_1_id, standardattributes_1.resource_type AS standardattributes_1_resource_type, standardattributes_1.description AS standardattributes_1_description, standardattributes_1.revision_number AS standardattributes_1_revision_number, standardattributes_1.created_at AS standardattributes_1_created_at, standardattributes_1.updated_at AS standardattributes_1_updated_at, subnetpools_1.project_id AS subnetpools_1_project_id, subnetpools_1.id AS subnetpools_1_id, subnetpools_1.name AS subnetpools_1_name, subnetpools_1.ip_version AS subnetpools_1_ip_version, subnetpools_1.default_prefixlen AS subnetpools_1_default_prefixlen, subnetpools_1.min_prefixlen AS subnetpools_1_min_prefixlen, subnetpools_1.max_prefixlen AS subnetpools_1_max_prefixlen, subnetpools_1.shared AS subnetpools_1_shared, subnetpools_1.is_default AS subnetpools_1_is_default, subnetpools_1.default_quota AS subnetpools_1_default_quota, subnetpools_1.hash AS subnetpools_1_hash, subnetpools_1.address_scope_id AS subnetpools_1_address_scope_id, subnetpools_1.standard_attr_id AS subnetpools_1_standard_attr_id, standardattributes_2.id AS standardattributes_2_id, standardattributes_2.resource_type AS standardattributes_2_resource_type, standardattributes_2.description AS standardattributes_2_description, standardattributes_2.revision_number AS standardattributes_2_revision_number, standardattributes_2.created_at AS standardattributes_2_created_at, standardattributes_2.updated_at AS standardattributes_2_updated_at \nFROM subnets LEFT OUTER JOIN subnetpools AS subnetpools_1 ON subnets.subnetpool_id = subnetpools_1.id LEFT OUTER JOIN standardattributes AS standardattributes_1 ON standardattributes_1.id = subnetpools_1.standard_attr_id LEFT OUTER JOIN standardattributes AS standardattributes_2 ON standardattributes_2.id = subnets.standard_attr_id'] > > I confirmed there is no column ‘project_id’ in the subnets table inside the neutron database.
Did you sync the neutron database[1]? We do the sync also during a neutron-server restart[2] via systemd but ignore failures here. Maybe you started neutron-server before you configured the database string in neutron.conf ?
[1] https://docs.openstack.org/mitaka/networking-guide/migration-database.html [2] https://build.opensuse.org/package/view_file/Cloud:OpenStack:Pike/openstack-...
Best,
Tom N�����r��y隊Z)z{.��%��~�{.n�+������Ǩ�?�r��i�m��0��ޙ�������?rZ.w�0�����Ǩ�