Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-5019

Fails to deprovision cluster when swift omits 'content-type' and there are empty containers

XMLWordPrintable

    • +
    • Low
    • None
    • ShiftStack Sprint 229
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Some object storage instances respond with "204 No Content" when there is no content to display. The OpenStack SDK we use in OpenShift does not handle 204s correctly. With this change, the Installer works around the issue when there are zero objects to list in a Swift container.
      Show
      Some object storage instances respond with "204 No Content" when there is no content to display. The OpenStack SDK we use in OpenShift does not handle 204s correctly. With this change, the Installer works around the issue when there are zero objects to list in a Swift container.
    • Bug Fix

      This is a clone of issue OCPBUGS-4941. The following is the description of the original issue:

      Description of problem: This is a follow-up to OCPBUGS-3933.

      The installer fails to destroy the cluster when the OpenStack object storage omits 'content-type' from responses, and a container is empty.

      Version-Release number of selected component (if applicable):

      4.8.z
      

      How reproducible:

      Likely not happening in customer environments where Swift is exposed directly. We're seeing the issue in our CI where we're using a non-RHOSP managed cloud.
      

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

            pprinett@redhat.com Pierre Prinetti
            openshift-crt-jira-prow OpenShift Prow Bot
            Jon Uriarte Jon Uriarte
            Red Hat Employee
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: