An error in VMware Communities was fixed on Sept 15 at 11am Pacific, and all functions of VMware Communities are now available and the site is running with no known errors.
From Sept 14 early afternoon Pacific until Sept 15 11am Pacific, the nodes in the cluster running VMware Communities were not connected properly. During this time, different data displayed depending on which node in the cluster a user was connected to. No data is known to be lost, and once the nodes were reconnected, normal behavior returned. The cause of the problem was human error, and we are reviewing internal processes to make sure this does not happen again.
If site visitors do see any issues, please contact RDellimmagine or post to Communities Website Feedback.
Update 9/16 AM: It appears there are some data issues with threads posted before the above error was fixed. My dev team is investigating, and I'll update here when I have more information. I apologize for the problems this is causing. Regards, Robert
Update 9/16 PM: We fixed a couple of places where the above issue caused messages to point to the incorrect parent messages. Also, I believe that the threads-out-of-chronological-order issue resolved itself. This issue persisted a while after the fix was made because it took some time for the cache to catch up with the site once all nodes rejoined the cluster. Regards, Robert
- Contributors:
-
Corey_R
-
JohnTroyer
-
ericni
-
RDellimmagine
-
Badsah