Open AlexVlan opened 1 month ago
@AlexVlan just to clarify - does the problem happen when you use the image with MAAS? Or are you trying to use the image with proxmox?
@AlexVlan just to clarify - does the problem happen when you use the image with MAAS? Or are you trying to use the image with proxmox?
when I use MAAS. I think this problem is due to the fact that when I build the image on my PC
(sudo PACKER_LOG=1 packer build centos9-stream.pkr.hcl or make)
,
I cannot use the disk sda
during the build, e.g.
bootloader --location=mbr --driveorder=“sda” --timeout=1
.
get error
==> qemu.centos9-stream (shell-local): ++ (( ++retries > 10 ))
==> qemu.centos9-stream (shell-local): ++ '[' -f /tmp/packer-maas-7iZo/p1/nbd ']'
==> qemu.centos9-stream (shell-local): ++ sleep 1
==> qemu.centos9-stream (shell-local): ++ (( ++retries > 10 ))
==> qemu.centos9-stream (shell-local): ++ return 1
==> qemu.centos9-stream (shell-local): + cleanup
==> qemu.centos9-stream (shell-local): + for dev in "${TMP_DIR}"/p*/ "${TMP_DIR}"/disk/ "${TMP_DIR}"/boot/
==> qemu.centos9-stream (shell-local): + dev=/tmp/packer-maas-7iZo/p1
==> qemu.centos9-stream (shell-local): + '[' -d /tmp/packer-maas-7iZo/p1 ']'
==> qemu.centos9-stream (shell-local): + fusermount -u -z /tmp/packer-maas-7iZo/p1
==> qemu.centos9-stream (shell-local): fusermount: failed to unmount /tmp/packer-maas-7iZo/p1: Invalid argument
2024/09/19 15:41:44 packer-post-processor-shell-local plugin: error: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
2024/09/19 15:41:44 [INFO] (telemetry) ending shell-local
2024/09/19 15:41:44 Deleting original artifact for build 'qemu.centos9-stream'
* Post-processor failed: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> Wait completed after 5 minutes 7 seconds
2024/09/19 15:41:44 machine readable: error-count []string{"1"}
==> Some builds didn't complete successfully and had errors:
2024/09/19 15:41:44 machine readable: qemu.centos9-stream,error []string{"1 error(s) occurred:\n\n* Post-processor failed: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]"}
* Post-processor failed: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]
==> Builds finished but no artifacts were created.
Build 'qemu.centos9-stream' errored after 5 minutes 7 seconds: 1 error(s) occurred:
2024/09/19 15:41:44 [INFO] (telemetry) Finalizing.```
It dont find such a disk. But I can
t using that image(with the '''vda''') with my proxmox ,it have next storage on the test mashine:
I see the issue for solved for ubuntu, https://github.com/canonical/packer-maas/issues/155 but dont understand how do for Centos, it dont using any scripts
Important! Read the logs, the problem was in the installation of the packages.
This issue is stale because it has been open for 30 days with no activity.
I am trying to run my “centos-9 Custom” image in “maas” using packer to build. My build works, after I try to install os in “proxmox” I get the following errors:
I am using the standard packer-maas for centos-9-stream, my “centos9-stream.ks.pkrtpl.hcl:
My image build process:
If I using Ubuntu Custom, it
s good working. I have small skills for that works, and don
t understand what is happen,P.S I tryed changed the next directives:
one step, one change, it
s don
t helped