07-03-2019, 08:08 PM
Hello everyone. Thank you for your patience while we worked through the issue with this update. For a short time, authentication was not working. Next, a handful of developer accounts could not access the cdb_Users table. The table appeared empty. The table was accepting changes and new users. These same developers could not see the changes though. We were affected by this issue as well.
I am happy to say that we have corrected the problem. Here is a post mortem for you.
Yesterday, we pushed an update to LiveCloud Manager. A single but necessary behavior file was accidentally not pushed to our auto-update system. The result was that LCM could not authenticate on any region. The forgotten was found and pushed.
We thought we had it all going well. But, the San Franciso Region had one more issue. The User instance that manages this region's user data had corrupted data in its config file. It took us a while to realize this corruption was there. The corrupted data has been cleared out. The instance is running and working well.
Please restart your LCM to ensure you have the latest update. Try accessing your User table.
We appreciate everyone's patience while we worked through this. A more detailed post is coming that details what the update contains.
I am happy to say that we have corrected the problem. Here is a post mortem for you.
Yesterday, we pushed an update to LiveCloud Manager. A single but necessary behavior file was accidentally not pushed to our auto-update system. The result was that LCM could not authenticate on any region. The forgotten was found and pushed.
We thought we had it all going well. But, the San Franciso Region had one more issue. The User instance that manages this region's user data had corrupted data in its config file. It took us a while to realize this corruption was there. The corrupted data has been cleared out. The instance is running and working well.
Please restart your LCM to ensure you have the latest update. Try accessing your User table.
We appreciate everyone's patience while we worked through this. A more detailed post is coming that details what the update contains.