Known limitations
Known limitations for IBM Bob on-premises in the current release, including missing Admin UI features, upgrade restrictions, and configuration requirements for Z-specific features.
The following limitations apply to the current release of IBM Bob on-premises.
Activity logs not available in Admin UI
The Activity Logs feature is not included in the Bob Admin UI for this release.
To access service logs, view the pod logs for the following services directly from the OpenShift Container Platform console or CLI:
- Authentication service
- Authorisation service
- Admin service
oc logs -n <instance-namespace> -l app=bob-authn
oc logs -n <instance-namespace> -l app=bob-authz
oc logs -n <instance-namespace> -l app=bob-adminIn-place upgrades not supported
Controlled in-place upgrades are not supported in this release. When moving to a new release version, a fresh installation is recommended.
You can apply hotfixes to an existing instance by re-running ./bobctl install against the same instance. Full in-place upgrade support is planned for a future release.
unknown model: zproxy error when using Z-specific features
If a user with a Bob Premium Package for Z entitlement encounters a "cause": "unknown model: zproxy" error when using Z-specific features, the backend was installed without the required Z components enabled.
To resolve this issue, the cluster administrator must reinstall or reconfigure the backend with the following values set in config.yaml before the frontend entitlement is assigned to users:
rag:
enabled: true
zProxy:
enabled: trueAssigning the Premium Package for Z entitlement to users before the corresponding backend components are installed causes this error. Ensure that rag.enabled: true and zProxy.enabled: true are configured and the installation is complete before assigning Z entitlements.