Release notes for the Splunk Python Upgrade Readiness App

The Python Upgrade Readiness App version 1.0.0 was released on March 27, 2021. This version is compatible with Splunk Enterprise versions 7.3, 8.0, and 8.1.

Known issues

This version of the Splunk Python Upgrade Readiness App has the following known issues and workarounds.

Publication date	Defect number	Description
2021-06-26	SPL-206256	Not able to execute scan on failed Splunkbase apps. The Python Upgrade Readiness App uses the metadata collected from Splunkbase APIs to validate whether an app is compatible with Python 3. This metadata is updated once daily at 11 PM. If the app version installed in your environment is not present in this metadata, the app will be classified as a failure. As designed, you cannot run a scan on the failed Splunkbase app. Workaround: To run scans on apps that show a failure for the above-described reason, perform the following steps on these metadata files: $SPLUNK_HOME/etc/apps/python_upgrade_readiness_app/local/app_list/splunkbaseapps_<timestamp>.csv (may not be always present) $SPLUNK_HOME/etc/apps/python_upgrade_readiness_app/bin/libs_py2/pura_libs_utils/splunkbaseapps.csv $SPLUNK_HOME/etc/apps/python_upgrade_readiness_app/bin/libs_py3/pura_libs_utils/splunkbaseapps.csv Open the CSV file and search for the app (using the app label or app id) for which you want to execute the scan. Remove that particular row from the CSV file and save it. After completing steps 1 and 2 for each metadata file, in Splunk Web, click Settings > Data inputs > Scripts and disable the script $SPLUNK_HOME/etc/apps/python_upgrade_readiness_app/bin/pura_get_all_apps.py.
2021-06-26	SPL-206257	Scan appears stuck and clicking "Manage Scan Schedule" returns an error. In a search head cluster, when you save the scan schedule using the "Manage Scan Schedule" button on any cluster member, the data in the KV Store is altered, which causes the scan to stop on the other cluster members. The member on which you change the schedule will continue to function as expected. Workaround: Delete the pra_schedule_scan KV Store collection in the python_upgrade_readiness_app, as follows: $SPLUNK_HOME/bin/splunk clean kvstore --app=python_upgrade_readiness_app --collection=pra_schedule_scan Or, you can delete the KV Store collection via REST API, as follows: curl -k -u <username>:<password> https://<splunk_ip_or_host>:8089/servicesNS/nobody/python_upgrade_readiness_app/storage/collections/data/pra_schedule_scan -X DELETE" Thereafter, to modify the schedule of scans, follow these steps: In Splunk Web, click Settings > Data Inputs > Scripts. Click $SPLUNK_HOME/etc/apps/python_upgrade_readiness_app/bin/pura_scan_apps.py. Change the interval to the desired interval. Click Save.
2021-02-26	SPL-203061	Scans show incomplete results if scan time exceeds user session timeout limit or hung scan may appear to still be running. Workaround: Select Cancel Scan to end the scan, then do one of the following: Break up your list of apps into multiple scans of smaller batches. OR Increase your session timeout duration beyond the 60 minute default before running long scans. See Configure user sessions timeouts.