Known Issues in this release of Splunk Phantom

These are the known issues for this release of Splunk Phantom.

Date filed	Issue number	Description
2021-08-04	PSAAS-2797	Message "Complete!" is displayed prematurely during upgrade of Splunk Phantom.
2021-08-04	PSAAS-2798, PSAAS-2560	A blank screen opens when editing an event in the Analyst Queue page. Workaround: Edit the event from the Investigation page instead.

Date filed	Issue number	Description
2022-07-20	PSAAS-9535	after --standby-mode --off postgresql.phantom.conf not cleaned up Workaround: manually disable archive_mode by removing postgresql.phantom.conf and editing postgresql.conf to delete the include_if_exists 'postgresql.phantom.conf' (for thoroughness). restart postgresql
2021-09-20	PSAAS-3615	Cannot add environment variables to specific tenant Workaround: no current workaround for issue.
2021-08-30	PSAAS-3374	NRI unable to add external SSH Repo Workaround: Manually correcting this via the CLI by running the following as the Phantom user, corrects the issue: ssh-keyscan -t rsa github.com >> /home/<phantom_user>/.ssh/known_hosts
2021-08-25	PSAAS-3345	Warm Standby: "phsvc status iptables" and "phsvc status firewalld" returned non-zero exit status 4 Workaround: none known
2021-08-25	PSAAS-3346	Warm standby missing logging in 4.10 as compared to 4.8
2021-08-25	PSAAS-3342, PSAAS-9527	Warm standby: After --primary-mode --off archive_mode is still on, potentially filling up disk space and crashing postgresql and system Workaround: manually disable archive_mode by removing postgresql.phantom.conf and editing postgresql.conf to delete the include_if_exists 'postgresql.phantom.conf' (for thoroughness). restart postgresql
2021-08-23	PSAAS-3289	Can't Delete Value from Org Id/Set Domain for Thycotic password vault
2021-08-18	PSAAS-3229	Indicator View Search Filter Text Entry Cause Screen to Blank Workaround: only known workaround is to manually scroll through the very long list of indicator types to find your desired indicator type.
2021-08-13	PSAAS-2945	DB replication and warm standby failover work, but webserver fails to start. You see "ERROR: cannot execute UPDATE in a read-only transaction" in logs. Server is operating as standby, but you can't run REST endpoints on the server, as webserver is down.
2021-07-16	PSAAS-2591	Asset Proxy Settings: Previously configured HTTP or HTTPS Proxy not working as intended Workaround: * Determine if your proxy is an HTTP or HTTPS proxy. If you have an HTTP proxy and your asset settings have proxy variables starting with https://<proxy_ip>, replace them with http://<proxy_ip> If you have an HTTPS proxy and your asset settings have proxy variables starting with http://<proxy_ip>, replace them with https://<proxy_ip>