Bug 1835770 - [openstack] 409 Conflict error removing Swift storage
Summary: [openstack] 409 Conflict error removing Swift storage
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Image Registry
Version: 4.3.z
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.6.0
Assignee: Ricardo Maraschini
QA Contact: Wenjing Zheng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-14 13:22 UTC by Adam Kaplan
Modified: 2020-10-27 15:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Removing the image registry on OpenStack (swift) when content has already been written to the storage. Consequence: Storage for image registry was not being removed and an error was logged (409 http return code). Fix: Removed the storage content before removing the storage solved the issue. Result: Now by removing the internal registry the operator removes its storage completely.
Clone Of:
Environment:
Last Closed: 2020-10-27 15:59:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
operator-logs-swift (711.23 KB, text/plain)
2020-05-14 13:22 UTC, Adam Kaplan 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-image-registry-operator pull 567 0 None closed Bug 1835770: Removing container content before deletion 2021-02-08 09:21:54 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 15:59:36 UTC

Description Adam Kaplan 2020-05-14 13:22:52 UTC 
Created attachment 1688445 [details]
operator-logs-swift

Description of problem:

On OpenStack+Swift, the image registry cannot be Removed if images have been pushed & saved on its storage.


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


How reproducible:
Not always

Steps to Reproduce:
1.Import some images to image registry on OpenStack with Swift storage backend
2.Try to remove image registry
3.Try to bring image registry back and check pods under openshift-image-registry

Actual results:

Image registry cannot be removed - status in operator:
  storage:
    swift:
      authURL: https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13000/v3
      authVersion: "3"
      container: qeci-4524-3-8qxr6-image-registry-mayamgwnilbbvwodsclwpiqlhioke
      domain: redhat.com
      regionName: regionOne
      tenant: openshift-qe-jenkins
      tenantID: 542c6ebd48bf40fa857fc245c7572e30
status:
  conditions:
  - lastTransitionTime: "2020-05-11T10:26:58Z"
    message: |-
      Expected HTTP response code [] when accessing [DELETE https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13808/v1/AUTH_542c6ebd48bf40fa857fc245c7572e30/qeci-4524-3-8qxr6-image-registry-mayamgwnilbbvwodsclwpiqlhioke], but got 409 instead
      <html><h1>Conflict</h1><p>There was a conflict when trying to complete your request.</p></html>
    reason: |-
      Expected HTTP response code [] when accessing [DELETE https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13808/v1/AUTH_542c6ebd48bf40fa857fc245c7572e30/qeci-4524-3-8qxr6-image-registry-mayamgwnilbbvwodsclwpiqlhioke], but got 409 instead
      <html><h1>Conflict</h1><p>There was a conflict when trying to complete your request.</p></html>
    status: Unknown
    type: StorageExists

Expected results:

Image registry can be removed.

Additional info:
Comment 1 Oleg Bulatov 2020-05-18 12:24:08 UTC 
This exists for a few releases, not a release blocker.
Comment 4 Wenjing Zheng 2020-06-28 09:26:24 UTC 
Verified on 4.6.0-0.nightly-2020-06-26-035408.
Comment 6 errata-xmlrpc 2020-10-27 15:59:18 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196
Note You need to log in before you can comment on or make changes to this bug.