Rebase diskimage-builder to 3.1.0 to pick up latest fixes.
When 16.1 switches to upstream 3.1.0 will there also be a downstream import of upstream changes since 3.1.0? (like what is happening with 16.2?) If not, I'll have to redo quite a few downstream backports to put back fixes that avoid regressions. I'll do a check on the priority of bugs fixed since 16.0 which may have regressed by distributing the 3.0.1 package, this may justify being a blocker for 16.1.6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:3762