Doc Bug: BSL configuration with Noobaa is not correct

[xinredhat]

Contact Details

xjiang@redhat.com

Describe bug

Here is the doc link https://github.com/openshift/oadp-operator/blob/master/docs/config/noobaa/install_oadp_noobaa.md.

The example of backupStorageLocations spec in the Velero CR has following issues:

1. insecureSkipTlsVerify is not correct. It should be insecureSkipTLSVerify, TLS should be uppercase. if you use insecureSkipTlsVerify , it will report error

time="2021-10-27T04:55:38Z" level=error msg="Error getting backup store for this location" backupLocation=example-velero-1 controller=backup-sync error="rpc error: code = Unknown desc = config has invalid keys [insecureSkipTlsVerify]; valid keys are [region s3Url publicUrl kmsKeyId s3ForcePathStyle signatureVersion credentialsFile profile serverSideEncryption insecureSkipTLSVerify bucket prefix caCert]" error.file="/opt/app-root/pkg/mod/github.com/vmware-tanzu/velero@v1.6.2/pkg/plugin/framework/validation.go:50" error.function=github.com/vmware-tanzu/velero/pkg/plugin/framework.validateConfigKeys logSource="pkg/controller/backup_sync_controller.go:175"

2. If there is one one BSL or VSL, you should add property spec.backupStorageLocations.default = true or spec.volumeSnapshotLocations.defaut=true. Otherwise it will report warning time="2021-10-27T04:58:59Z" level=warning msg="There is no existing backup storage location set as default. Please see velero backup-location -h for options." controller=backup-storage-location logSource="pkg/controller/backup_storage_location_controller.go:173"

What happened?

A bug happened!

OADP Version

0.4.x (Beta)

OpenShift Version

4.9

Velero pod logs

No response

Restic pod logs

No response

Operator pod logs

No response

New issue

• This issue is new