After the future removal of the classic playbook editor, your existing classic playbooks will continue to run, However, you will no longer be able to visualize or modify existing classic playbooks.
For details, see:
Fixed issues for
Release 6.1.0
Date resolved | Issue number | Description |
---|---|---|
2023-06-09 | PSAAS-11190 | VPE: Block Names with Container - A block name with "container" cannot share its results in other blocks in the Visual Editor |
2023-06-09 | PSAAS-12976 | VPE: Manually selecting an asset deletes block configuration |
2023-06-08 | PSAAS-13530 | "Phantom startup failed: phantom_actiond" and "Waiting for Mnesia tables" when starting cluster nodes |
2023-06-08 | PSAAS-13503 | When a user without system_settings view permission switches tabs from the SOAR homepage, the SOAR UI and apps become unresponsive. |
2023-06-06 | PSAAS-12782 | VPE: phantom.collect2 fails if using a filter block that contains an action name |
2023-06-02 | PSAAS-13156, PSAAS-12705 | VPE: Condition blocks treat "False" and "True" as strings, not Boolean values |
2023-06-01 | PSAAS-13154 | VPE: When opening playbooks, 'Invalid Resource' appears incorrectly on some blocks |
2023-05-30 | PSAAS-9533 | setup_warm_standby on standby fails with "String does not contain a date" when pg_last_xact_replay_timestamp() returns empty results and --status or --convert-to-primary specified |
2023-05-30 | PSAAS-12605 | setup_warm_standby.pyc does not take nri into consideration when processing --convert-to-primary: "yum command failed"/"You need to be root" |
2023-05-30 | PSAAS-12608 | setup_warm_standby.pyc still tries to use python 2.7 when processing --convert-to-primary: "{phantom_home}/bin/phenv pip2.7 install -r {phantom_home}/var/log/phantom/pip_packages_primary.txt |
2023-05-26 | PSAAS-13512 | Settings up shared services with make_server_node.py will fail if using a ssh keyfile instead of a user and a password for authentication. |
2023-05-26 | PSAAS-13398 | After upgrading from 6.0.0 to 6.0.1/6.0.2, configuring a new asset fails with the error message, "Cannot complete installing <app name>. Return to the Apps page and try installing again." |
2023-05-24 | PSAAS-9527, PSAAS-3342 | Warm standby: After --standby-mode --off archive_mode is still on, potentially filling up disk space and crashing postgresql and system |
2023-05-19 | PSAAS-12331 | VPE: Naming blocks the same for utility block causes the blocks to sync |
2023-05-09 | PSAAS-13176 | Conditional installer tasks can fail to execute when retrying a failed upgrade |
2023-05-09 | PSAAS-12968 | License is removed from SOAR if too many seats are used |
2023-05-02 | PSAAS-12198 | App action links within app documentation do not work |
2023-04-29 | PSAAS-13084 | Some SOAR connectors fail to install due to missing modules - import error |
2023-04-26 | PSAAS-13069 | Py2_deprecation check fails loudly if you run the unpriv installer as root |
2023-04-13 | PSAAS-13062 | Reverts PSAAS-11066 in 6.0.0 - User with the "view" permission in one tenant is able to edit assets in other tenants |
Known issues for | Compatibility with related Splunk products |
This documentation applies to the following versions of Splunk® SOAR (On-premises): 6.1.0
Feedback submitted, thanks!