N -> O upgrade: wrong nova placement parameters.
Bug #1684058 reported by
Sofer Athlan-Guyot
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Sofer Athlan-Guyot |
Bug Description
Hi,
during the upgrade we configure the compute node in batch (by default) and set some needed options for ocata. On of them in the placement configuration, see [1].
Unfortunatly, the configuration is wrong and we get:
ERROR oslo_service.
in the logs.
That seems to lead to an orchestration problem where the nova-compute service cannot be safely restarted.
I wonder if the restart [2] is needed as the packages are not yet updated at this point and we still have newton nova-compute.
Changed in tripleo: | |
assignee: | nobody → Sofer Athlan-Guyot (sofer-athlan-guyot) |
status: | Confirmed → In Progress |
tags: | added: upgrade |
To post a comment you must log in.
12:40 < chem> marios: https:/ /bugs.launchpad .net/tripleo/ +bug/1684058, I'm not sure we should restart the nova-compute at all /github. com/openstack/ tripleo- heat-templates/ blob/299b9f5323 77a3a0c16ba9cb4 fe92c637fc38eeb /puppet/ major_upgrade_ steps.j2. yaml#L63 which happens on
nova- compute nodes before the controller ansible upgrade
these things on nova node first
12:41 < chem> marios: it's still newton at that moment and don't need the new parameter or do I miss something ?
12:43 < marios> chem: well its meant to be for picking up that placement config i think owalsh was helping us with that at the time.. owalsh we are talking about
https:/
12:43 < marios> chem: i think it was 'in order to allow nova compute to talk to the upgraded nova and other services on controllers after we upgrade _those_ we should set