Splunk® Phantom (Legacy)

Release Notes

This documentation does not apply to the most recent version of Splunk® Phantom (Legacy). For documentation on the most recent version, go to the latest release.

Known issues in this release of Splunk Phantom

The following are issues and workarounds for this release of Splunk Phantom.


Date filed Issue number Description
2021-06-02 PPS-25847 Automation is not run when adding duplicate artifact from same batch/post
2021-04-16 PPS-25718 ibackup script does unnecessary user switching
2021-04-09 PPS-25693 Python3 playbook converter fails when there is custom function block without custom code

Workaround:
Either remove the empty function block or add temporary code to the empty function block before converting the playbook.
2021-03-29 PPS-25651 ibackup fails to generate consecutive incremental backups
2021-03-26 PPS-25650 Converting some Python 2 playbooks to Python 3 with playbooks_to_py3 utility fails.

Workaround:
If converting a Python 2 playbook fails do the following:
  1. Open the Python 2 playbook in the Visual Playbook Editor.
  2. Click the Edit Playbook button.
  3. Click the Save button.
  4. Run the playbooks_to_py3 utility again.
2021-03-26 PPS-25639 Playbooks aren't running as they fail to pass validation
2021-03-25 PPS-25634, PSAAS-2292, PORT-484 "Error" in web interface and "ERROR: App install failed" in wsgi.log when updating Apps on a release of Splunk Phantom with a lower minor version number than the final release for that version.

Workaround:
If you receive this error, take the following steps:

1. Upgrade to the latest Splunk Phantom platform release. Use the --without-apps option. See:

2. Once the Splunk Phantom platform upgrade is complete, upgrade your installed Apps upgraded using the Main Menu > Apps, then clicking the APP UPDATES button.

2021-03-19 PPS-25613 UI : Timestamps are one hour off after daylight savings.
2021-03-05 PPS-25581 Fix UniqueViolation error when saving Indicators with NULL value.
2021-03-04 PPS-25580 Playbook save_object API accepts but drops values other than dicts
2021-02-25 PPS-25551 During Phantom cluster upgrade from 4.9 to 4.10 releases does not generate correct certificates

Workaround:
Restore the certificates from the backup made during the upgrade.

Do these steps on each Splunk Phantom node.

  1. SSH to the Splunk Phantom node.
  2. Stop Splunk Phantom.
    /<PHANTOM_HOME>/bin/stop_phantom.sh
  3. Change directory to <PHANTOM_HOME>/etc/consul/ssl/ca/
  4. Rename cacert.pem.bak.<date/time> to cacert.pem
    mv cacert.pem.bak.<date/time> cacert.pem
  5. Rename privkey.pem.bak.<date/time> to privkey.pem
    mv privkey.pem.bak.<date/time> privkey.pem
  6. Restart Splunk Phantom.
    /<PHANTOM_HOME>/bin/start_phantom.sh

2021-02-24 PPS-25548 phantom_install_log traceback in upgrade related to setting up cron job
2021-02-18 PPS-25507 ibackup incorrectly identifies space requirements
2021-02-01 PPS-25422, PPS-25532 The default note editor is visible before all notes are loaded
2020-12-21 PPS-25246 Filter block and decision block do not return correct result when called multiple times on the same chain of action results
2020-12-11 PPS-25216 When using the "Related Event" item from the artifact info screen in Investigation, produces error 'indicator_value 404 Not found' then displays a never-ending 'loading history' message
2020-11-18 PPS-25038 Boolean parameter 'Verify server certificate' is treated as 'None' by the Splunk Phantom platform.
2020-06-15 PPS-23462 Playbook API collect_from_contains fails to return data from user-defined and regular CEF types
Last modified on 27 July, 2021
Welcome to Splunk Phantom 4.10.2   Fixed Issues in this release of Splunk Phantom

This documentation applies to the following versions of Splunk® Phantom (Legacy): 4.10.2


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters