Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1191869[details]
virt-builder traces
Description of problem:
When launching the following command on ARM aarch64 (mustang):
virt-builder fedora-23 -o ./f23 --arch aarch64 --root-password password:123456 --hostname f23guest --update
dnf -y --best upgrade is called and it looks it returns an error that prevents virt-builder from succeeding. As a consequence virt-builder fails creating the guest image:
virt-builder: error: dnf -y --best upgrade: command exited with an error
When launching the same command without --update and doing the "dnf -y --best upgrade" on the guest, the guest gets properly updated (although the same warning exists: Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]!=y). So the user experience is different.
The same command with fedora-24 works fine.
Version-Release number of selected component (if applicable):
virt-builder libguestfs-tools:
Version : 1.32.7
Release : 1.el7
How reproducible:
100%
Steps to Reproduce:
1. launch virt-builder fedora-23 -o ./f23 --arch aarch64 --root-password password:123456 --hostname f23guest --update -v -x
Actual results:
see attachement below.
Expected results:
Guest image is created and properly updated
Additional info:
(In reply to Eric Auger from comment #2)
> I put the virt-builder traces in the attachment. How can I output more
> information? Thanks Eric
this is question to virt-builder developers.
Comment 4Richard W.M. Jones
2016-08-18 16:54:17 UTC
Comment 5Richard W.M. Jones
2016-08-18 16:58:00 UTC
If you look at the logs, you'll see:
No '/dev/log' or 'logger' included for syslog logging
cat: /lib/firmware/amd-ucode/: Is a directory
No '/dev/log' or 'logger' included for syslog logging
Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]!=y
1810 blocks
and then dnf doesn't do any "Verify" lines. This probably
indicates that one of the %post scripts is bailing out, causing
dnf to (quite correctly) return an error. The error is picked
up by virt-builder because it indicates that the dnf update
command failed.
This is probably caused because of the very different kernels
in RHEL 7.3 (hence the appliance environment) and Fedora 23.
You can replace the --update option with the equivalent dnf
command, ignoring the error code, something like:
virt-builder --run-command 'dnf -y update ||:'
This is probably not something that we can fix in libguestfs.
It's a side effect of trying to modify a much newer guest using
a much older host kernel, and generally we recommend that you
always try to use a same/newer host when modifying guests, *or*
you explore the --firstboot options.
Created attachment 1191869 [details] virt-builder traces Description of problem: When launching the following command on ARM aarch64 (mustang): virt-builder fedora-23 -o ./f23 --arch aarch64 --root-password password:123456 --hostname f23guest --update dnf -y --best upgrade is called and it looks it returns an error that prevents virt-builder from succeeding. As a consequence virt-builder fails creating the guest image: virt-builder: error: dnf -y --best upgrade: command exited with an error When launching the same command without --update and doing the "dnf -y --best upgrade" on the guest, the guest gets properly updated (although the same warning exists: Disabling early microcode, because kernel does not support it. CONFIG_MICROCODE_[AMD|INTEL]!=y). So the user experience is different. The same command with fedora-24 works fine. Version-Release number of selected component (if applicable): virt-builder libguestfs-tools: Version : 1.32.7 Release : 1.el7 How reproducible: 100% Steps to Reproduce: 1. launch virt-builder fedora-23 -o ./f23 --arch aarch64 --root-password password:123456 --hostname f23guest --update -v -x Actual results: see attachement below. Expected results: Guest image is created and properly updated Additional info: