console.log not working
Bug #439161 reported by
Dustin Kirkland
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Dustin Kirkland |
Bug Description
The console.log is not getting written due to a simple typo in the placement of the -L console.log option.
:-Dustin
Related branches
Changed in eucalyptus (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Dustin Kirkland (kirkland) |
status: | Triaged → In Progress |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package eucalyptus - 1.6~bzr854- 0ubuntu13
--------------- 0ubuntu13) karmic; urgency=low
eucalyptus (1.6~bzr854-
* eucalyptus- common. eucalyptus. upstart: the -L option was in the wrong cc.eucalyptus- cc-registration .upstart, cc.upstart, eucalyptus- cloud.upstart, ipaddr. conf, eucalyptus- common. install, sc.eucalyptus- sc-registration .upstart, sc.upstart, eucalyptus- walrus. upstart: using "localhost"
place, breaking the console.log logging, LP: #439161
* eucalyptus-
eucalyptus-
eucalyptus-
eucalyptus-
eucalyptus-
is breaking registration; instead, use the real, external ip
address; consolidate the (nasty) logic for determining this
into a single, sourcable, overridable location, LP: #437058, #438602
* 80-eucalyptus-url: use the new $CLOUD_IP_ADDR value and logic
-- Dustin Kirkland <email address hidden> Wed, 30 Sep 2009 01:16:12 -0500