Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot copy template into S3 storage #1076

Open
1 task done
phm07 opened this issue Jan 17, 2023 · 2 comments
Open
1 task done

Cannot copy template into S3 storage #1076

phm07 opened this issue Jan 17, 2023 · 2 comments
Labels
s: needs testing The issue needs to be tested first to get more information t: bug Something isn't working as intended v: 4.X This pull should be included in the 4.0 release

Comments

@phm07
Copy link

phm07 commented Jan 17, 2023

Stacktrace

https://gist.github.com/pauhull/aa334eb6b253f664ac84288636273646

Actions to reproduce

  • Use CloudNet-Storage-S3 module for template storage
  • Copy template into storage

CloudNet version

[17.01 18:50:12.528] INFO:  
[17.01 18:50:12.534] INFO: CloudNet Blizzard 4.0.0-RC5 4ec2a84d
[17.01 18:50:12.536] INFO: Discord: <https://discord.cloudnetservice.eu/>
[17.01 18:50:12.538] INFO:  
[17.01 18:50:12.539] INFO: ClusterId: b524d946-****-45c6-****-4a8fcdf47225
[17.01 18:50:12.541] INFO: NodeId: Node-1
[17.01 18:50:12.553] INFO: Head-NodeId: Node-2
[17.01 18:50:12.557] INFO: CPU usage: (P/S) 2.05/100/100%
[17.01 18:50:12.560] INFO: Node services memory allocation (U/R/M): 10240/10240/25600 MB
[17.01 18:50:12.563] INFO: Threads: 79
[17.01 18:50:12.568] INFO: Heap usage: 78/456MB
[17.01 18:50:12.572] INFO: JVM: Debian 17 (OpenJDK 64-Bit Server VM 17.0.4+8-Debian-1deb11u1)
[17.01 18:50:12.577] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: beta
[17.01 18:50:12.580] INFO: 

Other

When trying to copy a local template into S3 storage the attached error occurs. No files are copied altough the command says it completed successfully.

The storage server is a locally hosted MinIO instance.
Output of minio --version:

minio version RELEASE.2023-01-12T02-06-16Z (commit-id=7bc95c47a322971aff7d4d4c270dcf28a933e84b)
Runtime: go1.19.4 linux/amd64
License: GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>
Copyright: 2015-2023 MinIO, Inc.

Contents of /modules/CloudNet-Storage-S3/config.json:

{
  "name": "s3",
  "bucket": "cloudnet",
  "region": "eu",
  "accessKey": "<redacted>",
  "secretKey": "<redacted>",
  "endpointOverride": "https://storage.novusmc.eu/",
  "accelerateMode": false,
  "pathStyleAccess": true,
  "chunkedEncoding": false,
  "checksumValidation": false,
  "dualstackEndpointEnabled": false
}

Issue uniqueness

  • Yes, this issue is unique. There are no similar issues.
@phm07 phm07 added s: needs triage Issue waiting for triage t: bug Something isn't working as intended labels Jan 17, 2023
@derklaro derklaro added v: 4.X This pull should be included in the 4.0 release s: needs testing The issue needs to be tested first to get more information and removed s: needs triage Issue waiting for triage labels Feb 15, 2023
@derklaro derklaro moved this to 📋 Backlog in v4 Roadmap Feb 15, 2023
@GiantTreeLP
Copy link
Member

GiantTreeLP commented Jul 26, 2024

FWIW I have found that the success message is printed, even if the internal deployment step, ie. the step that uploads the template to the S3 bucket, fails:

targetStorage.deploy(targetTemplate, stream);
source.sendMessage(I18n.trans("command-template-copy-success", sourceTemplate, targetTemplate));

@GiantTreeLP
Copy link
Member

Due to the fact that the gist is no longer available, I can not analyze the stacktrace anymore.

Do you happen to know, whether the region in MinIO is set correctly?

A quick test on my setup revealed that S3 templates do indeed work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
s: needs testing The issue needs to be tested first to get more information t: bug Something isn't working as intended v: 4.X This pull should be included in the 4.0 release
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants