Known Issues and Workarounds

installation known issue for version 24 3 0 of the turbine platform, if you encounter any issues with swimlane tenant pods related to the database during a new installation, redeploy the application no action is required if you are upgrading velero preflight check failing during online upgrades issue the velero preflight check fails for some online upgrades, potentially blocking the upgrade process workaround if velero version is v1 14 0, ignore the preflight check and proceed with the deployment if velero version is not v1 14 0, rerun the following command curl ssl https //kurl sh/turbine turbine 24 3 2 | sudo bash turbine library issue #1 when using auto sync with a remote repository in the turbine library, if there’s a conflict between remote and local changes, the merge conflict resolution screen does not appear immediately instead, an error is displayed, indicating that publishing to the remote repository has failed workaround use the manual "push" option in the admin panel to trigger the merge conflict resolution screen, allowing you to choose between applying the local or remote changes issue #2 when publishing content packages to the library, the publish action fails if the package name contains special characters or duplicates the name of an existing package workaround ensure that the content package name is unique and does not contain any of the following special characters /, ?, <, >, , , , |, , , or " issue #3 currently the ui allows user to select the current version of a content package when reverting content to a previous version workaround this is mainly a ui/ux issue and do not impact core functionality when in this scenario, user will be prompted to enter a new version # and this revert will not result in any changes in the content issue #4 when user is publishing a custom content package into turbine library that may contain previously installed swimlane content, the “package details” dialog may incorrectly display a yellow exclamation icon workaround this is mainly a ui/ux issue and do not impact core functionality user can disregard the icon and no further action needed remote agents known issue remote agents may fail to recover and reconnect after a network disconnection, resulting in repeated “unexpected error occurred during agent heartbeat” messages workaround a script can be provided to restart the remote agent container please contact support for assistance if you encounter this issue usage metrics dashboard issue in the events dashboard, the triggered playbooks column is incorrectly showing the number of events instead of the actual count of triggered playbooks turbine login issue if an invalid domain name or account name is provided in the settings, any attempts to update will fail without displaying specific error messages workaround ensure that the domain name is valid before attempting updates a domain name validity check should be implemented when updates to account settings fail audit logging issue the audit log api in swimlane turbine may encounter a 500 internal server error when attempting to retrieve or display a list of ip addresses in the source ip field adding users to groups issue when a user is added to a group the action fails intermittently workaround add group to user or add group to a role and add to a user