Update to 9.1.0 breaks access to Linode Object Storage

[toddler-boy]

Longtime fan here, but noticed a problem reported by a few others over on Linode/Akamai Cloud Computing

Describe the bug
Updating to Cyberduck version 9.1.0 seems to break access to buckets on Linode Object Storage. After connecting with existing, previously working creds, it will not show any buckets.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade to newest version of Cyberduck
2. Use existing credentials to access buckets on Linode Object Storage platform
3. Buckets do not load

Expected behavior
Buckets load and are accessible via UI regardless of version.

[dkocher]

Can you point me to the discussion(s) in the forum.

[TheLordsKnight]

I ran into this issue connecting to my Linode Object Storage account. I was troubleshooting the issue with another user in my company. They were using version 9.1.0 for Mac and it would successfully connect but would not list the storage buckets. It was working for me using the same credentials on 9.0.3 for Windows. Mine had said there was an update, so I went ahead and updated to the same version as the other user. Now when I tried using the same saved credentials in 9.1.0 it connected but would not show the buckets. I reverted to 9.0.3 and it started working again.

[dkocher]

It would be great if you can provide a debug log.

[TheLordsKnight]

I updated back to 9.1.0 and tried again with debug logging turned on. Here is the generated debug log.
cyberduck.log

[dkocher]

Thanks @TheLordsKnight. Relevant log output is

2024-12-11 14:17:57,404 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-1aa21ae2-e919-4b51-a46a-0de1f4bd16b2-1637347616', type=[directory, volume]} in region default
2024-12-11 14:17:57,559 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-9351fd80-5f94-4203-a8f1-340add57c0d9-1633442104', type=[directory, volume]} in region default
2024-12-11 14:17:57,724 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-eeaf0813-989a-4274-bc75-0e8a806791a1-1637347585', type=[directory, volume]} in region default
2024-12-11 14:17:57,877 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-a9121917-c4a1-4b3e-9e58-8ab5a96614c8-1637348237', type=[directory, volume]} in region default
2024-12-11 14:17:58,038 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-d1a7d3e1-e799-41f1-98e5-944bf57dd602-1637347634', type=[directory, volume]} in region default
2024-12-11 14:17:58,243 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-fef6e438-1381-4d64-9d8d-ef88b2bd33ec-1637347661', type=[directory, volume]} in region default
2024-12-11 14:17:58,289 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-1aa21ae2-e919-4b51-a46a-0de1f4bd16b2-1637347616', type=[directory, volume]} in region default
2024-12-11 14:17:58,289 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-9351fd80-5f94-4203-a8f1-340add57c0d9-1633442104', type=[directory, volume]} in region default
2024-12-11 14:17:58,289 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-eeaf0813-989a-4274-bc75-0e8a806791a1-1637347585', type=[directory, volume]} in region default
2024-12-11 14:17:58,290 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-a9121917-c4a1-4b3e-9e58-8ab5a96614c8-1637348237', type=[directory, volume]} in region default
2024-12-11 14:17:58,290 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-d1a7d3e1-e799-41f1-98e5-944bf57dd602-1637347634', type=[directory, volume]} in region default
2024-12-11 14:17:58,290 [background-5] WARN  ch.cyberduck.core.s3.S3BucketListService - Skip bucket Path{path='/redacted-fef6e438-1381-4d64-9d8d-ef88b2bd33ec-1637347661', type=[directory, volume]} in region default

With e4de4f8 buckets not matching the region identifier from the connection profile are skipped. We would expect the service would return the bucket location matching the region name us-mia-1 instead of default.

[dkocher]

The actual regression is from ea534ae. Previously no lookup for the region of the bucket was made for profiles with a Region set.