Uploaded image for project: 'OpenShift Runtimes'
  1. OpenShift Runtimes
  2. RUN-1929

podman machine: callback teardown for init

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Undefined
    • None
    • None
    • None
    • RUN 242, RUN 243, RUN 244, RUN 245

    Description

      this would need to be done on all providers

      when podman machine init fails, we need to clean up behind what was done because or we can get our state all messed up.  this would entail something like:

      • if json file is written, we need to delete it
      • if image file is created, we need to delete it
      • if a vm instance is created, it needs to be deleted (WSL and HyperV)
      • if ssh ids are created, we need to delete them
      • if system connections are created, we need to delete them

       

      thoughts on testing:

      We need  to find ways to trip failures.  One idea for something like keys

      • podman machine init foobar
      • podman machine rm save-keys
      • podman machine init foobar

      the same could be done for system connections

      Attachments

        Activity

          People

            ashley-cui Ashley Cui
            bbaude@redhat.com Brent Baude
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: