Comment 32 for bug 1846789

Thanks, I missed that. Trying with the above patch.

On my single node Train deploy I also see:

```
keystone/keystone-apache-public-error.log:2020-06-29 17:11:21.562830 File "/usr/lib/python2.7/site-packages/keystone/receipt/providers/fernet/core.py", line
 45, in __init__
keystone/keystone-apache-public-error.log:2020-06-29 17:11:21.562879 'Fernet keys.') % subs)
keystone/keystone-apache-public-error.log:2020-06-29 17:11:21.562902 SystemExit: /etc/keystone/fernet-keys/ does not contain keys, use keystone-manage fernet_
setup to create Fernet keys.
keystone/keystone-apache-public-error.log:2020-06-29 17:11:25.810353 File "/usr/lib/python2.7/site-packages/keystone/receipt/providers/fernet/core.py", line
 45, in __init__
keystone/keystone-apache-public-error.log:2020-06-29 17:11:25.810403 'Fernet keys.') % subs)
keystone/keystone-apache-public-error.log:2020-06-29 17:11:25.810427 SystemExit: /etc/keystone/fernet-keys/ does not contain keys, use keystone-manage fernet_
setup to create Fernet keys.
```

With the following fernet-keys folder in the container (but perhaps not when Keystone started):

(keystone)[root@controller1 fernet-keys]# ls -la
total 8
drwxrwx--- 2 keystone keystone 24 Jun 29 17:11 .
drwxr-x--- 1 root keystone 46 Jun 30 08:30 ..
-rw------- 1 keystone keystone 44 Jun 29 17:11 0
-rw------- 1 keystone keystone 44 Jun 29 17:11 1