This repository has been archived by the owner on Dec 4, 2018. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 42
Venerable app is not deleted #37
Comments
Was the new app running successfully? |
I'm having the same issue. Otherwise, it works great. update: I've used this 3 times now, and one time it worked as intended where venerable app was deleted after deploying the new app. |
Might be nice for autopilot to handle some edge cases, such as both the regular and venerable apps existing when you try and deploy, or just the venerable. In those cases, it could either give an error and some guidance, or just Do The Right Thing. |
aeijdenberg
added a commit
to govau/autopilot
that referenced
this issue
Nov 2, 2017
… left dangling May fix some of the edge cases identified in <contraband#37 (comment)>
aeijdenberg
added a commit
to govau/autopilot
that referenced
this issue
Feb 1, 2018
Fix situations where CI has failed, and -venerable apps left dangling May fix some of the edge cases identified in <contraband#37 (comment)>
xoebus
pushed a commit
that referenced
this issue
Feb 1, 2018
Fix situations where CI has failed, and -venerable apps left dangling May fix some of the edge cases identified in <#37 (comment)>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In a similar vein to #12 - the renamed (venerable) app is not being deleted for me. The initial deploy does not appear to be successful, but instead simply hangs without an error. Below is what I see in the console, hanging at the last line with no resolution.
At this point both apps, new and venerable, still visible in my Bluemix console. Not sure on how to debug further. Suggestions?
The text was updated successfully, but these errors were encountered: