Open Stack

On Thu, Feb 9, 2017 at 12:22 AM, Ian Wienand <iwienand at redhat.com> wrote:
> Hi
>
> diskimage-builder has been working on a feature/v2 branch
> incorporating some largely internal changes to the way it finds and
> calls elements, enhancements to partitioning and removal of some
> long-deprecated elements.  We have just tagged 2.0.0rc1 and are
> requesting testing by interested parties.
>

I am too late, but it is a good place to mention that 2.0.0 introduced
a regression that ends up breaking image build on ppc64 platform
somehwere within bootloader element.

Error trace:

2017-03-17 15:54:37,317 INFO nodepool.image.build.devstack-xenial: +
[[ ppc64el =~ ppc ]]
2017-03-17 15:54:37,317 INFO nodepool.image.build.devstack-xenial: +
/usr/sbin/grub-install --modules=part_msdos --force /dev/loop0
--no-nvram
2017-03-17 15:54:37,369 INFO nodepool.image.build.devstack-xenial:
Installing for powerpc-ieee1275 platform.
2017-03-17 15:54:45,912 INFO nodepool.image.build.devstack-xenial:
/usr/sbin/grub-install: warning: unknown device type loop0p1
2017-03-17 15:54:45,913 INFO nodepool.image.build.devstack-xenial: .
2017-03-17 15:54:45,987 INFO nodepool.image.build.devstack-xenial:
/usr/sbin/grub-install: error: the chosen partition is not a PReP
partition.

On 1.2.8, the cmdline was ` /usr/sbin/grub-install
--modules=part_msdos --force /dev/loop0p1 --no-nvram`. I do not know
yet why grub-install thinks it should still use loop0p1 on 2.1.0.

I have not dug too deep into it, ended up downgrading
diskimage-builder to 1.2.8. Simple downgrade would not work, because
1.2.8 would now fail with dib-run-parts binary missing. So I also had
to copy dib-run-parts from 2.1.0. Maybe installing from source and
pinning 1.2.8 would have been a better strategy.

---
Mikhail Medvedev (mmedvede)
IBM