upps :-) thx again.
So, as conclusion after any yum upgrade we need to run packstack again and do a neutron-db-manage like:[root controller ~(keystone_admin)]# neutron-db-manage --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugin.ini upgrade headINFO [alembic.migration] Context impl MySQLImpl.INFO [alembic.migration] Will assume non-transactional DDL.INFO [alembic.migration] Running upgrade juno -> c00e3802ef7, empty messageand openstack-service restartright?Now I've a small problem with the vnc console, it doesn't work anymore, in the vnc proxy log I see:2014-10-12 06:08:46.583 23108 INFO nova.console.websocketproxy [req-83b79c9e-9f2f-467e-87fe-b73d589b9532 None] connecting to: <controller-ip>:59002014-10-12 06:08:56.170 23106 INFO nova.console.websocketproxy [-] <vpn-server-ip>: ignoring empty handshakecirros needs a long time to come up, due to "failed to get instance-id of datasource": ???
cirros-ds 'net' up at 60.74checking http://169.254.169.254/2009-04-04/instance-id failed 1/20: up 60.75. request failed failed 2/20: up 65.76. request failed ....failed 19/20: up 122.76. request failed failed 20/20: up 125.76. request failed failed to read iid from metadata. tried 20 no results found for mode=net. up 128.76. searched: nocloud configdrive ec2 failed to get instance-id of datasource Starting dropbear sshd: generating rsa key... generating dsa key... OK === system information === Platform: Fedora Project OpenStack NovaTested that with CentOS image too, it seems to be a routing problem:cloud-init: 2014-10-17 09:39:57,539 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [119/120s]: request error [[Errno 113] No route to host] cloud-init: 2014-10-17 09:40:02,544 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.254/2009-04-04/meta-data/instance-id'] after 124 seconds cloud-init: 2014-10-17 09:40:05,552 - url_helper.py[WARNING]: Calling 'http://184.108.40.206//latest/meta-data/instance-id' failed [3/120s]: request error [[Errno 113] No route to host]loud-init: 2014-10-17 09:42:00,666 - url_helper.py[WARNING]: Calling 'http://220.127.116.11//latest/meta-data/instance-id' failed [118/120s]: request error [[Errno 113] No route to host] cloud-init: 2014-10-17 09:42:05,672 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://18.104.22.168//latest/meta-data/instance-id'] after 123 seconds cloud-init: Cloud-init v. 0.7.5 running 'modules:config' at Fri, 17 Oct 2014 09:42:07 +0000. Up 323.40 seconds.Thanks!-ArashOn Fri, Oct 17, 2014 at 10:38 AM, Ihar Hrachyshka <ihrachys redhat com> wrote:-----BEGIN PGP SIGNED MESSAGE-----
You've missed 'head' at the end of the command.
On 17/10/14 10:36, Arash Kaffamanesh wrote:
> .. wenn I run: [root controller~(keystone_admin)]#
> neutron-db-manage --config-file /etc/neutron/neutron.conf
> --config-file /etc/neutron/plugin.ini upgrade
> I'm getting:
> You must provide a revision or relative delta
> any ideas?
> Thx -Arash
> On Fri, Oct 17, 2014 at 10:34 AM, Arash Kaffamanesh
> <ak cloudssky com <mailto:ak cloudssky com>> wrote:
> Ihar, thanks, much appreciated. When I run:
> On Fri, Oct 17, 2014 at 10:13 AM, Ihar Hrachyshka
> <ihrachys redhat com <mailto:ihrachys redhat com>> wrote:
> On 16/10/14 18:12, Arash Kaffamanesh wrote:
>> Just let you know, I did a yum upgrade on controller and compute
>> nodes and the packages was upgraded to rc2 and rc3 packages,
>> after that neutron didn't work on controller and I'd only to
>> re-run packstack and reboot my instances and I was more than
>> lucky :-)
> I suspect this is because you need to run db migration steps after
> each update till the final release, otherwise you loose some db
> migration steps, and service crashes.
> # neutron-db-manage \ --config-file /etc/neutron/neutron.conf \
> --config-file /etc/neutron/plugin.ini upgrade head
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
-----END PGP SIGNATURE-----