Chapter 3. Known Issues

This chapter provides a list of known issues at the time of release.

BZ#1654703
A block hosting volume stop request, sometimes, fails to detach a brick instance from the running parent brick process. This results further deletion request for the block hosting volume to fail with "resource busy" error. Due to this, heketi has stale block hosting volume entry maintained in it's database. To workaround this issue, the system state can be corrected by restarting the gluster pod where a dangling resource for the brick instance of the block hosting volume exists. Heketidb can be repaired by removing the block hosting volume entry.
However, it is advised NOT to delete block hosting volumes as the workaround steps are complex.
BZ#1644289
Brick multiplexing is not automatically enabled in any of the deployment modes of gluster. Brick multiplexing is required to meet the OCS supported volume limits and hence it must be manually enabled if the trusted storage pool will be used with OCS in independent mode.
BZ#1597320
Few paths are missing for iscsi mpath device. This is because, either CHAP security values mismatch or iscsi CSG: stage 0 has been skipped. Both will result in iSCSI login negotiation to fail.
To workaround this issue, delete the app pod which will trigger the restart of the pod. The pod start will then update the credentials and relogins.