Bug 1292212 - Updating a failed stack fails with Stack already has an action (UPDATE) in progress.
Updating a failed stack fails with Stack already has an action (UPDATE) in pr...
Status: CLOSED DUPLICATE of bug 1253773
Product: Red Hat OpenStack
Classification: Red Hat
Component: rhosp-director (Show other bugs)
7.0 (Kilo)
Unspecified Unspecified
unspecified Severity urgent
: ---
: 7.0 (Kilo)
Assigned To: chris alfonso
Depends On:
  Show dependency treegraph
Reported: 2015-12-16 13:18 EST by Marius Cornea
Modified: 2016-04-18 03:00 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1301511 (view as bug list)
Last Closed: 2016-01-07 14:35:37 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
2nd.update.output (3.40 KB, text/plain)
2015-12-16 13:18 EST, Marius Cornea
no flags Details

  None (edit)
Description Marius Cornea 2015-12-16 13:18:04 EST
Created attachment 1106501 [details]

Description of problem:
I'm trying to update a 7.0 environment and simulate a failure during the update. To accomplish this I didn't install any repos on the overcloud nodes. The first update attempt failed, I then installed the repos on the nodes and reran the update command but I still got a failed stack.

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. Deploy 7.0 with the overcloud nodes having no repos installed
openstack overcloud deploy \
    --templates ~/templates/my-overcloud \
    --control-scale 1 --compute-scale 1 --ceph-storage-scale 0 \
    --ntp-server clock.redhat.com \
    --libvirt-type qemu \
    -e ~/templates/my-overcloud/environments/network-isolation.yaml \
    -e ~/templates/network-environment.yaml \

2. Update the undercloud to 7.2 and attempt to update the overcloud
/usr/bin/yes '' | openstack overcloud update stack overcloud -i \
         --templates ~/templates/my-overcloud \
         -e ~/templates/my-overcloud/overcloud-resource-registry-puppet.yaml \
         -e ~/templates/my-overcloud/environments/network-isolation.yaml \
         -e ~/templates/network-environment.yaml \
         -e ~/templates/my-overcloud/environments/updates/update-from-keystone-admin-internal-api.yaml \
         -e ~/templates/param-updates.yaml

Result: update finished with status FAILED
 "deploy_stderr": "cat: /var/lib/tripleo/installed-packages/*: No such file or directory\nThere are no enabled repos.\n Run \"yum repolist all\" to see the repos you have.\n You can enable repos with yum-config-manager --enable <repo>\n", 

3. Manually add the 7.2 repos on the overcloud nodes

4. Rerun the update command

Actual results:
The update command fails after trying to remove the breakpoint on overcloud-compute-0 for a couple of times(see attached 2nd.update.output). The yum update has been run on the overcloud-compute-0 node as there are no available packages updates. 

The stack_status_reason is resources.Controller: Stack overcloud-Controller-5ldijz5uvxog already has an action (UPDATE) in progress and indeed there seem to be nested stacks with UPDATE_IN_PROGRESS while the overcloud stack is UPDATE_FAILED.

heat stack-list -n | grep PROGRESS
| a4f9c92d-cbd3-427b-8829-f3913f187cae | overcloud-Controller-5ldijz5uvxog                                                                             | UPDATE_IN_PROGRESS | 2015-12-16T16:49:28Z | e48ee6e8-e167-4a84-91e3-04978ec3520e |
| 2b03d6ba-e222-4565-a3f3-2d2b2744ec83 | overcloud-Controller-5ldijz5uvxog-0-spbwkx4yxzeo                                                              | UPDATE_IN_PROGRESS | 2015-12-16T16:49:31Z | a4f9c92d-cbd3-427b-8829-f3913f187cae |

heat stack-list
| id                                   | stack_name | stack_status  | creation_time        |
| e48ee6e8-e167-4a84-91e3-04978ec3520e | overcloud  | UPDATE_FAILED | 2015-12-16T16:49:12Z |
Expected results:
The update process completes OK.
Comment 2 Marius Cornea 2015-12-17 03:01:25 EST
Workaround for this is to to wait until that IN_PROGRESS update times out and 
rerun update.
Comment 3 Zane Bitter 2016-01-07 14:35:37 EST
Note that you *should* be able to speed up the workaround by restarting heat-engine on the undercloud, as that puts the nested stacks into the FAILED state at startup. I say "should" because this was notoriously buggy in the past, though we believe it's working now.

I'm going to close this as a duplicate, since it's a known problem.

*** This bug has been marked as a duplicate of bug 1253773 ***

Note You need to log in before you can comment on or make changes to this bug.