Okay, I talked to Scott about similar upstart situations last week, and I think I have his blessing on what I thought would be hacky.
Basically, we need to create an additional, upstart (psuedo) job, that would start on started networking, and basically loop until some conditional is settled (in this case, ip_address_obtained), at which point this psuedo job would emit a signal. The Eucalyptus upstart jobs would simply wait on this signal. I'll implement this at the distro sprint. ** Summary changed: - eucalyptus-cloud doesn't reply to requests + eucalyptus-cloud doesn't reply to requests (due to upstart networking issue) -- eucalyptus-cloud doesn't reply to requests (due to upstart networking issue) https://bugs.launchpad.net/bugs/503180 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
