Comment 14 for bug 1874381

I redeployed the system where this failures was original observed and recreated the issue.
Running 'sudo vgck --updatemetadata s5lp8-vg' did work around this bug, when run after the upgrade but prior to the reboot.

Here is the vgdisplay output requested by Steve:

ubuntu@s5lp8:~$ sudo vgdisplay
  --- Volume group ---
  VG Name s5lp8-vg
  System ID
  Format lvm2
  Metadata Areas 1
  Metadata Sequence No 4
  VG Access read/write
  VG Status resizable
  MAX LV 0
  Cur LV 3
  Open LV 3
  Max PV 0
  Cur PV 1
  Act PV 1
  VG Size <64.00 GiB
  PE Size 4.00 MiB
  Total PE 16383
  Alloc PE / Size 16377 / 63.97 GiB
  Free PE / Size 6 / 24.00 MiB
  VG UUID 3B7wkv-AIvn-5A7N-pmWB-7y7h-ylkd-jUIfRd