Deployment and activation status information
You can see status information for deployment and activation on the Real Estate and Facilities page. The Facilities operator maintains a status
subresource for each instance that it manages. This status includes both Kubernetes conditions and
reason codes.
Conditions
- Running
- True while the operator is running the reconciliation for the custom resource (CR) instance.
- Successful
- True when the reconciliation cycle for the CR instance finishes without errors. The operator then waits for the next reconciliation action, either the reconcile period, dependent watches triggers, or the resource is updated.
- Failed
- True if an error occurs during the reconciliation run for the CR instance, and the error message from the error that caused this condition is reported. The error message is the raw output from the run for reconciliation. If the failure is intermittent, the situation can often be resolved when the operator reruns the reconciliation loop.
- Initialized
- True when all resources are created, including all the application pods.
- Ready
- True when all application pods reach the
Readycondition.
Reason codes
FacilitiesApp
PodTemplatesInvalid- Validation ofpodTemplateskeys failed.CertificateNotReady- Secret is not available.TruststoreNotReady- Suite truststore is not ready.
FacilitiesWorkspace
AppserverNotReady- TheAppserverStatefulSethas not finished its initialization.MinimumReplicasNotAvailable- The minimum required number of replicas forStatefulSetis not met.StorageError- Unable to create or modify StorageClass.DWFAgentsNotReady- The dedicated workflow agents have not finished initialization.AgentsNotReady- One or more agents have not finished initialization.BindingFailure- Facilities did not correctly bind to IBM® Maximo® Application Suite.CompatibilityCheckFailure- The supported Maximo Real Estate and Facilities and Maximo Real Estate and Facilities versions do not match.CompatibilityCheckFailure- The supported Manage Foundation and Maximo Real Estate and Facilities versions do not match.DataInitializationPending- Data Initialization not yet finished. This can take up to a few hours, depending on your network speed and database storage type.DataInitializationFailed- Data Initialization has failed.