search

vmware-archive / pcf-pipelines

PCF Pipelines
Apache License 2.0
158 stars 283 forks source link

AWS Ops Manager upgrades timed out during replace-opsman-vm task #122

Closed xyloman closed 7 years ago

xyloman commented 7 years ago

I have been fighting with this issue for a few weeks now and had not posted anything until we got our pipelines built out and maintained using pcf-pipelines-maestro. We also have upgraded our AWS foundation to leverage pcf-pipelines 0.15.0 from pivnet. When we get to the task replace-opsman-vm for job upgrade-opsmgr we continuously get the error 2017/06/15 15:20:10 error: timed out waiting for instance to become TERMINATED (last status was stopped)

cf-gitbot commented 7 years ago

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

xchapter7x commented 7 years ago

this was an issue with a tool called cliaas, which is bundled in our base image. this should just start working as the next time the task runs it will pull the latest docker image, which now contains the fix.

for reference: https://github.com/pivotal-cf/cliaas/releases/tag/v0.1.9

closing this for now, let me know if the issue is not resolved and we can re-open @xyloman

sakkoub commented 6 years ago

@xyloman I am still facing this issue with PCF pipelines version v0.23.6, please any advise