Trident: Storage prefix doesn't support "" any longer.

We just updated 20.01.1 to 20.07.0 and ran into this as well. Our prefix includes a "-".

time="2020-08-11T08:19:05Z" level=error msg="Could not initialize storage driver." error="error validating ontap-nas driver: driver validation failed: storage prefix may only contain letters/digits/underscore and must begin with letter/underscore"
time="2020-08-11T08:19:05Z" level=warning msg="Cannot terminate an uninitialized backend." backend= backendUUID= driver=ontap-nas state=failed
time="2020-08-11T08:19:05Z" level=error msg="problem initializing storage driver 'ontap-nas': error validating ontap-nas driver: driver validation failed: storage prefix may only contain letters/digits/underscore and must begin with letter/underscore" backend= handler=UpdateBackend

Now we're stuck because updating it is not supported:

updating the storage prefix isn't currently supported (400 Bad Request)
command terminated with exit code 1

Problem introduced in #401

@lopf we are working on providing a patch release to fix this issue. I'll also update this issue once the commit with the fix is merged.

@gnarl Is there an approximate date for the patch release? We are eagerly waiting for it so that we can continue with the next clusters.

@sevenval-admins, I can't give you a solid date but we are currently working on bug fixes and also need to qualify K8S 1.19 for a 20.07.1 patch release. The storage prefix fix is already committed here.

This is fixed with the Trident v20.07.1 release.