You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Volume mount failing with timeout error, please find error below.
It is observed that after mount failure, volume, snapshot & clone creation also fails intermittently.
In case volume mount pass, it will fail to mount it's snap volume.
Failure error of mount says "volume name must be unique", it is inappropriate error message.
Steps: -
create block volume and mount it.
create snapshot of volume and mount snapshot.
create clone of volume and mount it.
Error: -
Mount error : "docker: Error response from daemon: create volume1: found reference to volume 'volume1' in driver 'hpe:latest', but got an error while checking the driver: error while checking if volume "volume1" exists in driver "hpe:latest": Post http://%2Frun%2Fdocker%2Fplugins%2Fa7b2a1f89860c5314c4229f14aff62787f79547ff23cc0922b386ce09b1f0f57%2Fhpe.sock/VolumeDriver.Get: net/http: request canceled (Client.Timeout exceeded while awaiting headers): volume name must be unique."
Volume create error: "Error response from daemon: create volume1_snap: Post http://%2Frun%2Fdocker%2Fplugins%2Fa7b2a1f89860c5314c4229f14aff62787f79547ff23cc0922b386ce09b1f0f57%2Fhpe.sock/VolumeDriver.Create: net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
virendra-sharma
changed the title
Block volume operations failing in latest build, causing CI failure
Issue with global configuration parameters in hpe.conf, if updated in multiple backend then it damage plugin operations
Jul 15, 2019
CI issue resolved after updating "3PAR_DEBUG=True" in default backend and keep false in all other backends. But still just updating parameter should not affect plugin behavior.
Also, Error message updated in above issue looks misleading, it will be good if we look into it as well.
Observation: -
Steps: -
Error: -
Mount log : -
mount_fail.log
Volume log : -
volume_fail.log
The text was updated successfully, but these errors were encountered: