@Scott: I am sorry, I do not know, not yet. We only know of these issues because the test script will grab the console output for *failed* SSH sessions to the instance. I intend to try and -- instead of terminating the instance -- leave it running, so I can get to the specific node that is running it and try to access it locally. But, if the root is really read-only, I very much doubt I will be able to log in to the instance :-(
Running the instance in debug mode for either plymouth or mountall is probably not going to help, since we cannot get the *current* console output: we can get it just after boot, at shutdown, or on "significat events" (whatever that means), and only 64K-worth of output. I understand this is a tough nail to gnaw (and I know personally, my teeth hurt). Please rest assured that we do intend to get to the bottom of it. -- rm: cannot remove `/var/lib/urandom/random-seed': Read-only file system https://bugs.launchpad.net/bugs/567592 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
