[Bug 338344] Re: Node controller doesn't report invalid image downloads

[Dmitrii Zagorodnov]

*** This bug is a duplicate of bug 341714 ***
    https://bugs.launchpad.net/bugs/341714

The reason there is no error message about the failed transfer is
because the NC crashed in the middle of the transfer according to both
log excerpts above. (The line that starts with `NC is looking for
configuration...` is the first one that NC prints when it starts.)
Since any incoming request from the CC causes NC to restart, the crashes
are easy to miss.

So, this bug is not really about the lack of error messages (we do try
to log everything that goes wrong) but about a crash. If this crash
still happens with the recent version of the code, I would like to know
more about the circumstances so that I can recreate it. I tried a few
runs with NC running out of disk space during different stages of
instance initialization, with both compressed and non-compressed Walrus
downloads, but in all cases the failure to write was handled properly.

-- 
Node controller doesn't report invalid image downloads
https://bugs.launchpad.net/bugs/338344
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs