Uploaded image for project: 'jclouds'
  1. jclouds
  2. JCLOUDS-187

ParseSwiftErrorFromHttpResponse.handleError should throw ContainerNotFoundException instead of KeyNotFoundException in all situations where container does not exist

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Minor
    • Resolution: Duplicate
    • 1.6.1
    • None
    • jclouds-blobstore

    Description

      ParseSwiftErrorFromHttpResponse.handleError always throws KeyNotFoundException for blob operations reporting 404. Could it parse the response from Swift and throw ContainerNotFoundException instead?

      $ bin/jclouds-cli-1.6.1-incubating/bin/jclouds blobstore container-exists gaul-fakecontainer
      Container not found: gaul-fakecontainer not found: while checking existence

      $ bin/jclouds-cli-1.6.1-incubating/bin/jclouds blobstore write gaul-fakecontainer blob input
      Blob not found: blob not found in container gaul-fakecontainer: <html><h1>Not Found</h1><p>The resource could not be found.</p></html>

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JCLOUDS-193 getBlob and putBlob do not throw ContainerNotFoundException on non-existent bucket

          • Critical - Crashes, loss of data, severe memory leak.
          • Open

          Activity

            People

              Unassigned Unassigned
              gaul Andrew Gaul
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: