apache / apache/cloudstack

Default systemVM template is not downloaded to S3 secondary storage

Open
#9,002 6 comments 1 reaction 0 assignees Claimed by @Damans227 View on GitHub
component:secondary-storage component:systemvm-template no-issue-activity
Dominant language
Java
Stars
3.1k
Forks
1.4k
Avg merge
6d 19h
Merged PRs (30d)
32

Description

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
S3 Secondary storage, system VM template
~~~

##### CLOUDSTACK VERSION

~~~
4.19 with PR #8986
~~~

##### CONFIGURATION

MinIO S3 bucket configured
NFS staging storage

##### SUMMARY

Although the S3 secondary storage gets added with the fix in #8986 the default system VM template do not get downloaded. In the management server logs, I can see the _'DownloadProgressCommand'_ running but the file is not being downloaded. Note that the zone is created fresh and there is no SSVM to download the template. I am assuming there may be something missing to copy the systemVM template in the management server to the S3 bucket either via staging NFS or without it.

##### STEPS TO REPRODUCE

~~~
1. Create a MinIO S3 bucket
2. Add a zone with S3 secondary storage and NFS staging storage using the above bucket.
3. Launch the zone and wait for the system VM template status to become 'Ready'
~~~

##### EXPECTED RESULTS

~~~
SystemVM template is downloaded
~~~

##### ACTUAL RESULTS

~~~
SystemVM template is not downloaded
~~~

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with a MinIO S3 bucket, NFS staging storage, and a fresh zone as described, then review PR #8986 and the open PR #12426. Done means the default SystemVM template reaches S3 secondary storage and becomes Ready after the zone is launched.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.