Description of problem:
trying to update osp13 from 2018-03-16.1 to 2018-03-29.1 fails
2018-04-04 10:39:58Z [overcloud-AllNodesDeploySteps-25fgux5nj775.WorkflowTasks_Step2_Execution]: UPDATE_COMPLETE The Resource WorkflowTasks_Step2_Execution requires replacement.
2018-04-04 10:39:59Z [overcloud-AllNodesDeploySteps-25fgux5nj775.WorkflowTasks_Step2_Execution]: CREATE_IN_PROGRESS state changed
2018-04-04 10:43:11Z [overcloud-AllNodesDeploySteps-25fgux5nj775.WorkflowTasks_Step2_Execution]: CREATE_FAILED resources.WorkflowTasks_Step2_Execution: ERROR
2018-04-04 10:43:11Z [overcloud-AllNodesDeploySteps-25fgux5nj775]: UPDATE_FAILED Resource CREATE failed: resources.WorkflowTasks_Step2_Execution: ERROR
2018-04-04 10:43:11Z [AllNodesDeploySteps]: UPDATE_FAILED resources.AllNodesDeploySteps: Resource CREATE failed: resources.WorkflowTasks_Step2_Execution: ERROR
2018-04-04 10:43:11Z [overcloud]: UPDATE_FAILED Resource UPDATE failed: resources.AllNodesDeploySteps: Resource CREATE failed: resources.WorkflowTasks_Step2_Execution: ERROR
Stack overcloud UPDATE_FAILED
Heat Stack update failed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install osp13 puddle 2018-03-16.1
2. run the update procedure
Created attachment 1417216 [details]
Created attachment 1417239 [details]
Created attachment 1417241 [details]
Created attachment 1417243 [details]
can you please provide some more info?
1) Mistral logs from undercloud would be useful (/var/log/mistral/*).
2) What were the `overcloud deploy` and `overcloud update` commands that were ran.
3) Was this an environment with Ceph? The error looks like it could be related to ceph-ansible, as WorkflowTasks_Step2_Execution is where ceph-ansible runs when it's enabled.
I understand we may not have the environment anymore but in case we hit this again, please add the info.
Please add logs from /var/log/mistral on undercloud
Hey Raviv can you add last logs Lukas asked?
I'm just closing this for now, but I will be happy to re-open if you provide the data requested in 10 days ago in #5.
Sure, I have mover to a newer build, which doe's not had this problem.