[Bug 1018554] Re: write timestamp to console on halt/reboot/shutdown

[Scott Moser]

** Description changed:

  === Begin SRU Information ===
  [Impact]
-  * When launching a cloud instance, the console log is extremely valuable
-    in debugging issues, and is often times all the data you have.
-    In Ubuntu automated tests [1], having timestamps on the console for
-    'reboot' or 'halt' allows us to correlate logs from the instance
-    console and test harness.
+  * When launching a cloud instance, the console log is extremely valuable
+    in debugging issues, and is often times all the data you have.
+    In Ubuntu automated tests [1], having timestamps on the console for
+    'reboot' or 'halt' allows us to correlate logs from the instance
+    console and test harness.
  
-    This change simply writes a message to /dev/console when a reboot or
-    shutdown occurs.
+    This change simply writes a message to /dev/console when a reboot or
+    shutdown occurs.
  
-    [1] https://jenkins.qa.ubuntu.com/view/Quantal/view/All%20Quantal/job
+    [1] https://jenkins.qa.ubuntu.com/view/Quantal/view/All%20Quantal/job
  /quantal-server-ec2/
  
  [Test Case]
-  * To demonstrate the usefulness, launch an instance, and then power it
-    off.  After that, get the console log.  You'll notice no timestamp
-    other than the kernel uptime timestamps that could help you to
-    determine when the instance was terminated.
+  * To demonstrate the usefulness, launch an instance, and then power it
+    off.  After that, get the console log.  You'll notice no timestamp
+    other than the kernel uptime timestamps that could help you to
+    determine when the instance was terminated.
  
  [Regression Potential]
-  * There is very little regression potential here.  If this upstart job was
-    somehow buggy, it would just result in failure to write the message.
- 
- [Other Info]
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
-  * and address these questions in advance
+  * There is very little regression potential here.  If this upstart job was
+    somehow buggy, it would just result in failure to write the message.
  
  === End SRU Information ===
  
- 
- In EC2 and other cloud platforms, the console data is programmatically available.
+ In EC2 and other cloud platforms, the console data is programmatically
+ available.
  
  Our tests in EC2 collect this console output on shutdown / reboot
  /terminate.  The data is very useful.
  
  in cloud-init i've added timestamps to output so that information is available in the console log.
  One thing missing (which cloud-init has no hooks for) is 'shutdown' or 'reboot'.
  
  I'd like for upstart to write a message to /dev/console saying:
   rebooting Wed, 27 Jun 2012 15:52:45 -0400
  
  or something like that.
  I'd be happy if the 'nih_info' messages in util/reboot.c
  had at timestamp on them, and got written to /dev/console by default (they do not seem to).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: upstart 1.5-0ubuntu7
  ProcVersionSignature: User Name 3.5.0-2.2-generic 3.5.0-rc4
  Uname: Linux 3.5.0-2-generic x86_64
  ApportVersion: 2.2.5-0ubuntu1
  Architecture: amd64
  Date: Wed Jun 27 19:45:52 2012
  ProcEnviron:
   TERM=screen
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1018554

Title:
  write timestamp to console on halt/reboot/shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1018554/+subscriptions