landscape-client init script does not wait for the network to be available before checking for EC2 user data

By the way, this is similar to bug #308530 in ubuntu-on-ec2, which they're fixing by putting the following snippet into their startup scripts (or at least, this is the currently-proposed solution):

+def checkServer():
+ for x in range(30*60):
+ s = socket.socket()
+ try:
+ address = '169.254.169.254'
+ port = 80
+ s.connect((address,port))
+ s.close()
+ return
+ except socket.error, e:
+ time.sleep(1)
+
+checkServer()

Hey Chris, thanks for cooking up this branch despite illness! Nice
job, +1

[1]

+ if time.time() - start > timeout:
+ break

This change doesn't seem to have a test.

Nice simple fix!

thanks

+1

Thanks guys. I've added a test for the timeout and merged it to trunk.

When the server guys make a test build of their new Ubuntu-on-EC2 AMIs, we'll test it then.

actually, apparently you can reboot a machine in EC2 and it keeps the same filesystem, so we *can* test this. I'll do that soon.

I see the boot order change in the debian/rules file, but what about a package upgrade from a previous version which still starts at level 25 instead of 45 (which is what it was changed to)?

I guess I'll see that once I start the ugprade tests with the final-final-final client.