Commits on Sep 18, 2018

1. ci-operator/templates/cluster-launch-installer-e2e*: Destroy with --c… …

   …ontinue-on-error
   
   Taking advantage of openshift/installer@23915f2e (installer/*: Add
   --continue-on-error to destroy workflow, 2018-09-16,
   openshift/installer#252) so we can reap at least most of our resources
   even if the cluster doesn't come up enough for the machine API
   operator to be able to destroy workers.  With various stages of
   cluster health:
   
   1. Cluster never comes up at all.
   2. Cluster healthy enough to create workers.
   3. Cluster healthy enough to destroy workers.
   
   we're only worried about leakage in the space between 2 and 3.
   Hopefully there isn't any space there, but without this commit we're
   currently leaking resources from 1 as well.
   
   The two-part destroy attempts are originally from 51df634 (Support an
   aws installer CI job, 2018-06-07, openshift#928), although there's not much to
   motivate them there.  With --continue-on-error destruction, we're
   already trying pretty hard to clean everything up.  So excepting brief
   network hiccups and such, I think a single pass is sufficient.  And
   we'll want a better backstop to catch any resources that leak through
   (e.g. orphaned workers), so I'm dropping the retry here.

   

   wking committed Sep 18, 2018
   Configuration menu

   • View commit details
   • Copy full SHA for 8444b7d
   • Browse repository at this point

   Copy the full SHA

   8444b7d View commit details

   Browse the repository at this point in the history