ocata->pike upgrade CI - ansible fails with "no action detected in task"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Jiří Stránský |
Bug Description
This is an error we hit in upgrades CI but not when executing upgrades locally:
2017-04-11 16:20:33 | 2017-04-11 16:20:01Z [overcloud]: UPDATE_FAILED resources.
2017-04-11 16:20:33 |
2017-04-11 16:20:33 | Stack overcloud UPDATE_FAILED
2017-04-11 16:20:33 |
2017-04-11 16:20:33 | overcloud.
2017-04-11 16:20:33 | resource_type: OS::Heat:
2017-04-11 16:20:33 | physical_
2017-04-11 16:20:33 | status: CREATE_FAILED
2017-04-11 16:20:33 | status_reason: |
2017-04-11 16:20:33 | Error: resources[0]: Deployment to server failed: deploy_status_code : Deployment exited with non-zero status code: 4
2017-04-11 16:20:33 | deploy_stdout: |
2017-04-11 16:20:33 |
2017-04-11 16:20:33 | deploy_stderr: |
2017-04-11 16:20:33 | ERROR! no action detected in task. This often indicates a misspelled module name, or incorrect module path.
2017-04-11 16:20:33 | ++ onerror
2017-04-11 16:20:33 | ++ echo 'Command failed'
2017-04-11 16:20:33 | Command failed
2017-04-11 16:20:33 | ++ openstack stack resource list overcloud
2017-04-11 16:20:37 | ++ openstack stack failures list --long overcloud
2017-04-11 16:21:07 | ++ exit 1
Changed in tripleo: | |
milestone: | none → pike-2 |
Based on discussion with Artem Hrechanychenko and further investigation, this problem is likely caused by the fact that all multinode jobs deploy pacemaker environments.
The problem is probably twofold:
1) We're likely missing Pacemaker Ansible module on the overcloud, hence Ansible not recognizing the tasks correctly.
2) Currently we cannot upgrade Pacemakerized deployments anyway (containerization of pacemakerized services is WIP), upgrades have only been tested with non-Pacemaker deployments so far.
I'm going to focus the fix on problem 2 for now, to unblock the upgrade CI as soon as possible.