New Question
0

Prepare image for MAAS - VMware/bare metal deployment

asked 2018-03-06 15:13:23 +0300

rxwrxrx gravatar image

Hi,

Thanks for windows-openstack-imaging-tools -- very useful scripts & good documentation. I'm trying to prepare image for testing on the VMware & bare metal.

Successfully prepared Windows 7 SP1, including all needed drivers, converted it to ddtgz format, attached to MAAS region controller. But after the installations process reboots once, windows start continuously rebooting.

On the MAAS logs I have:

Mar 2 03:09:15 MAAS1 kernel: [ 249.143122] sda: sda1
Mar 2 03:09:15 MAAS1 systemd-udevd[2324]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2.
Mar 2 03:09:16 MAAS1 kernel: [ 249.734205] sda: sda1
Mar 2 03:09:16 MAAS1 systemd-udevd[2339]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2.
Mar 2 03:09:16 MAAS1 ntfs-3g[2352]: Version 2015.3.14AR.1 integrated FUSE 28
Mar 2 03:09:16 MAAS1 ntfs-3g[2352]: Mounted /dev/sda1 (Read-Write, label "OS", NTFS 3.1)
Mar 2 03:09:16 MAAS1 ntfs-3g[2352]: Cmdline options: rw
Mar 2 03:09:16 MAAS1 ntfs-3g[2352]: Mount options: rw,allowother,nonempty,relatime,fsname=/dev /sda1,blkdev,blksize=4096
Mar 2 03:09:16 MAAS1 ntfs-3g[2352]: Ownership and permissions disabled, configuration type 7
Mar 2 03:09:16 MAAS1 ntfs-3g[2352]: Unmounting /dev/sda1 (OS)
Mar 2 03:09:16 MAAS1 systemd-udevd[2354]: Process '/bin/sh -c 'echo 180 >/sys$DEVPATH/device/timeout'' failed with exit code 2.
Mar 2 03:09:16 MAAS1 ntfs-3g[2360]: Version 2015.3.14AR.1 integrated FUSE 28
Mar 2 03:09:16 MAAS1 ntfs-3g[2360]: Mounted /dev/sda1 (Read-Write, label "OS", NTFS 3.1)
Mar 2 03:09:16 MAAS1 ntfs-3g[2360]: Cmdline options: rw
Mar 2 03:09:16 MAAS1 ntfs-3g[2360]: Mount options: rw,allow
other,nonempty,relatime,fsname=/dev /sda1,blkdev,blksize=4096
Mar 2 03:09:16 MAAS1 ntfs-3g[2360]: Ownership and permissions disabled, configuration type 7
Mar 2 03:09:18 MAAS1 cloud-init[2273]: Traceback (most recent call last):
Mar 2 03:09:18 MAAS1 cloud-init[2273]: File "/tmp/tmpemf69ztr/target/curtin/finalize.py", line 141, in <module>
Mar 2 03:09:18 MAAS1 cloud-init[2273]: curthooks()
Mar 2 03:09:18 MAAS1 cloud-init[2273]: File "/tmp/tmpemf69ztr/target/curtin/finalize.py", line 88, in curthooks
Mar 2 03:09:18 MAAS1 cloud-init[2273]: cloudbaseinit = getcloudbaseinitdir(target)
Mar 2 03:09:18 MAAS1 cloud-init[2273]: File "/tmp/tmpemf69ztr/target/curtin/finalize.py", line 82, in getcloudbaseinitdir
Mar 2 03:09:18 MAAS1 cloud-init[2273]: raise ValueError("Failed to find cloudbase-init install destination")
Mar 2 03:09:18 MAAS1 cloud-init[2273]: ValueError: Failed to find cloudbase-init install destination
Mar 2 03:09:19 MAAS1 cloud-init[2273]: Unexpected error while running command.
Mar 2 03:09:19 MAAS1 cloud-init[2273]: Command: ['/tmp/tmpemf69ztr/target/curtin/finalize']
Mar 2 03:09:19 MAAS1 cloud-init[2273]: Exit code: 1
Mar 2 03:09:19 MAAS1 cloud-init[2273]: Reason: -
Mar 2 ... (more)

edit retag flag offensive close merge delete

2 answers

Sort by » oldest newest most voted
0

answered 2018-03-14 12:08:40 +0300

avladu gravatar image

Hello,

The looks like a problem with Cloudbase-Init installation folder, which is required to be on the root partition, at one of these 3 known paths: https://github.com/cloudbase/windows-...

Can you make sure this is the case in your environment?

Thank you,
Adrian Vladu

edit flag offensive delete link more
1

answered 2018-04-19 20:32:25 +0300

rxwrxrx gravatar image

updated 2018-04-19 20:34:59 +0300

Hello Adrian,

Thanks for the tips, you are right!
I had missed cloudbase-init in my hyper-v instance, somehow.

Thank you for this great job!

Best regards,
Dmitriy

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2018-03-06 15:13:23 +0300

Seen: 64 times

Last updated: Apr 19