yahoo-eng-team team mailing list archive

[Chad Smith <1770712@xxxxxxxxxxxxxxxxxx>]

won't fixed artful as it is EOL as of June 20th,

** Tags removed: verification-needed verification-needed-artful verification-needed-xenial
** Tags added: verification-done verification-done-artful verification-done-xenial

** Tags removed: verification-done-artful verification-needed-bionic
** Tags added: verification-done-bionic

** Description changed:

+ === Begin SRU Template ===
+ [Impact]
+ Cloud-init logs should now contain full packaged version of cloud-init on xenial, artful and bionic.
+ 
+ [Test Case]
+ # We should see specific version and patch information
+ for series in xenial artful bionic;
+ do
+    echo '=== BEGIN ' $series ' ==='
+    ref=$series-proposed;
+    lxc delete test-$series --force;
+    lxc-proposed-snapshot -p -P $series $ref | egrep 'Creating|cloud-init';
+    lxc init $ref test-$series;
+    lxc start test-$series;
+    packaged_version=`lxc exec test-$series -- dpkg-query --show -f '${version}' cloud-init`;
+    lxc exec test-$series -- grep $packaged_version /var/log/cloud-init.log;
+    lxc exec test-$series -- cloud-init --version;
+ done
+ 
+ # Also, cloud-init --version should show the packaged version
+ # it should contain a -0ubuntu portion.
+ 
+ $ cloud-init --version
+ /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1
+ 
+ [Regression Potential]
+ This really should be low chance of regression.  The chance would be
+ if something is running 'cloud-init --version' and parsing the output,
+ or parsing the output of /var/log/cloud-init.log (or the console log).
+ 
+ Such specific parsing of a log seems brittle anyway. Parsing output
+ of --version that expected to not have a -0ubuntuX in it would need to
+ be updated.
+ 
+ [Other Info]
+ Upstream commit at
+   https://git.launchpad.net/cloud-init/commit/?id=525a9e8f
+ 
+ === End SRU Template ===
+ 
+ 
  [Test Case]
  # We should see specific version and patch information
  $ packaged_version=$(dpkg-query --show -f '${version}' cloud-init)
  $ grep $packaged_version /var/log/cloud-init.log  # Expect to stage header logs
  ...
  2018-07-10 19:33:16,406 - util.py[DEBUG]: Cloud-init v. 18.3-9-g2e62cb8a-0ubuntu1 running 'init-local' at Tue, 10 Jul 2018 19:33:16 +0000. Up 1.00 seconds.
  
  # Also, cloud-init --version should show the packaged version
  # it should contain a -0ubuntu portion.
  
  $ cloud-init --version
  /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1
  
  [Regression Potential]
  This really should be low chance of regression.  The chance would be
  if something is running 'cloud-init --version' and parsing the output,
  or parsing the output of /var/log/cloud-init.log (or the console log).
  
  Such specific parsing of a log seems brittle anyway. Parsing output
  of --version that expected to not have a -0ubuntuX in it would need to
  be updated.
  
  [Other Info]
  Upstream commit at
-   https://git.launchpad.net/cloud-init/commit/?id=525a9e8f
+   https://git.launchpad.net/cloud-init/commit/?id=525a9e8f
  
  === End SRU Template ===
  
  
+ === Original Description ===
  Cloud-init rsyslog has the major version of cloud-init:
  
  May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2
  running 'init-local' at Fri, 11 May 2018 17:40:47 +0000. Up 15.63
  seconds.
  
  However, it would be nice if it places the whole version, so that we can
  now exactly what version of cloud-init its running, e.g:
  
  May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2
  (27-g6ef92c98-0ubuntu1~18.04.1) running 'init-local' at Fri, 11 May 2018
  17:40:47 +0000. Up 15.63 seconds.

** Changed in: cloud-init (Ubuntu Artful)
       Status: Fix Committed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1770712

Title:
  It would be nice if cloud-init provides full version in logs

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Artful:
  Won't Fix
Status in cloud-init source package in Bionic:
  Fix Committed
Status in cloud-init source package in Cosmic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Cloud-init logs should now contain full packaged version of cloud-init on xenial, artful and bionic.

  [Test Case]
  # We should see specific version and patch information
  for series in xenial artful bionic;
  do
     echo '=== BEGIN ' $series ' ==='
     ref=$series-proposed;
     lxc delete test-$series --force;
     lxc-proposed-snapshot -p -P $series $ref | egrep 'Creating|cloud-init';
     lxc init $ref test-$series;
     lxc start test-$series;
     packaged_version=`lxc exec test-$series -- dpkg-query --show -f '${version}' cloud-init`;
     lxc exec test-$series -- grep $packaged_version /var/log/cloud-init.log;
     lxc exec test-$series -- cloud-init --version;
  done

  # Also, cloud-init --version should show the packaged version
  # it should contain a -0ubuntu portion.

  $ cloud-init --version
  /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1

  [Regression Potential]
  This really should be low chance of regression.  The chance would be
  if something is running 'cloud-init --version' and parsing the output,
  or parsing the output of /var/log/cloud-init.log (or the console log).

  Such specific parsing of a log seems brittle anyway. Parsing output
  of --version that expected to not have a -0ubuntuX in it would need to
  be updated.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=525a9e8f

  === End SRU Template ===

  
  [Test Case]
  # We should see specific version and patch information
  $ packaged_version=$(dpkg-query --show -f '${version}' cloud-init)
  $ grep $packaged_version /var/log/cloud-init.log  # Expect to stage header logs
  ...
  2018-07-10 19:33:16,406 - util.py[DEBUG]: Cloud-init v. 18.3-9-g2e62cb8a-0ubuntu1 running 'init-local' at Tue, 10 Jul 2018 19:33:16 +0000. Up 1.00 seconds.

  # Also, cloud-init --version should show the packaged version
  # it should contain a -0ubuntu portion.

  $ cloud-init --version
  /usr/bin/cloud-init 18.3-9-g2e62cb8a-0ubuntu1

  [Regression Potential]
  This really should be low chance of regression.  The chance would be
  if something is running 'cloud-init --version' and parsing the output,
  or parsing the output of /var/log/cloud-init.log (or the console log).

  Such specific parsing of a log seems brittle anyway. Parsing output
  of --version that expected to not have a -0ubuntuX in it would need to
  be updated.

  [Other Info]
  Upstream commit at
    https://git.launchpad.net/cloud-init/commit/?id=525a9e8f

  === End SRU Template ===

  
  === Original Description ===
  Cloud-init rsyslog has the major version of cloud-init:

  May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v.
  18.2 running 'init-local' at Fri, 11 May 2018 17:40:47 +0000. Up 15.63
  seconds.

  However, it would be nice if it places the whole version, so that we
  can now exactly what version of cloud-init its running, e.g:

  May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v.
  18.2 (27-g6ef92c98-0ubuntu1~18.04.1) running 'init-local' at Fri, 11
  May 2018 17:40:47 +0000. Up 15.63 seconds.

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