Description of problem:

If we create a LokiStack with a StorageClassName that doesn't exist in the cluster then the pods of all the StatefulSet components will stay in "pending", this is expected as the cluster will try to provision persistent volumes with a storage class that doesn't exist. However, if we update the StorageClassName to a correct one then the user has to both delete the StatefulSets and only then the PersistentVolumenClaim otherwise he will not be able to get a working stack.

Version-Release number of selected component (if applicable): 6.1 and prior

How reproducible: Always

Steps to Reproduce:

1. Create LokiStack with wrong storageClassName
2. Update the LokiStack to a correct storageClassName
3. Validate that both the StatefulSets & PersistentVolumenClaim still have the wrong StorageClassName

Actual results:

Expected results: If a StorageClass doesn't exist then we should be safe to deal with this issue for the user and not making him having to manually delete resources.

Additional info: