Deploy failure involving curtin and a temporary directory

[Peter Matulis]

I tried to deploy Ubuntu 18.04 LTS on a bare metal machine and there was a failure at the very end of the process. I was even able to log in over SSH but got booted out shortly after.

A temporary directory appears to be busy, EFI-related packages cannot be installed, and the directory cannot be unmounted.

See attachment 'install-log.txt' for details.

[Ryan Harper (raharper)]

Hi,

Thanks for filing a bug.

"umount: /tmp/tmplaz_auvz/target/run: target is busy."

I've seen the error before and typically it happens when you ssh into the instance during the install. When the ubuntu user logs in , systemd will mount up some temp directories for the user in /run.

Can you recreate this failure without logging in to the system at all? MAAS will detect if the deployment has failed. You can fetch and collect logs after the failure if needed.

https://discourse.maas.io/t/getting-curtin-debug-logs/169

[Peter Matulis (petermatulis)]

I was not able to reproduce. What you describe is probably what happened since I did indeed SSH in quite early. I wonder if this can be prevented somehow.

[Alberto Donato (ack)]

I hit the same issue by ssh-ing in the machine during a deploy

[Jerzy Husakowski (jhusakowski)]

Waiting for curtin analysis to be completed.

[Launchpad Janitor (janitor)]

[Expired for MAAS because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for curtin because there has been no activity for 60 days.]