Bug 57349 (ucs508meta) - UCS-5.0-8 Meta Bug
Summary: UCS-5.0-8 Meta Bug
Status: CLOSED FIXED
Alias: ucs508meta
Product: UCS
Classification: Unclassified
Component: General
Version: UCS 5.0
Hardware: All other
: P5 normal
Target Milestone: UCS 5.0-8
Assignee: Iván.Delgado
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 57267 57312 57350 ucs508updater ucs508changelog ucs508highlight ucs508manual 57355 ucs508errata 57357 ucs508jenkins ucs508images ucs508ec2 57378
Blocks:
  Show dependency tree / graph
 
Reported: 2024-05-28 13:31 CEST by Iván.Delgado
Modified: 2024-10-11 15:06 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Release Management
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Iván.Delgado univentionstaff 2024-05-28 13:31:34 CEST 
UCS 5.0-8 is scheduled for 2024-06-11.

After the release is published:
QA: UCS ISO + Appliances available as <https://www.univention.de/download/download-ucs/>
QA: UCS available on <http://updates.software-univention.de/>
QA 4: ftp/download/ucs-maintenance/$5.0-8.yaml exists.
QA 5: univention/dist/release-dates> is updated.
QA: EC2 AMIs are copied and public.
QA: EC2 AMI and KVM image is used by tests.

POST: Update the default branch in GitLab and GitHub.
POST: Re-seed UCS 5.0-8 Jenkins jobs to use the production mirror
POST: Re-seed UCS@school Jenkins jobs to be compatible to UCS 5.0-8
POST: Re-seed Jenkins jobs `App Appliance` to use the new release
Comment 1 Iván.Delgado univentionstaff 2024-06-12 07:53:18 CEST 
#!/bin/sh                                                                                                                                                                                                     ─╯
set -e -u
while read -r region ami
do
        aws ec2 modify-image-attribute --region "$region" --image-id "$ami" --launch-permission 'Add=[{Group=all}]'
        aws ec2 describe-images --region "$region" --image-id "$ami"
done <<EOF
us-east-2       ami-01eac8c91aa0f7c6d
us-east-1       ami-02e6438a14b0db0d5
us-west-1       ami-0d642fc142ee8138e
us-west-2       ami-082b435a2991ca9b5
ap-south-1      ami-014e50cb1767f86b5
ap-northeast-3  ami-02c20d8d85e7a892f
ap-northeast-2  ami-04eeb2f4e624e794d
ap-southeast-1  ami-0353c0488c898cd51
ap-southeast-2  ami-09e5cc027d911a9a9
ap-northeast-1  ami-033dbe87fdd202594
ca-central-1    ami-0a6408163e4320a18
eu-central-1    ami-0ce226910b2b56136
eu-west-1       ami-0165dba9749b1012f
eu-west-2       ami-026223d82a52a0950
eu-west-3       ami-06d54722c754488f2
eu-north-1      ami-00605fcb581d2e409
sa-east-1       ami-0df72b578a2863c96
EOF