| 2009-10-22 08:46:50 |
Thierry Carrez |
bug |
|
|
added bug |
| 2009-10-26 10:24:59 |
Thierry Carrez |
eucalyptus (Ubuntu): importance |
Undecided |
Low |
|
| 2009-10-26 10:24:59 |
Thierry Carrez |
eucalyptus (Ubuntu): status |
New |
Confirmed |
|
| 2009-10-26 10:56:11 |
Thierry Carrez |
summary |
Changing LOGLEVEL in eucalyptus.conf doesn't affect log verbosity |
LOGLEVEL in eucalyptus.conf doesn't affect cloud-*.log verbosity |
|
| 2009-10-26 10:56:17 |
Thierry Carrez |
eucalyptus (Ubuntu): status |
Confirmed |
Triaged |
|
| 2009-10-29 16:28:16 |
Thierry Carrez |
summary |
LOGLEVEL in eucalyptus.conf doesn't affect cloud-*.log verbosity |
LOGLEVEL in eucalyptus.conf doesn't affect cloud-output.log verbosity |
|
| 2009-10-29 16:32:04 |
Thierry Carrez |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-10-29 16:32:04 |
Thierry Carrez |
bug task added |
|
eucalyptus (Ubuntu Karmic) |
|
| 2009-10-29 16:32:20 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): milestone |
|
karmic-updates |
|
| 2009-10-29 16:35:26 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): assignee |
|
Thierry Carrez (ttx) |
|
| 2009-10-30 14:54:33 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/eucalyptus/ubuntu |
|
| 2009-10-30 14:56:33 |
Thierry Carrez |
eucalyptus (Ubuntu Karmic): status |
Triaged |
Fix Committed |
|
| 2009-11-03 22:49:08 |
Mathias Gug |
description |
eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log. |
eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log.
==================
SRU Verification
Impact:
The logging level of most components are set to debug which is too verbose for a production setup in a release.
How the bug has been addressed:
The init script has been modified to use the LOGLEVEL option from the configuration file when starting the daemons.
To reproduce the bug:
1. Install a CC.
2. Check the verbosity level in /var/log/eucalyptus/cloud-*.log. There should be message of INFO and DEBUG level.
3. After the upgrade, edit /etc/eucalyptus/eucalyptus.conf to set LOGLEVEL to ERROR and restart the CC. There shouldn't be any messages of INFO or DEBUG level in /var/log/eucalyptus/cloud-*.log anymore.
Regression potential:
The actual log levels are not changed by the update. Only local modifications of the LOG level will be taken into account. The default level are still set to DEBUG.
================== |
|
| 2009-11-04 00:12:50 |
Dustin Kirkland |
description |
eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log.
==================
SRU Verification
Impact:
The logging level of most components are set to debug which is too verbose for a production setup in a release.
How the bug has been addressed:
The init script has been modified to use the LOGLEVEL option from the configuration file when starting the daemons.
To reproduce the bug:
1. Install a CC.
2. Check the verbosity level in /var/log/eucalyptus/cloud-*.log. There should be message of INFO and DEBUG level.
3. After the upgrade, edit /etc/eucalyptus/eucalyptus.conf to set LOGLEVEL to ERROR and restart the CC. There shouldn't be any messages of INFO or DEBUG level in /var/log/eucalyptus/cloud-*.log anymore.
Regression potential:
The actual log levels are not changed by the update. Only local modifications of the LOG level will be taken into account. The default level are still set to DEBUG.
================== |
eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log.
===========
SRU Verification
1) Watch log file
* tail -f /var/log/eucalyptus/cloud-output.log
2) Modify the log level configuration
* sudo -i "s/^LOGLEVEL=.*/LOGLEVEL=ERROR/" /etc/eucalyptus/eucalyptus.conf
3) Restart Eucalyptus
* sudo restart eucalyptus
4) Check the log, making sure that new INFO messages are not appended.
Regression Potential
This will need to be tested thoroughly to ensure that we do not discard wanted log messages.
=========== |
|
| 2009-11-05 17:52:29 |
Mathias Gug |
tags |
|
uec |
|
| 2009-11-06 10:06:36 |
Martin Pitt |
tags |
uec |
uec verification-needed |
|
| 2009-11-06 11:00:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/eucalyptus |
|
| 2009-11-06 13:22:10 |
Thierry Carrez |
description |
eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log.
===========
SRU Verification
1) Watch log file
* tail -f /var/log/eucalyptus/cloud-output.log
2) Modify the log level configuration
* sudo -i "s/^LOGLEVEL=.*/LOGLEVEL=ERROR/" /etc/eucalyptus/eucalyptus.conf
3) Restart Eucalyptus
* sudo restart eucalyptus
4) Check the log, making sure that new INFO messages are not appended.
Regression Potential
This will need to be tested thoroughly to ensure that we do not discard wanted log messages.
=========== |
eucalyptus 1.6~bzr931-0ubuntu7, UEC Cluster install from 20091020.3
In an effort to set saner production-oriented default log levels, I tried to change LOGLEVEL from DEBUG et ERROR in /etc/eucalyptus/eucalyptus.conf.
I still get INFO and DEBUG type messages in /var/log/eucalyptus/cloud-*.log.
===========
SRU Verification
1) Watch log file
* tail -f /var/log/eucalyptus/cloud-output.log
2) Modify the log level configuration
* sudo -i "s/^LOGLEVEL=.*/LOGLEVEL=WARN/" /etc/eucalyptus/eucalyptus.conf
3) Restart Eucalyptus
* sudo restart eucalyptus
4) Check the log, making sure that new INFO messages are not appended.
Regression Potential
This will need to be tested thoroughly to ensure that we do not discard wanted log messages.
===========
|
|
| 2009-11-06 13:23:13 |
Thierry Carrez |
tags |
uec verification-needed |
uec verification-done |
|
| 2009-11-23 09:46:08 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-11-23 09:48:14 |
Martin Pitt |
eucalyptus (Ubuntu): status |
Triaged |
Fix Released |
|
| 2009-11-23 09:51:25 |
Martin Pitt |
eucalyptus (Ubuntu Karmic): status |
Fix Released |
Fix Committed |
|
| 2009-11-30 20:16:09 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
