| 2019-12-17 11:39:03 |
Łukasz Zemczak |
bug |
|
|
added bug |
| 2019-12-17 11:39:07 |
Łukasz Zemczak |
ubuntu-image: status |
New |
In Progress |
|
| 2019-12-17 11:39:09 |
Łukasz Zemczak |
ubuntu-image: milestone |
|
1.9 |
|
| 2019-12-17 11:39:12 |
Łukasz Zemczak |
ubuntu-image: assignee |
|
Łukasz Zemczak (sil2100) |
|
| 2019-12-17 11:44:27 |
Łukasz Zemczak |
bug task added |
|
livecd-rootfs (Ubuntu) |
|
| 2019-12-17 11:48:25 |
Łukasz Zemczak |
merge proposal linked |
|
https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/+git/livecd-rootfs/+merge/376790 |
|
| 2019-12-20 19:41:44 |
Francis Ginther |
tags |
|
id-5de55a9fab643c64680a854b |
|
| 2020-01-15 11:17:19 |
Łukasz Zemczak |
livecd-rootfs (Ubuntu): status |
New |
In Progress |
|
| 2020-01-15 11:17:22 |
Łukasz Zemczak |
livecd-rootfs (Ubuntu): assignee |
|
Łukasz Zemczak (sil2100) |
|
| 2020-01-15 11:18:02 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-01-15 11:18:02 |
Łukasz Zemczak |
bug task added |
|
livecd-rootfs (Ubuntu Bionic) |
|
| 2020-01-15 11:18:10 |
Łukasz Zemczak |
livecd-rootfs (Ubuntu Bionic): assignee |
|
Łukasz Zemczak (sil2100) |
|
| 2020-01-15 11:18:13 |
Łukasz Zemczak |
livecd-rootfs (Ubuntu): importance |
Undecided |
High |
|
| 2020-01-15 11:18:15 |
Łukasz Zemczak |
ubuntu-image: importance |
Undecided |
High |
|
| 2020-01-15 11:18:17 |
Łukasz Zemczak |
livecd-rootfs (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2020-01-15 11:18:19 |
Łukasz Zemczak |
livecd-rootfs (Ubuntu): importance |
High |
Medium |
|
| 2020-01-21 17:09:36 |
Łukasz Zemczak |
description |
Our installer-based images (those touched by debian-cd) get a .disk/info file written on the rootfs that contains useful information such as the build timestamp. We do not have anything like that available for our u-i images, while for preinstalled images sometimes it is very important to know from which batch of images the given one comes. |
[Impact]
Our installer-based images (those touched by debian-cd) get a .disk/info file written on the rootfs that contains useful information such as the build timestamp. We do not have anything like that available for our u-i images, while for preinstalled images sometimes it is very important to know from which batch of images the given one comes.
We have decided that this will be very useful to have for our 18.04.4 images.
[Test Case]
For ubuntu-image changes:
Build a classic bionic image with something like:
ubuntu-image classic -d -p ubuntu-cpc -O out/ -s bionic --cloud-init user-data --disk-info disk-info-file path/to/gadget/prime
Boot up the image on kvm, check if /.disk/info is populated.
For all the changes:
Build a new classic bionic image via cdimage (raspi3 for instance). Boot it up (or mount it) and confirm that /.disk/info has the corresponding datestamp serial number in it.
[Regression Potential]
Besides classic images failing to build on cdimage, I don't think there's any other scenario I can think of. Any regression would most likely cause a build failure. |
|
| 2020-01-21 17:09:43 |
Łukasz Zemczak |
bug task added |
|
ubuntu-image (Ubuntu) |
|
| 2020-01-21 17:12:45 |
Łukasz Zemczak |
description |
[Impact]
Our installer-based images (those touched by debian-cd) get a .disk/info file written on the rootfs that contains useful information such as the build timestamp. We do not have anything like that available for our u-i images, while for preinstalled images sometimes it is very important to know from which batch of images the given one comes.
We have decided that this will be very useful to have for our 18.04.4 images.
[Test Case]
For ubuntu-image changes:
Build a classic bionic image with something like:
ubuntu-image classic -d -p ubuntu-cpc -O out/ -s bionic --cloud-init user-data --disk-info disk-info-file path/to/gadget/prime
Boot up the image on kvm, check if /.disk/info is populated.
For all the changes:
Build a new classic bionic image via cdimage (raspi3 for instance). Boot it up (or mount it) and confirm that /.disk/info has the corresponding datestamp serial number in it.
[Regression Potential]
Besides classic images failing to build on cdimage, I don't think there's any other scenario I can think of. Any regression would most likely cause a build failure. |
[Impact]
Our installer-based images (those touched by debian-cd) get a .disk/info file written on the rootfs that contains useful information such as the build timestamp. We do not have anything like that available for our u-i images, while for preinstalled images sometimes it is very important to know from which batch of images the given one comes.
We have decided that this will be very useful to have for our 18.04.4 images.
[Test Case]
For ubuntu-image changes:
Build a classic bionic image with something like:
ubuntu-image classic -d -p ubuntu-cpc -O out/ -s bionic --cloud-init user-data --disk-info disk-info-file path/to/gadget/prime
Boot up the image on kvm, check if /.disk/info is populated.
For all the changes:
Build a new classic bionic image via cdimage (raspi3 for instance). Boot it up (or mount it) and confirm that /.disk/info has the corresponding datestamp serial number in it.
[Regression Potential]
Besides classic images failing to build on cdimage, I don't think there's any other scenario I can think of. Any regression would most likely cause a build failure.
[Other SRU Info]
I am submitting a bionic ubuntu-image SRU without releasing the same changes for focal as I was originally planning to release this feature as part of 1.9. The exact same changes are landed in master, and will be released with 1.9 when it's ready, so there's certainty that it will not be missed. I didn't feel like doing another intermediate release for focal is strictly required - but I can do so if someone requires it. |
|
| 2020-01-22 07:58:31 |
Brian Murray |
ubuntu-image (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2020-01-22 07:58:34 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-01-22 07:58:37 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-01-22 07:58:41 |
Brian Murray |
tags |
id-5de55a9fab643c64680a854b |
id-5de55a9fab643c64680a854b verification-needed verification-needed-bionic |
|
| 2020-01-22 09:32:03 |
Brian Murray |
livecd-rootfs (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2020-01-22 16:27:33 |
Łukasz Zemczak |
ubuntu-image (Ubuntu): status |
New |
In Progress |
|
| 2020-01-22 16:27:46 |
Łukasz Zemczak |
ubuntu-image: status |
In Progress |
Fix Committed |
|
| 2020-01-22 16:28:16 |
Łukasz Zemczak |
bug task added |
|
ubuntu-cdimage |
|
| 2020-01-22 16:34:10 |
Łukasz Zemczak |
ubuntu-cdimage: status |
New |
Fix Released |
|
| 2020-01-28 21:26:17 |
Brian Murray |
tags |
id-5de55a9fab643c64680a854b verification-needed verification-needed-bionic |
id-5de55a9fab643c64680a854b verification-done-bionic verification-needed |
|
| 2020-01-30 09:24:18 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-01-30 09:34:19 |
Launchpad Janitor |
livecd-rootfs (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-01-30 09:44:25 |
Launchpad Janitor |
ubuntu-image (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-02-21 11:42:59 |
Paride Legovini |
bug |
|
|
added subscriber Paride Legovini |
| 2020-02-28 03:33:00 |
Launchpad Janitor |
ubuntu-image (Ubuntu): status |
In Progress |
Fix Released |
|
| 2020-04-28 08:42:27 |
Łukasz Zemczak |
ubuntu-image: status |
Fix Committed |
Fix Released |
|
