Public bug reported:
Hello everybody!
I have 2 controllers and 2 compute nodes. I disabled all the services on the
first controller and compute (nova service-disable), then I upgraded those
services to newton, executed `db sync` and started all the services on both
nodes.
After start the FIRST controller and compute nodes, I noticed, that nova-api on
my SECOND controller is down and the services don't work anymore.
nova-api log on the second controller:
ServiceTooOld: This service is older (v9) than the minimum (v15) version of the
rest of the deployment. Unable to continue.
And now i have a question:
How that upgrading process of the first half of my cluster affected on
the second half of my cluster?
(my goals: upgrade from mitaka to newton with minimal downtime, because
I have 2 controllers, I want to upgrade the first one and only then the
second one)
both server:
3.10.0-327.36.3.el7.x86_64
The first one (already newton):
openstack-nova-console-14.0.0-1.el7.noarch
openstack-nova-api-14.0.0-1.el7.noarch
openstack-nova-scheduler-14.0.0-1.el7.noarch
openstack-nova-common-14.0.0-1.el7.noarch
openstack-nova-novncproxy-14.0.0-1.el7.noarch
openstack-nova-conductor-14.0.0-1.el7.noarch
The second one (still mitaka):
openstack-nova-common-13.1.2-1.el7.noarch
openstack-nova-scheduler-13.1.2-1.el7.noarch
openstack-nova-conductor-13.1.2-1.el7.noarch
openstack-nova-api-13.1.2-1.el7.noarch
openstack-nova-console-13.1.2-1.el7.noarch
openstack-nova-novncproxy-13.1.2-1.el7.noarch
Thanks!
** Affects: nova
Importance: Undecided
Status: New
** Description changed:
Hello everybody!
- I have 2 controllers and 2 compute nodes. I disabled all the services on the
first controller and compute (nova service-disable), then I upgraded those
services to newton, executed `db sync` and start all the services on both
nodes.
+ I have 2 controllers and 2 compute nodes. I disabled all the services on the
first controller and compute (nova service-disable), then I upgraded those
services to newton, executed `db sync` and started all the services on both
nodes.
After start the FIRST controller and compute node, I noticed, that nova-api
on my SECOND controller is down and the services don't work anymore.
nova-api log on the second controller:
ServiceTooOld: This service is older (v9) than the minimum (v15) version of
the rest of the deployment. Unable to continue.
And now i have a question:
How that upgrading process of the first half of my cluster affected on
the second half of my cluster?
(my goals: upgrade from mitaka to newton with minimal downtime, because
I have 2 controllers, I want to upgrade the first one and only then the
second one.)
both server:
3.10.0-327.36.3.el7.x86_64
The first one (already newton):
openstack-nova-console-14.0.0-1.el7.noarch
openstack-nova-api-14.0.0-1.el7.noarch
openstack-nova-scheduler-14.0.0-1.el7.noarch
openstack-nova-common-14.0.0-1.el7.noarch
openstack-nova-novncproxy-14.0.0-1.el7.noarch
openstack-nova-conductor-14.0.0-1.el7.noarch
The second one (still mitaka):
openstack-nova-common-13.1.2-1.el7.noarch
openstack-nova-scheduler-13.1.2-1.el7.noarch
openstack-nova-conductor-13.1.2-1.el7.noarch
openstack-nova-api-13.1.2-1.el7.noarch
openstack-nova-console-13.1.2-1.el7.noarch
openstack-nova-novncproxy-13.1.2-1.el7.noarch
-
Thanks!
** Description changed:
Hello everybody!
I have 2 controllers and 2 compute nodes. I disabled all the services on the
first controller and compute (nova service-disable), then I upgraded those
services to newton, executed `db sync` and started all the services on both
nodes.
- After start the FIRST controller and compute node, I noticed, that nova-api
on my SECOND controller is down and the services don't work anymore.
+ After start the FIRST controller and compute nodes, I noticed, that nova-api
on my SECOND controller is down and the services don't work anymore.
nova-api log on the second controller:
ServiceTooOld: This service is older (v9) than the minimum (v15) version of
the rest of the deployment. Unable to continue.
And now i have a question:
How that upgrading process of the first half of my cluster affected on
the second half of my cluster?
(my goals: upgrade from mitaka to newton with minimal downtime, because
I have 2 controllers, I want to upgrade the first one and only then the
second one.)
both server:
3.10.0-327.36.3.el7.x86_64
The first one (already newton):
openstack-nova-console-14.0.0-1.el7.noarch
openstack-nova-api-14.0.0-1.el7.noarch
openstack-nova-scheduler-14.0.0-1.el7.noarch
openstack-nova-common-14.0.0-1.el7.noarch
openstack-nova-novncproxy-14.0.0-1.el7.noarch
openstack-nova-conductor-14.0.0-1.el7.noarch
The second one (still mitaka):
openstack-nova-common-13.1.2-1.el7.noarch
openstack-nova-scheduler-13.1.2-1.el7.noarch
openstack-nova-conductor-13.1.2-1.el7.noarch
openstack-nova-api-13.1.2-1.el7.noarch
openstack-nova-console-13.1.2-1.el7.noarch
openstack-nova-novncproxy-13.1.2-1.el7.noarch
Thanks!
** Description changed:
Hello everybody!
I have 2 controllers and 2 compute nodes. I disabled all the services on the
first controller and compute (nova service-disable), then I upgraded those
services to newton, executed `db sync` and started all the services on both
nodes.
After start the FIRST controller and compute nodes, I noticed, that nova-api
on my SECOND controller is down and the services don't work anymore.
nova-api log on the second controller:
ServiceTooOld: This service is older (v9) than the minimum (v15) version of
the rest of the deployment. Unable to continue.
And now i have a question:
How that upgrading process of the first half of my cluster affected on
the second half of my cluster?
(my goals: upgrade from mitaka to newton with minimal downtime, because
I have 2 controllers, I want to upgrade the first one and only then the
- second one.)
+ second one)
both server:
3.10.0-327.36.3.el7.x86_64
The first one (already newton):
openstack-nova-console-14.0.0-1.el7.noarch
openstack-nova-api-14.0.0-1.el7.noarch
openstack-nova-scheduler-14.0.0-1.el7.noarch
openstack-nova-common-14.0.0-1.el7.noarch
openstack-nova-novncproxy-14.0.0-1.el7.noarch
openstack-nova-conductor-14.0.0-1.el7.noarch
The second one (still mitaka):
openstack-nova-common-13.1.2-1.el7.noarch
openstack-nova-scheduler-13.1.2-1.el7.noarch
openstack-nova-conductor-13.1.2-1.el7.noarch
openstack-nova-api-13.1.2-1.el7.noarch
openstack-nova-console-13.1.2-1.el7.noarch
openstack-nova-novncproxy-13.1.2-1.el7.noarch
Thanks!
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1649263
Title:
Nova APi failed after upgrade mitaka->newton
Status in OpenStack Compute (nova):
New
Bug description:
Hello everybody!
I have 2 controllers and 2 compute nodes. I disabled all the services on the
first controller and compute (nova service-disable), then I upgraded those
services to newton, executed `db sync` and started all the services on both
nodes.
After start the FIRST controller and compute nodes, I noticed, that nova-api
on my SECOND controller is down and the services don't work anymore.
nova-api log on the second controller:
ServiceTooOld: This service is older (v9) than the minimum (v15) version of
the rest of the deployment. Unable to continue.
And now i have a question:
How that upgrading process of the first half of my cluster affected on
the second half of my cluster?
(my goals: upgrade from mitaka to newton with minimal downtime,
because I have 2 controllers, I want to upgrade the first one and only
then the second one)
both server:
3.10.0-327.36.3.el7.x86_64
The first one (already newton):
openstack-nova-console-14.0.0-1.el7.noarch
openstack-nova-api-14.0.0-1.el7.noarch
openstack-nova-scheduler-14.0.0-1.el7.noarch
openstack-nova-common-14.0.0-1.el7.noarch
openstack-nova-novncproxy-14.0.0-1.el7.noarch
openstack-nova-conductor-14.0.0-1.el7.noarch
The second one (still mitaka):
openstack-nova-common-13.1.2-1.el7.noarch
openstack-nova-scheduler-13.1.2-1.el7.noarch
openstack-nova-conductor-13.1.2-1.el7.noarch
openstack-nova-api-13.1.2-1.el7.noarch
openstack-nova-console-13.1.2-1.el7.noarch
openstack-nova-novncproxy-13.1.2-1.el7.noarch
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1649263/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
