Thank you guys,
in fact I was following wrongly the procedure: I had to stamp with the
old conf file, but I was using the new one.
Now it works well!
Alvise
On 02/02/2015 08:54 PM, Kris G. Lindgren wrote:
That¹s what I was thinking as well. I looked at the install guide and it
says to set the stamp using your existing config, then run the db upgrade
using the new config - then do a db migration after db upgrade. I thought
I had read some where that you had to migrate first then upgrade. We were
already running ml2 - so I didn't have to do that step.
____________________________________________
Kris Lindgren
Senior Linux Systems Engineer
GoDaddy, LLC.
On 2/2/15, 12:46 PM, "Jesse Keating" <j...@bluebox.net> wrote:
On 2/2/15 5:56 AM, Alvise Dorigo wrote:
For neutron I got a problem at the very last step:
neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file
/etc/neutron/plugins/ml2/ml2_conf.ini upgrade icehouse
[...]
sqlalchemy.exc.ProgrammingError: (ProgrammingError) (1146, "Table
'neutron.ml2_port_bindings' doesn't exist") "ALTER TABLE
ml2_port_bindings ADD COLUMN vnic_type VARCHAR(64) DEFAULT 'normal' NOT
NULL" ()
Did I miss something which would have created that missing table ?
Can someone provide some help ?
Were you already using ml2 plugin before upgrading?
--
-jlk
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
