Cluster controller initscripts do not output messages at boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Low
|
Thierry Carrez |
Bug Description
Testing Alpha6 candidate, UEC install / Cluster mode.
eucalyptus 1.6~bzr746-0ubuntu3
Symptom:
The initscripts for eucalyptus-* (while successful) do not output any boot message:
-----------------
* Starting web server apache2
apache2: Could not reliably determine the server's fully qualified domain name,
using 127.0.1.1 for ServerName
* Restarting OpenBSD Secure Shell server sshd
Enabling IP forwarding
Ubuntu karmic (development branch) ubuntu tty1
ubuntu login:
-----------------
Expected result:
-----------------
* Starting web server apache2 [ OK ]
* Starting Eucalyptus Cluster Controller eucalyptus-cc [ OK ]
* Starting Eucalyptus Cloud Controller eucalyptus-cloud [ OK ]
* Starting Eucalyptus Storage Controller eucalyptus-sc [ OK ]
* Starting Eucalyptus Walrus eucalyptus-walrus [ OK ]
Ubuntu karmic (development branch) ubuntu tty1
ubuntu login:
-----------------
Adding VERBOSE=yes at the top of the /etc/init.
Changed in eucalyptus (Ubuntu): | |
assignee: | nobody → Thierry Carrez (ttx) |
status: | Triaged → In Progress |
The issue is that even the very basic messages are guarded by if [ "$VERBOSE" != no ]...