Description of problem:
Controller upgrade fails at the post deployment steps if there is a "-" at the heat template resource definitions;
PLAY [Server Post Deployments] *************************************************
TASK [include] *****************************************************************
Thursday 31 October 2019 16:13:58 +0300 (0:00:00.276) 0:30:40.821 ******
included: /var/lib/mistral/eebc1388-af6b-465d-9b39-8d2bba8507b4/Controller/deployments.yaml for cauqctr02, cauqctr03, cauqctr01
included: /var/lib/mistral/eebc1388-af6b-465d-9b39-8d2bba8507b4/Controller/deployments.yaml for cauqctr02, cauqctr03, cauqctr01
included: /var/lib/mistral/eebc1388-af6b-465d-9b39-8d2bba8507b4/Controller/deployments.yaml for cauqctr02, cauqctr03, cauqctr01
TASK [Lookup deployment UUID] **************************************************
Thursday 31 October 2019 16:13:58 +0300 (0:00:00.536) 0:30:41.357 ******
fatal: [cauqctr02]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"}
fatal: [cauqctr03]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"}
fatal: [cauqctr01]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"}
Version-Release number of selected component (if applicable):
OSP10z12 --> OSP13z7 FFU
How reproducible:
Always
Steps to Reproduce:
1. Put a "-" at a definition in the Extra config post file
OS::TripleO::NodeExtraConfigPost: ../post-deploy/post-deploy.yaml
Ex:
ExtraDeployments-sriov: <<<<<<<<<<<<<<<<<<<<<<<<< here
type: OS::Heat::StructuredDeployments
properties:
servers: {get_param: servers}
config: {get_resource: ExtraConfigSriov}
# Do this on CREATE/UPDATE (which is actually the default)
actions: ['CREATE', 'UPDATE']
2. Start the controller upgrade with the command "openstack overcloud upgrade run --nodes Controller --skip-tags validation"
Actual results:
TASK [Lookup deployment UUID] **************************************************
Thursday 31 October 2019 16:13:58 +0300 (0:00:00.536) 0:30:41.357 ******
fatal: [cauqctr02]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"}
fatal: [cauqctr03]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"}
fatal: [cauqctr01]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n
Expected results:
Upgrade of the controller proceeds without any error
Additional info:
Workaround: Remove the "-" at the definition and start the FFU process from scratch
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:0760
Description of problem: Controller upgrade fails at the post deployment steps if there is a "-" at the heat template resource definitions; PLAY [Server Post Deployments] ************************************************* TASK [include] ***************************************************************** Thursday 31 October 2019 16:13:58 +0300 (0:00:00.276) 0:30:40.821 ****** included: /var/lib/mistral/eebc1388-af6b-465d-9b39-8d2bba8507b4/Controller/deployments.yaml for cauqctr02, cauqctr03, cauqctr01 included: /var/lib/mistral/eebc1388-af6b-465d-9b39-8d2bba8507b4/Controller/deployments.yaml for cauqctr02, cauqctr03, cauqctr01 included: /var/lib/mistral/eebc1388-af6b-465d-9b39-8d2bba8507b4/Controller/deployments.yaml for cauqctr02, cauqctr03, cauqctr01 TASK [Lookup deployment UUID] ************************************************** Thursday 31 October 2019 16:13:58 +0300 (0:00:00.536) 0:30:41.357 ****** fatal: [cauqctr02]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"} fatal: [cauqctr03]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"} fatal: [cauqctr01]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"} Version-Release number of selected component (if applicable): OSP10z12 --> OSP13z7 FFU How reproducible: Always Steps to Reproduce: 1. Put a "-" at a definition in the Extra config post file OS::TripleO::NodeExtraConfigPost: ../post-deploy/post-deploy.yaml Ex: ExtraDeployments-sriov: <<<<<<<<<<<<<<<<<<<<<<<<< here type: OS::Heat::StructuredDeployments properties: servers: {get_param: servers} config: {get_resource: ExtraConfigSriov} # Do this on CREATE/UPDATE (which is actually the default) actions: ['CREATE', 'UPDATE'] 2. Start the controller upgrade with the command "openstack overcloud upgrade run --nodes Controller --skip-tags validation" Actual results: TASK [Lookup deployment UUID] ************************************************** Thursday 31 October 2019 16:13:58 +0300 (0:00:00.536) 0:30:41.357 ****** fatal: [cauqctr02]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"} fatal: [cauqctr03]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n ^"} fatal: [cauqctr01]: FAILED! => {"msg": "JMESPathError in json_query filter plugin:\nUnexpected token: -2: Parse error at column 16, token \"-2\" (NUMBER), for expression:\n\"ExtraDeployments-2.id\"\n Expected results: Upgrade of the controller proceeds without any error Additional info: Workaround: Remove the "-" at the definition and start the FFU process from scratch