Skip to main content
Keystone

Known limitations

Contributors netapp-shwetav netapp-manini
PDFs

Known limitations identify platforms, devices, or functions that are not supported by Keystone STaaS services or components, or that do not interoperate correctly. Review these limitations carefully.

Keystone Collector limitations

Keystone Collector authentication failure with StorageGRID SSO enabled

Keystone Collector does not support metering when the StorageGRID system has single sign-on (SSO) enabled. The following error message is displayed in the logs:

panic: json: cannot unmarshal object into Go struct field AuthResponse.data of type string

See Knowledge Base article Keystone Collector fails to authenticate with StorageGRID in SSO Mode for information and resolution.

Keystone Collector cannot start on vSphere 8.0 Update 1

A Keystone Collector virtual machine (VM) with VMware vSphere version 8.0 Update 1 cannot be switched on, and the following error message is displayed:

Property 'Gateway' must be configured for the VM to power on.

See Knowledge Base article Keystone Collector fails to start on vSphere 8.0 U1 for information and resolution.

Support bundle cannot be generated over Kerberos

If the Keystone Collector home directory is mounted over NFSv4 using Kerberos, the support bundle is not generated, and the following error message is displayed:

subprocess.CalledProcessError: Command '['sosreport', '--batch', '-q', '--tmp-dir', '/home/<user>']' returned non-zero exit status 1.

See Knowledge Base article Keystone Collector fails to generate support bundle on Kerberized home directory for information and resolution.

Keystone Collector cannot communicate with hosts within specific network range

Keystone Collector is unable to communicate with devices within the 10.88.0.0/16 network range when the ks-collector service is running. See Knowledge Base article Keystone Collector container conflict with customer network for information and resolution.

Keystone Collector cannot verify customer root SSL CA certificate

If SSL/TLS inspection is enabled at the border firewall in an environment to inspect SSL/TLS traffic, Keystone Collector is unable to establish an HTTPS connection, because the customer's root CA certificate is not trusted.

For more information and resolution, see Trust a custom root CA or Knowledge Base article Keystone Collector cannot verify Customer Root SSL CA certificate.