Uploaded image for project: 'MicroShift'
  1. MicroShift
  2. USHIFT-4550

validate-custom-certificates.robot should cleanup changes to config at the end

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • openshift-4.18
    • openshift-4.18, openshift-4.16.z, openshift-4.17.z
    • None
    • None
    • None
    • uShift Sprint 261, uShift Sprint 262

      In the Configure Named Certificates keyword, the suite configures MicroShift to use extra certificates but it never reverts the config back to before-the-test version.

      This can sometimes result in a flake if the configured certs in /tmp dir disappear during next test resulting in MicroShift not starting.

      https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-microshift-release-4.16-ocp-metal-nightly-arm/1840225253691756544 

              pmatusza@redhat.com Patryk Matuszak
              pmatusza@redhat.com Patryk Matuszak
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: