Basic scenario files on `umount` error

[jeffmcaffer]

With a fresh download of ignite 0.10 on Ubuntu 20.04 (amd64) and run the first line of the README example. Fails on umount.

sudo ignite run weaveworks/ignite-ubuntu --cpus 2 --memory 1GB --ssh --name my-vm
INFO[0000] Starting image import...
FATA[0002] command ["umount" "/tmp/364427222"] exited with "umount: /tmp/364427222: target is busy.\n": exit status 32

I get the same thing using ignited and following the getting started example with smoke-test.yml

I tried building from source and that didn't help. Also poked around in the code to find the failing umount and comment it out. That gets me further along but then I get an error related to e2fsck.

~/git/ignite$ sudo ignite run weaveworks/ignite-ubuntu --cpus 2 --memory 1GB --ssh --name my-vm
INFO[0000] Starting image import...
INFO[0001] skipping to umount
INFO[0004] Imported OCI image "weaveworks/ignite-ubuntu:latest" (248.9 MB) to base image with UID "3f1ddf40d160cb01"
INFO[0004] containerd image "weaveworks/ignite-kernel:5.10.51" not found locally, pulling...
INFO[0007] Imported OCI image "weaveworks/ignite-kernel:5.10.51" (71.3 MB) to kernel image with UID "1ff5defb99c12f2e"
INFO[0008] Removed VM with name "my-vm" and ID "c40b1f9686ad2fe6"
FATA[0008] command ["resize2fs" "/dev/mapper/ignite-c40b1f9686ad2fe6"] exited with "resize2fs 1.45.5 (07-Jan-2020)\nPlease run 'e2fsck -f /dev/mapper/ignite-c40b1f9686ad2fe6' first.\n\n": exit status 1

Feels like somehow something fundamental in my setup is wrong but I don't see what. Pretty vanilla all around.

A few things of note (perhaps):

• In the doc output for ignite version the last line talks about "runtime". I do not have that in my output. Not sure if it matters. I did notice in some commands I'd get a "No runtime" error. I do have containerd (and Docker) installed.

  azureuser@ExtendoCompute:~/git/ignite$ ignite version
  Ignite version: version.Info{Major:"0", Minor:"10+", GitVersion:"v0.10.0-8+7017a60c3ff771-dirty", 
  GitCommit:"7017a60c3ff77191d7c14cfa4602a439171fa82e", GitTreeState:"dirty", BuildDate:"2021-10-19T22:13:36Z", 
  GoVersion:"go1.16.3", Compiler:"gc", Platform:"linux/amd64", SandboxImage:version.Image{Name:"weaveworks/ignite", 
  Tag:"dev", Delimeter:":"}, KernelImage:version.Image{Name:"weaveworks/ignite-kernel", Tag:"5.10.51", Delimeter:":"}}
  Firecracker version: v0.22.4

• many of the install/setup snippets assume you are running as root. I am not so sprinkled sudos around. Since most of those were install operations, once they work it seems they should be fine. Note that I also tried running sudo -s first and then running ignite and still get the e2fsck error.

[jeffmcaffer]

I went through the code and found everywhere that resize2fs is called and it DOES appear that `e2fsck -pf is being run. However, in all cases it appears any errors it may be giving are being skipped.

It seems that when I run e2fsck -pf from the command line I get the following error.

e2fsck -pf /dev/mapper/ignite-a76c835f22fd4f66
/dev/mapper/ignite-a76c835f22fd4f66: Resize inode not valid.

/dev/mapper/ignite-a76c835f22fd4f66: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)

So perhaps skipping the errors masking this issue and there is in turn some other more fundamental issue with the filesystem?

[jeffmcaffer]

Update. I think this is something (still not sure what) in my machine configuration. I created a new 18.04 VM and it works fine. then I created a new 20.04 VM and it worked fine. Then I installed a few things like Docker, node, acl, and go and ran my some of my code and that seems to have broken Ignite.

Summary, at this point I'm pretty sure this is a local problem and I need to work through it. I'll close this now and post if I find the conflict and there's anything to be done about it with Ignite.