The reason why I think I had the same issuse is the fact that when you check the mysqld.log in the job [1] you can see that all cloud services have issues using DB. After upgrade on my env the cloud more or less worked, but apparently there was a network issue, which in my case made redeploy after FFU fail 100% time on the Keystone check step.
The reason why I think I had the same issuse is the fact that when you check the mysqld.log in the job [1] you can see that all cloud services have issues using DB. After upgrade on my env the cloud more or less worked, but apparently there was a network issue, which in my case made redeploy after FFU fail 100% time on the Keystone check step.
[1] https:/ /e453f1d8808c5b 6bd184- 223d8b88d73ea59 070ac36b627fdc3 bc.ssl. cf2.rackcdn. com/739457/ 27/check/ tripleo- ci-centos- 8-standalone- upgrade- ussuri/ ad8724d/ logs/undercloud /var/log/ containers/ mysql/mysqld. log