IBM VPC Block CSI Driver build fails in hermetic mode due to non-deterministic GOPATH handling in Makefile. The build system rewrites $GOPATH causing the binary output path -o ${GOPATH}/bin/${EXE_DRIVER_NAME} to become invalid, resulting in build failures.

OpenShift 4.19+ (affects hermetic build conversion) 

Always - when building ibm-vpc-block-csi-driver in hermetic mode

  1. Build ibm-vpc-block-csi-driver container in hermetic mode
  2. Makefile uses absolute GOPATH-dependent output path: -o ${GOPATH}/bin/${EXE_DRIVER_NAME}
  3. Build system rewrites $GOPATH during hermetic build process     

Build fails because binary cannot be found at expected GOPATH location after build system modifies $GOPATH

Error: building at STEP "COPY --from=builder /cachi2/output/deps/gomod/bin/ibm-vpc-block-csi-driver /bin/ibm-vpc-block-csi-driver": checking on sources under [...]: copier: stat: "/cachi2/output/deps/gomod/bin/ibm-vpc-block-csi-driver": no such file or directory

Build succeeds using relative path bin/${EXE_DRIVER_NAME} that doesn't depend on GOPATH manipulation, consistent with other CSI drivers like aws-ebs-csi-driver  

Fix implemented: Change Makefile to use relative path -o bin/${EXE_DRIVER_NAME} instead of absolute GOPATH-dependent path. This aligns with other CSI drivers and makes builds hermetic-compatible. Comment added to indicate this is a permanent carry patch for OpenShift builds.