syslog logging is broken in natty

Bug #704509 reported by Scott Moser
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released

Bug Description

Binary package hint: cloud-init

syslog logging is broken in natty, while it works fine in maverick. on a maverick instance, /var/log/cloud-init.log will have lines like"

[CLOUDINIT] 2011-01-18 16:44:19,830 - cloud-init[INFO]: cloud-init start-local running: Tue, 18 Jan 2011 16:44:19 +0000. up 11.47 seconds
Jan 18 16:44:26 ip-10-244-17-175 [CLOUDINIT] 2011-01-18 16:44:26,183 - cloud-init-cfg[INFO]: cloud-init-cfg ['all']

the shift in format is due to the change in the logging config that is used.
The first format is cloud-init writing directly to the file. The second is cloud-config when the syslog is availalbe, writing through syslog. Something is busted with that in natty.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: cloud-init 0.5.15-0ubuntu4
ProcVersionSignature: User Name 2.6.37-12.26-virtual 2.6.37
Uname: Linux 2.6.37-12-virtual x86_64
Architecture: amd64
Date: Tue Jan 18 16:45:23 2011
Ec2AMI: ami-78b54511
Ec2AMIManifest: ubuntu-images-testing-us/ubuntu-natty-daily-amd64-server-20110118.manifest.xml
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: m1.large
Ec2Kernel: aki-427d952b
Ec2Ramdisk: unavailable
PackageArchitecture: all
 PATH=(custom, user)
SourcePackage: cloud-init

Revision history for this message
Scott Moser (smoser) wrote :
Revision history for this message
Scott Moser (smoser) wrote :

In my natty instance, /var/log/cloud-init.log was owned by root:root.
In the maverick instance, it is owned by syslog:adm.

I'm not sure what would have changed this. It seems I may need to create the file with proper permissions on package install.

Changed in cloud-init (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Scott Moser (smoser) wrote :

fix-released with 0.6.0 and 0.6.0-0ubuntu1

Changed in cloud-init (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.