This should always guarantee that openjdk-7-jre-headless is configured before zookeeperd. Instead it is somehow being configured *after* default-jre-headless and thus, the alternatives are not set up.
There is a workaround.. if you install with --no-install-recommends
The order is correct.
This also exposes two other bugs to me:
1) /var/lib/zookeeper should belong to zookeeper
2) the upstart job should be reporting the failure, not 'start/running'
Scott, good call. That was definitely a red herring.
So this appears to be a circular dependency problem with dpkg... because
zookeeperd -> zookeeper -> default- jre-headless -> openjdk- 7-jre-headless
This should always guarantee that openjdk- 7-jre-headless is configured before zookeeperd. Instead it is somehow being configured *after* default- jre-headless and thus, the alternatives are not set up.
There is a workaround.. if you install with --no-install- recommends
The order is correct.
This also exposes two other bugs to me:
1) /var/lib/zookeeper should belong to zookeeper
2) the upstart job should be reporting the failure, not 'start/running'