High-Speed Transfer Server deployment conditions and error messages

When you deploy High-Speed Transfer Server (HSTS), the conditions that are provided specify the deployment status of OpenShift. You might also get an Error that describes what needs to be fixed.


Kubernetes conditions are supported by the Aspera HSTS service; they are a snapshot of the Aspera HSTS service instance's most recent and current condition. The following table describes these conditions.

Condition Description
Pending When the Aspera HSTS service is initially created, the Pending condition is set to True, and it reconciles the wanted StatefulSet.

The Pending condition is eliminated after the StatefulSet is constructed and is Ready. The messages update while the user is in the Pending state to acknowledge the current stage of the provisioning process. For instance, a message can mention that a ConfigMap is being currently provisioned and the process is not yet complete.

Ready The Ready condition is set to True when all of the pods in a StatefulSet are ready and the number of replicas therein matches the wanted number of replicas that are specified by the Aspera HSTS Service instance spec.
Error When an error occurs during an Aspera HSTS Service reconciliation, the Error condition is set to True. Details concerning the issue must be included in the Reason and Message, such as the usage of an improper storage class.

Error condition messages

If an error occurs during an HSTS Service reconciliation, the Error condition is set to True and an error message is returned. The following table describes the Error condition messages.

Error message Description
spec.license.accept must be true Produced if the user didn't accept the license (triggers during run time as well).
spec.license.key must not be empty Produced if the user left the license key value empty.
spec.storages: claimName, mountPath and class must not be empty Produced when the user left either claimName, mountPath, or class values empty.
Could not create semantic constraint Produced if the user attempted to run the operator on an unsupported version of Red Hat OpenShift. For more information, see High-Speed Transfer Server (HSTS) support matrix.
Unable to retrieve OpenShift Version from the ClusterVersion object Produced when the operator version might not be retrieved (reinstall and redeploy the cluster).
Could not resolve semantic version Produced when the operator might not deploy, even though the version of Red Hat OpenShift is later than the minimum supported version. For more information, see High-Speed Transfer Server (HSTS) support matrix.
spec.license.key not a valid license Produced if an invalid license was entered.
invalid upgrade path Produced if a user attempted to upgrade from one version of the operator to another version that isn't supported. For more information, see High-Speed Transfer Server (HSTS) support matrix.
Name should not be longer than 253 characters, must consist of lower case alphanumeric characters or '-', start and ends with an alphabetic character Produced if an invalid service name was selected for the HSTS service.