[enhacement] MAAS script runner should capture the environment in results.yaml

Bug #1782220 reported by Lee Trager
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Unassigned

Bug Description

The operating system, kernel version, and test tool version can all effect the results of any commissioning or testing script. For example the fio test normally gives higher numbers when run on Bionic vs Xenial. MAAS does not currently record anything about the environment so users who are trying to compare results do not have a way to check for environmental changes.

The MAAS script runner should automatically capture the operating system name, version, codename, kernel version, and any Debian/Snap package version installed by the script runner. The results should be appended to the results.yaml file to contain this information in a new object, environment.

Lee Trager (ltrager)
description: updated
Changed in maas:
milestone: none → 2.5.0alpha2
milestone: 2.5.0alpha2 → 2.5.0
status: New → Triaged
importance: Wishlist → Undecided
summary: - MAAS script runner should capture the environment in results.yaml
+ [enhacement] MAAS script runner should capture the environment in
+ results.yaml
Changed in maas:
milestone: 2.5.0 → 2.5.x
Changed in maas:
milestone: 2.5.x → next
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Changed in maas:
milestone: next → none
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.