You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On beta.codenvy.com, the factory is failing to load properly the workspace. The machine is not starting and there is no error message and the logs are empty.
Reproduction Steps:
Click on a factory
The factory loading screen is displayed but nothing happen
Expected behavior:
After a certain period of time, the product is displaying an error message to the user. Moreover, if there is a problem it should be possible to analyze it from the logs.
Observed behavior:
The loading screen is hanging forever. No error message is displayed
The logs are completely empty.
Codenvy version: 4.6.2
Additional information:
After initial analyze, it seems the problem is due to a connectivity trouble with DockerHub.
Problem only started happening recently, didn't happen in an older version of Codenvy: Yes
Problem can be reliably reproduced: Yes at this moment
The text was updated successfully, but these errors were encountered:
There is not output for "Workspace initializing...". And the outputs for "Start workspace runtime" didn't show up before a long time (and sometime does not display at all).
On beta.codenvy.com, the factory is failing to load properly the workspace. The machine is not starting and there is no error message and the logs are empty.
Reproduction Steps:
Expected behavior:
After a certain period of time, the product is displaying an error message to the user. Moreover, if there is a problem it should be possible to analyze it from the logs.
Observed behavior:
The loading screen is hanging forever. No error message is displayed
The logs are completely empty.
Codenvy version: 4.6.2
Additional information:
After initial analyze, it seems the problem is due to a connectivity trouble with DockerHub.
Problem only started happening recently, didn't happen in an older version of Codenvy: Yes
Problem can be reliably reproduced: Yes at this moment
The text was updated successfully, but these errors were encountered: