If a custom profile is uploaded with any syntactical errors (see Chef InSpec Profile Style Guide) then it will hang the Chef Automate UI when attempting to render the profile by clicking the compliance tab and then attempting to load/render the highlighted profile. It will subsequently render a spinning chef logo which will hang the UI. The only way to exit this is to reload the browser tab without navigating to this profile.

If you don't already have the erroneous profile locally, use an API call to fetch it to your local machine (see profiles):

curl --insecure -H "x-data-collector-token: token-val" https://automate.example.com/api/v0/compliance/profiles/tar -d '{"name":"my-custom-profile-lvel1","owner":"admin","version":"1.0.0"}'

Retrieve the SHA256 from your profile using:

inspec json my-custom-profile-level1-1.0.0.tar.gz | grep sha256

This ensures that if you have multiple similarly-named profiles, we only pick out the SHA sum-matched profile. You should be able to confirm the SHA sum from the included section:

"depends": [], "sha256": "2067ce3bba2c1492016d66ecfdd5fd92237217e7d170e9636f4baf5151d4bacb", "groups": [], "controls": [], "attributes": [], "latest_version": "" }

To actually remove the custom profile, follow the below steps.

Log in to the Chef Automate instance via shell session as a root/system level user, and run the following command:

chef-automate dev psql chef_compliance_service

You should now be in the chef_compliance_service shell. Identify the profile to delete using its SHA256 checksum:

select * from store_namespace where sha256='2067ce3bba2c1492016d66ecfdd5fd92237217e7d170e9636f4baf5151d4bacb';

Expect a response like:

 owner |                              sha256                              
-------+------------------------------------------------------------------
 admin | 2067ce3bba2c1492016d66ecfdd5fd92237217e7d170e9636f4baf5151d4bacb
(1 row)

Once confirmed, delete the profile from the namespace table:

delete from store_namespace where sha256='2067ce3bba2c1492016d66ecfdd5fd92237217e7d170e9636f4baf5151d4bacb';

Also delete the profile from the store_profiles table (note this will only work on profiles you have customized/uploaded as the store_market profiles cannot be removed):

delete from store_namespace where sha256='2067ce3bba2c1492016d66ecfdd5fd92237217e7d170e9636f4baf5151d4bacb';

Verify that your profile is now gone:

select * from store_namespace where sha256='2067ce3bba2c1492016d66ecfdd5fd92237217e7d170e9636f4baf5151d4bacb';

owner | sha256 
-------+--------
(0 rows)

In the Automate UI, if you navigate to the Compliance tab and click through to the profile, it should now render the details correctly.