Skip to content

Release QA: fleetd-1.49.1 #34772

@lukeheath

Description

@lukeheath

fleetd agent

Includes updates to:

  • Orbit/Desktop: True
  • Chrome extension: False

List versions changes for any component updates below:

  • Orbit/Desktop v1.48.0 > v1.49.0

Testing gates for new fleetd release

Goal: Ensure new fleetd is tested and promoted from local > edge > stable channels

  1. Build a new fleetd from the release candidate branch as needed for Orbit, Desktop, and Chrome Extension.
Test nameStep instructionsExpected resultpass/fail
$Name{what a tester should do}{what a tester should see when they do that}pass/fail
`fleetd` local testing 1. Following [Testing TUF]([url](https://github.com/fleetdm/fleet/blob/main/tools/tuf/test/README.md)) instructions create binaries for Mac, Windows, and Ubuntu using your local TUF repository and install on macOS, Linux, and Windows hosts.
1. Confirm the hosts install with the updated version and are working correctly.
2. Confirm any new features and/or bug fixes associated with this release are working as intended.
pass/fail
`fleetd` auto-update tests 1. Conduct the [`fleetd` auto-update n+1 test]([url](https://github.com/fleetdm/fleet/blob/main/tools/tuf/test/Fleetd-auto-update-test-guide.md))
2. QA certifies new release by commenting in issue.
1. Agent successfully auto-updates.
2. Issue is certified by QA.
pass/fail
`fleetd` tests 1. Set up a host in your instance to receive updates from the `edge` channels.
2. Work with engineer leading the release to push changes to the `edge` channel.
1. Confirm the hosts running on the edge channel receive the update and are working correctly.
2. Confirm any new features and/or bug fixes associated with this release are working as intended.
pass/fail

New fleetd pushed to edge

Goal: Ensure fleetd version pushed to edge is working with the current released version of fleet.

  1. Fleet server is running the latest released version available on Fleet Releases page.
  2. Set Agent options to use edge in the Fleet server configuration. For example:

    update_channels:

    osqueryd: edge

    orbit: edge

    desktop: edge
Test nameStep instructionsExpected resultpass/fail
$Name{what a tester should do}{what a tester should see when they do that}pass/fail
Query flowRun queries. 1. Queries can be run manually 4.75.0: pass
4.76.0: pass
Host FlowVerify a new host can be added using your own device. 1. Hosts can enroll and report correct version of `fleetd` (orbit, osquery, desktop).
2. Refetching host vitals completes and returns updated information.
4.75.0: pass
4.76.0: pass
My device pageVerify the end user's my device page loads successfully. 1. Clicking the Fleet desktop item, then "My device" successfully loads the my device page.
2. The "My device" page is populated correctly and as expected.
3. Styling and padding appears correct.
4.75.0: pass
4.76.0: pass
ScriptsVerify script execution 1. Verify able to run a script on all host types from CLI.
2. From Host details (macOS, Windows, & Linux) run a script that should PASS, verify.
3. From Host details (macOS, Windows, & Linux) run a script that should FAIL, verify.
4. Verify script results display correctly in Activity feed.
4.75.0: pass
4.76.0: pass
SoftwareVerify software install / download 1. From Host details (macOS, Windows, & Linux) run an install that should PASS, verify.
2. From My Device (macOS, Windows, & Linux) software tab should have self-service items available, verify.
3. Verify software installs display correctly in Activity feed.
4.75.0: pass
4.76.0: pass
OS settingsVerify OS settings functionality 1. Verify able to configure Disk encryption (macOS, Windows, & Linux).
2. Verify host enrolled with Disk encryption enforced successfully encrypts.
4.75.0: pass
4.76.0: pass
Packs flowVerify management, operation, and logging of ["2017 packs"](https://fleetdm.com/handbook/company/why-this-way#why-does-fleet-support-query-packs). 1. Packs successfully run on host machines after migrations
2. New Packs can be created.
3. Packs can be edited and deleted
4. Packs results information is logged
4.75.0: pass
4.76.0: pass
Fleet FreeVerify that Fleet Desktop works on Fleet Free. After repointing a Fleet Desktop install at a server running Fleet Free:
  1. Clicking the Fleet desktop item, then "My device" successfully loads the my device page.
  2. The "My device" page is populated correctly and as expected.
  3. Styling and padding appears correct.
4.75.0: pass
4.76.0: pass

Notes

Issues found new to this version:

Issues found that reproduce in last stable version:

What has not been tested:

Include any notes on whether issues should block release or not as needed:

Metadata

Metadata

Labels

#g-mdmMDM product group#g-orchestrationOrchestration product group#g-security-complianceSecurity & Compliance product group#g-softwareSoftware product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.

Type

No type

Projects

Status

Done

Status

Done

Status

Done

Status

Done

Relationships

None yet

Development

No branches or pull requests

Issue actions