Known issues with solutions:


# If issue occurred while unmounting the ZFS volume : 

  • Simply reboot the VM.


# Storage File system issue on SWIFT.

  • We should add at least 40GB disk in VM then you can create a storage on SWIFT.


# If you get the error due to image unmount failed then you can try unmount the mounted image manually. (Note: SWIFT does image unmounting cleanups every 20 seconds by default use these steps if that doesn't unmount the images )

  • losetup -a /dev/loop0 [0040]:2 (/swift-pool01/mnt/xyz.img)
  • umount /swift-pool01/mnt/xyz.img
  • losetup -d /dev/loop0
  • zfs list NAME USED AVAIL REFER MOUNTPOINT swift-pool01/xyz 2.61M 57.5G 2.61M /swift-pool01/mnt/xyz
  • umount /swift-pool01/mnt/xyz
  • zfs set mountpoint=none swift-pool01/xyz


#  If you get the Timed out issue while synching in SWIFT, then you can uncomment below field in options file in SWIFT.

  • #dev_k8sClientOptions_httpTimeoutRetries=3

    #dev_k8sClientOptions_httpTimeoutRetryDelayMs=100


  • Option file path:  /opt/swift/data/options


#  Sync fails with error similar to

Object Sync action failed. [ ERROR: Failed to upload the object: <Object Kind> [name : <Object Name>]

ERROR: Object create request failed: POST request to the remote host failed [HTTP-Code: 500]: Server returned error response:

{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: failed calling webhook:

failed to call webhook: Post \"https://<Service Name>.<Namespace Name>.svc:443/<group>/<version>/<Object Kind>?timeout=10s\":

dial tcp 10.100.73.33:443: connect: connection refused" }

  • This error happens when the webhook dependencies are not ready.

      If the sync was triggered with sync webhook option then check the sync job for a warning indicating

      unreadiness of the workload object. If yes, and if the pod logs shows error indicating absence of some service,

      split the sync in to two syncs. First sync selecting the namespace specified in error message as the source namespace

      and selecting sync webhook option. Second sync with the original namespace without sync webhook option. Here the first

      sync will ensure all required services are present in the namespace required by the webhook dependencies thus making the

      webhhok dependencies ready.