This is on Ubuntu 12.04.1 LTS with upstart versions 1.5-0ubuntu7.1 and 1.5-0ubuntu7.2.
These updates were pushed back mid release and break every machine from the company I host with.
I am not sure if it qualifies for a bug report as they use a customized kernel config, however the behavior seems like a bug.
Tested four machines with three different hardware setups, all non-RAID, non-LVM, three fresh primary partition installs.
The unexpected behavior is that once 7.1 or 7.2 is installed /dev/sda ceases to be accessible as evidenced by
apt-get install upstart
reboot
fdisk /dev/sda
fdisk: unable to open /dev/sda: No such file or directory
The partitions are mounted, accessible, and running fine. To me this screams regression bug, but as the above says not sure if it qualifies.
So the question, should I submit this as an upstart bug, or just continue to yell at my hosting company for the kernel config I told them would cause problems six months ago?
