group.of.nepali.translators team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Hello Andres, or anyone else affected,

Accepted curtin into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/curtin/0.1.0~bzr399-0ubuntu1~16.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Also affects: curtin (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: curtin (Ubuntu Xenial)
   Importance: Undecided
       Status: New

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

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

** Tags added: verification-needed

-- 
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 Xenial:
  Fix Committed

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