[Bug 1856684] Re: Populate .disk/info in ubuntu-image built images

[Łukasz Zemczak]

** Description changed:

+ [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.

** Also affects: ubuntu-image (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

  [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.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1856684

Title:
  Populate .disk/info in ubuntu-image built images

Status in Ubuntu Image:
  In Progress
Status in livecd-rootfs package in Ubuntu:
  In Progress
Status in ubuntu-image package in Ubuntu:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in ubuntu-image source package in Bionic:
  New

Bug 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.

  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-image/+bug/1856684/+subscriptions