Skip to content

RHCOS 4.11 ppc64le test failures due to libguestfs errors? #720

@miabbott

Description

@miabbott

There's a lot going on in the ppc64le RHCOS 4.11 build:

libguestfs failure messages:

Details

libguestfs: error: appliance closed the connection unexpectedly.
This usually means the libguestfs appliance crashed.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
libguestfs: error: /usr/bin/qemu-system-ppc64 exited with error status 1.
To see full error messages you may need to enable debugging.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
libguestfs: error: guestfs_launch failed.
This usually means the libguestfs appliance failed to start or crashed.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
2022-02-16T14:23:39Z kola: retryloop: failed to bring up machines: ignition injection with guestfs failed: guestfish launch failed: exit status 1
libguestfs: error: appliance closed the connection unexpectedly.
This usually means the libguestfs appliance crashed.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
libguestfs: error: /usr/bin/qemu-system-ppc64 exited with error status 1.
To see full error messages you may need to enable debugging.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
libguestfs: error: guestfs_launch failed.
This usually means the libguestfs appliance failed to start or crashed.
Do:
  export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
and run the command again.  For further information, read:
  http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs
You can also run 'libguestfs-test-tool' and post the *complete* output
into a bug report or message to the libguestfs mailing list.
2022-02-16T14:23:41Z kola: retryloop: failed to bring up machines: ignition injection with guestfs failed: guestfish launch failed: exit status 1
--- FAIL: ext.config.shared.networking.prefer-ignition-networking (5.59s)
        harness.go:1381: Cluster failed starting machines: ignition injection with guestfs failed: guestfish launch failed: exit status 1

List of failed tests:

  • FAIL: ext.config.shared.networking.prefer-ignition-networking (5.59s)
  • FAIL: ext.config.shared.networking.mtu-on-bond-kargs (1.97s)
  • FAIL: coreos.ignition.mount.partitions (682.80s)
  • FAIL: ext.config.shared.networking.force-persist-ip
  • FAIL: coreos.ignition.mount.disks
  • FAIL: coreos.boot-mirror
  • FAIL: coreos.boot-mirror.luks
  • FAIL: ext.config.shared.reboot
  • FAIL: ext.config.shared.kdump.crash

Build log - https://url.corp.redhat.com/f0f692f

kola_artifacts.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions