group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1590846@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package curtin - 0.1.0~bzr399-0ubuntu1~16.04.1

---------------
curtin (0.1.0~bzr399-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/new-upstream-snapshot: fix for specifying revision.
  * SRU current curtin
    - curtin/net: fix inet value for subnets, don't add interface attributes
      to alias (LP: #1588547)
    - improve net-meta network configuration (LP: #1592149)
    - reporting: set webhook handler level to DEBUG, no filtering
      (LP: #1590846)
    - tests/vmtests: add yakkety, remove vivid
    - curtin/net: use post-up for interface alias, resolve 120 second time out
      on Trusty when using interface aliases
    - vmtest: provide info on images used
    - fix multipath configuration and add multipath tests (LP: #1551937)
    - tools/launch and tools/xkvm: whitespace cleanup and bash -x
    - tools/launch: boot by root=LABEL=cloudimg-rootfs
    - Initial vmtest power8 support and TestSimple test.

 -- Ryan Harper <ryan.harper@xxxxxxxxxxxxx>  Tue, 12 Jul 2016 11:29:30
-0500

** Changed in: curtin (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1590846

Title:
  [2.0b6] Installation log is not sent back to MAAS

Status in curtin:
  Fix Committed
Status in MAAS:
  Invalid
Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Trusty:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * MaaS deployments using curtin revno newer than 365 find that curtin
     no longer sends the installation log file back to maas due to a
     change in how the curtin reporter is configured.

     This affects MaaS users looking to examine the install process of a
     node.
     
   * This SRU resolves the bug by changing the reporter configuration to
     always send the install log independent of the log level
     configured.

  [Test Case]

   * On a Xenial 16.04 system
      - % apt-get install curtin
      - In one shell download and run the report-webhook-logger (attached
        to this bug)
        % python3 ./report-webhook-logger 8000
      - In second shell: run
        % sudo curtin -vvv install \
            --set install/logfile=/tmp/foo \
            --set reporting/mypost/type=webhook \
            --set reporting/mypost/endpoint=http://localhost:8000/ \
            file://tmp/non-existing.tar.gz

    PASS: In the reporting shell, the reporter will recieve an event
          like this with base64 encoded content.

      {
          "event_type": "finish",
          "level": "ERROR",
          "description": "failed: curtin command install",
          "files": [
              {
                  "content": <base64 content redacted for brevity>
                  "encoding": "base64",
                  "path": "/var/log/curtin/install.log"
              }
          ],
          "result": "FAIL",
          "name": "cmd-install",
          "origin": "curtin",
          "timestamp": 1468357973.042974
      }

  
    FAIL: Reporter does not post an event with install log file.

  [Regression Potential]


  [Original Description]

  Installation log is not sent back to back regardless of whether it
  being a successful or failed install.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1590846/+subscriptions