Open Stack

Hi Eugene,

I did have an upgrade issue on my end
that could well have impacted the DB migration.

Just after upgrade and when the Ubuntu packed migration scripts ran
the database connection in neutron.conf pointed to a local sqllite
location.  So first thing I did was correct that to point at the
correct MySQL location then:

neutron-db-manage --config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
stamp grizzly
neutron-db-manage --config-file /etc/neutron/neutron.conf
--config-file /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
upgrade

If the pools.status_description column is meant to exist I should
probably do a clean install (rather than upgrade) in my test
environment and diff the database schemas...

Thanks,
-Jon

On Mon, Jan 13, 2014 at 9:04 AM, Eugene Nikanorov
<enikanorov at mirantis.com> wrote:
> Hi Jonathan,
>
> It really looks as migration issue. I wonder how did you perform the
> migration.
> Devstack usually runs migration during the setup and everything works fine
> with the current code.
>
> Could you provide more details about how you run the migration.
>
> Thanks,
> Eugene.
>
>
>
> On Mon, Jan 13, 2014 at 2:46 AM, Jonathan Proulx <jon at jonproulx.com> wrote:
>>
>> Hi all,
>>
>> neutron-lbass-agent is failing with:
>>
>> neutron.service OperationalError: (OperationalError) (1054, "Unknown
>> column 'pools.status_description' in 'field list'") 'SELECT
>> pools.tenant_id AS pools_tenant_id, pools.id AS pools_id, pools.status
>> AS pools_status, pools.status_description AS pools_status_description,
>> pools.vip_id AS pools_vip_id, pools.name AS pools_name,
>> pools.description AS pools_description, pools.subnet_id AS
>> pools_subnet_id, pools.protocol AS pools_protocol, pools.lb_method AS
>> pools_lb_method, pools.admin_state_up AS pools_admin_state_up,
>> providerresourceassociations_1.provider_name AS
>> providerresourceassociations_1_provider_name,
>> providerresourceassociations_1.resource_id AS
>> providerresourceassociations_1_resource_id \nFROM pools LEFT OUTER
>> JOIN providerresourceassociations AS providerresourceassociations_1 ON
>> pools.id = providerresourceassociations_1.resource_id' ()
>>
>> If I run the query by hand without the offending
>> pools.status_description column it works.
>>
>> This may indicate something went wrong with the database migration,
>> but as the "pools" table didn't exist in Grizzly and Havana neutron is
>> otherwise working it may also be a bug in the lbaas agent.
>>
>> shall I just modify the table to have that column and go on with my
>> life, or is this likely a deeper issue?
>>
>> Thanks,
>> -Jon
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to     : openstack at lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>