Portworx install looks to be ok but PVCs created after Portworx is reinstalled fail to start.
The problem could be that the original volumes are reused with the second portworx deploy... If the volumes are deleted then new ones will be automatically created but if a volume already exists with the same name then it will be reused. Right now there is no automated way to destroy the volumes.
Perhaps we should generate a unique identifier with each deploy to add to the volume identifier...
Portworx install looks to be ok but PVCs created after Portworx is reinstalled fail to start.
The problem could be that the original volumes are reused with the second portworx deploy... If the volumes are deleted then new ones will be automatically created but if a volume already exists with the same name then it will be reused. Right now there is no automated way to destroy the volumes.
Perhaps we should generate a unique identifier with each deploy to add to the volume identifier...