#9240 Update published Fedora 31 cloud images
Closed: Get back later by humaton. Opened by pbrobinson.

  • Describe the issue
    Fedora 31 shipped with the 5.3.7 kernel, we're now at 5.4.18 (ish) and there's been a number of CVEs and related so it would be advisable to publish a new set of stable cloud images to AWS and related locations.

  • When do you need this? (YYYY/MM/DD)
    ASAP

  • When is this no longer needed or useful? (YYYY/MM/DD)
    Until the next round

  • If we cannot complete your request, what is the impact?
    Current images stay


Can we also update the aarch64 AWS regions when this happens:

  • Drop "US West (N. California)" - not valid for aarch64 A1 instances
  • Add Singapore - New for aarch64 A1 instances

we've wanted to do this for some time: https://pagure.io/cloud-sig/issue/138

recently there has been a push by @jdoss and others to take the appropriate steps to make it maintainable.

I'm well aware of that ticket, I wouldn't say any of that was recent, last comment was 2 years.

The current process has been always a manual one to tag/push updated images as "stable" by rel-eng, that's what I'm requesting here, not reinvent the world. That can happen on the other ticket.

But there is a lot of little stuff that needs to happen, like updating the website and making sure image uploads don't fail. Like I said there has been recent interest by a handful of people to start working on this, we'll see if it goes anywhere.

In the 04/14/2020 cloud sig community meeting we discussed what it would take to ship cloud images more regularly.

16:27:38 <dustymabe> #info we agree we would all like to upload and release 
                     cloud images more often. releng has agreed to try to 
                     achieve the following items: 1) copy files to a more 
                     permanent location 2) get them on some mirrors 3) 
                     update website 4) sending release email. Cloud working
                     group will try to do the following items: 1) uploading
                     to clouds 2) running tests on clouds 3) promoting release
                     candidates

So the items for releng are:

  1. copy files to a more permanent location
  2. get them on some mirrors
  3. update website
  4. sending release email

The action items for the cloud working group can be followed in these open tickets:

  • https://pagure.io/cloud-sig/issue/301
  • https://pagure.io/cloud-sig/issue/302
  • https://pagure.io/cloud-sig/issue/303

Closing, if there is anything we can do please reopen this issue.

Metadata Update from @humaton:
- Issue close_status updated to: Get back later
- Issue status updated to: Closed (was: Open)

Metadata