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
{{ message }}
Repository navigation
Commit 405cdf4
Browse filesBrowse the repository at this point in the historyBrowse files
engine-schema: use new systemvm template names in metadata and export script
For 24.x and later, templateConfig.sh generates metadata.ini with the
templates in the directory named after the major version and with
major.minor in the file and template names (24/systemvmtemplate-24.0-...,
systemvm-kvm-24.0-x86_64), so that the checksums are found in
sha512sum.txt. The version in metadata.ini is unchanged (24.0.0).
export-templates.sh uses major.minor for the template file names too.
Legacy (4.x) behavior is unchanged. Tests are updated and extended.
if [[ "$subversion1"-ge"$NEW_VERSIONING_CUTOVER_MAJOR_VERSION" ]];then
35
33
# New versioning (major.minor.security): the third component is the
36
34
# security release itself, there is no separate patch component. A
@@ -40,11 +38,17 @@ function getTemplateVersion() {
40
38
echo"Invalid version '${projVersion}': major versions at or above ${NEW_VERSIONING_CUTOVER_MAJOR_VERSION} do not support a 4-component major.minor.patch.security format">&2
41
39
exit 1
42
40
fi
43
-
export FULL_VERSION="${VERSION}"
41
+
# The templates are in the directory named after the major version (24),
42
+
# and the file names contain major.minor (24.0), like 4.22 and 4.22.0 before
assert_eq "metadata.ini cutover security release uses the same template""https://download.cloudstack.org/systemvm//24/systemvmtemplate-24.0-x86_64-kvm.qcow2.bz2""$actual"
0 commit comments