Open soyacz opened 5 months ago
@soyacz
Could be that we somehow going via the external API endpoint ?
And there's a way to force the client to connect locally ?
See: https://learn.microsoft.com/en-us/azure/api-management/troubleshoot-response-timeout-and-errors
Issue description
It started with failure of restarting VM, where we run reboot command on Azure:
later still problem was persisting failing to list resources with the same error which led to missing logs and failure in resources cleanup. Nothing specific was present in RG activity log.
Impact
test failure and missing logs and leave resources up.
How frequently does it reproduce?
First time seen
Installation details
Kernel Version: 5.15.0-1053-azure Scylla version (or git commit hash):
5.5.0~dev-20240119.b1ba904c4977
with build-id7a5829efb1f6ef7b467d2dc837300abcc0b739c8
Cluster size: 4 nodes (Standard_L16s_v3)
Scylla Nodes used in this run:
OS / Image:
/subscriptions/6c268694-47ab-43ab-b306-3c5514bc4112/resourceGroups/SCYLLA-IMAGES/providers/Microsoft.Compute/images/scylla-5.5.0-dev-x86_64-2024-01-20T02-21-36
(azure: undefined_region)Test:
longevity-1tb-5days-azure-test
Test id:bd04be7c-8fd7-4d51-b683-57c4491dcae3
Test name:scylla-master/longevity/longevity-1tb-5days-azure-test
Test config file(s):Logs and commands
- Restore Monitor Stack command: `$ hydra investigate show-monitor bd04be7c-8fd7-4d51-b683-57c4491dcae3` - Restore monitor on AWS instance using [Jenkins job](https://jenkins.scylladb.com/view/QA/job/QA-tools/job/hydra-show-monitor/parambuild/?test_id=bd04be7c-8fd7-4d51-b683-57c4491dcae3) - Show all stored logs command: `$ hydra investigate show-logs bd04be7c-8fd7-4d51-b683-57c4491dcae3` ## Logs: *No logs captured during this run.* [Jenkins job URL](https://jenkins.scylladb.com/job/scylla-master/job/longevity/job/longevity-1tb-5days-azure-test/34/) [Argus](https://argus.scylladb.com/test/d03f9d55-942a-4f66-ae48-9d35d59a59e2/runs?additionalRuns[]=bd04be7c-8fd7-4d51-b683-57c4491dcae3)