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
Due to recent cpu resource crunch in lab regions, i noticed the below error on the Elektra dashboard :
`Elektron::Errors::Request
Failed to open TCP connection to glance.monsoon3.svc.kubernetes.qa-de-3.cloud.sap:9292 (Connection refused - connect(2) for "glance.monsoon3.svc.kubernetes.qa-de-3.cloud.sap" port 9292)
There are no further details available. Sorry!`
The text was updated successfully, but these errors were encountered:
As you said there was a problem that not enough resource where available in K8s. This is a very seldom edge case and I am not sure what we should do here?
there were instances in the past even when the glance-api pods were in crashloop due to maintenance controller. Was wondering what could support do if this issue occurs during off work hours.
Do we know how or why elektra fetches this message from ? this is generated on the home page (meaning none can access the dashboard or their services from UI) not when clicking server snapshots or images.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you need to keep this issue open set label of this issue to 'neverstale'. Thank you for your contributions.
Hi Team,
Due to recent cpu resource crunch in lab regions, i noticed the below error on the Elektra dashboard :
`Elektron::Errors::Request
Failed to open TCP connection to glance.monsoon3.svc.kubernetes.qa-de-3.cloud.sap:9292 (Connection refused - connect(2) for "glance.monsoon3.svc.kubernetes.qa-de-3.cloud.sap" port 9292)
There are no further details available. Sorry!`
The text was updated successfully, but these errors were encountered: