Version : TrueNAS-12.0-U3.1

Impact : Unable to create any OpenStack Swift cloud credentials, which prevents setting up cloud sync tasks.

Details:

When trying to add OpenStack Swift cloud credentials, I am getting the following error:

Error: Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 137, in call_method
result = await self.middleware._call(message['method'], serviceobj, methodobj, params, app=self,
File "/usr/local/lib/python3.8/site-packages/middlewared/main.py", line 1195, in _call
return await methodobj(*prepared_call.args)
File "/usr/local/lib/python3.8/site-packages/middlewared/schema.py", line 973, in nf
return await f(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/cloud_sync.py", line 559, in verify
await self._validate("cloud_sync_credentials_create", data)
File "/usr/local/lib/python3.8/site-packages/middlewared/plugins/cloud_sync.py", line 650, in _validate
raise verrors
middlewared.service_exception.ValidationErrors: [EINVAL] cloud_sync_credentials_create.attributes.auth_version: Invalid choice: 3

How to replicate:

Create a new Cloud Credential
Select OpenStack Swift as the provider
Fill in required fields
Select any version of AuthVersion (v3 in this case)
Save
Edit the Cloud Crednials you just created
Note immediately that the AuthVersion field is not displaying v3, but rather the placeholder text "AuthVersion". Also note that some additional fields are now appearing under "Authentication Advanced Options": User Id , User Domain , Tentant Domain .
Press "Verify Credential", get the above error.

Additional obersvations.

If you subsequently re-select "v3" for Auth Version , the User Id , User Domain , and Tentant Domain fields disappear.
If you re-select "v3" for Auth Version and press "Verify Credntial" without saving, the following error occurs:

Error: 2021/05/17 09:28:11 Failed to create file system for "remote:": Bad Request

I did see ticket #109311 ( https://jira.ixsystems.com/browse/NAS-109311 ) which appears to be a similar bug, however this issue still exists in TrueNAS-12.0-U3.1