• EN
Solved

Kasten does not recognize Openstack Storage Driver Settings.

  • 13 February 2023
  • 2 comments
  • 138 views
R
Userlevel 1

I have Kasten installed in an OpenStack-Cluster via Helm. 

I have also set-up an infrastructure profile for OpenStack which is shown as valid. 

I can run normal Backups /w/o Volume Snapshots just fine but Snapshots fail.

The storage class is still recognized as CSI as shown in the Support page. 

The prefilight checks fail with the following message:

     ./k10tools primer storage check csi
serviceaccount/k10-primer created
clusterrolebinding.rbac.authorization.k8s.io/k10-primer created
job.batch/k10primer created
Pod k10primer-jzvsr is in Pending phase
Pod Ready!

Using "K10_PRIMER_CONFIG_YAML" env var content as config source
Using "K10_PRIMER_CONFIG_YAML" env var content as config source
CSI Snapshot Walkthrough:
  Unable to find a VolumeSnapshotClass for provisioner (cinder.csi.openstack.org) with k10 annotation (k10.kasten.io/is-snapshot-class) set to true.  -  Error
Error: {"message":"Unable to find a VolumeSnapshotClass for provisioner (cinder.csi.openstack.org) with k10 annotation (k10.kasten.io/is-snapshot-class) set to true.","function":"kasten.io/k10/kio/tools/k10primer.(*TestRetVal).Errors","linenumber":180,"file":"kasten.io/k10/kio/tools/k10primer/k10primer.go:180"}
failed to create fsnotify watcher: too many open files
serviceaccount "k10-primer" deleted
clusterrolebinding.rbac.authorization.k8s.io "k10-primer" deleted
job.batch "k10primer" deleted

From my understanding, setting the Volume SnapshotClass is not required for the Cinder integration, so it looks like Kasten is using CSI instead of the proper integration. 

Which step did I miss? 

icon

Best answer by jaiganeshjk 13 February 2023, 15:00

View original

2 comments

Madi.Cristil
Userlevel 7
Badge +7

@jaiganeshjk 

Madi Cristil
jaiganeshjk
Userlevel 6
Badge +2

@Refresh2260 Thank you for posting your question here.

Openstack infrastructure profile is supported only for PVCs provisioned with Cinder In-Tree provisioner(kubernetes.io/cinder). Most of the times, we use infrastructure profiles only in cases where the provisoner doesn’t support taking snapshots the CSI way(Except for Vsphere).

Since Cinder CSI driver already supports snapshotting through volumeSnapshot resources, I would suggest you to make use of that by creating volumesnapshotclass and annotating it with the above annotation.

https://docs.kasten.io/latest/install/storage.html#csi-snapshot-configuration

Jaiganesh

Comment


Terms & Conditions