Current status here:
I have successfully booted uec image 20100310 6 times on one UEC that I have access to, and booted the 20100305 successfully as well. That is good news. Unfortunately, this is not on the UEC set up that I had originally seen the issue with 20100303 in. I will try on that later today.
In the meantime, I looked at what else changed between 20100303 and 20100305. The big change was
-linux-image-2.6.32-14-virtual 2.6.32-14.20
+linux-image-2.6.32-15-virtual 2.6.32-15.22
To see if that fixed this issue, I got the older kernel, and booted 20100310 with it. It failed to run cloud-init.
So, in short conclusion, it *seems* like this was fix-released with linux-image-2.6.32-15-virtual . However, there is still the possibility of race condition. I'll test with the original UEC system to verify problem is solved with 20100310 there.
Current status here:
I have successfully booted uec image 20100310 6 times on one UEC that I have access to, and booted the 20100305 successfully as well. That is good news. Unfortunately, this is not on the UEC set up that I had originally seen the issue with 20100303 in. I will try on that later today.
In the meantime, I looked at what else changed between 20100303 and 20100305. The big change was image-2. 6.32-14- virtual 2.6.32-14.20 image-2. 6.32-15- virtual 2.6.32-15.22
-linux-
+linux-
To see if that fixed this issue, I got the older kernel, and booted 20100310 with it. It failed to run cloud-init.
So, in short conclusion, it *seems* like this was fix-released with linux-image- 2.6.32- 15-virtual . However, there is still the possibility of race condition. I'll test with the original UEC system to verify problem is solved with 20100310 there.