fleet/orbit/changes/19218-exit-status-78 at bdfcf646b75dffb72ccc985231adfe5e4e837598 - Elgato_dark/fleet - Forgejo: Beyond coding. We Forge.

Elgato_dark/fleet

mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00

Victor Lyuboslavsky 5eb48b4f88

ignore osquery error when valid host info data is returned (#19233 )

#19218
This fixes the "exit status 78" error seen at orbit startup.

Manually tested by forcing orbit to take the "error" path.

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Added/updated tests
- [x] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

2024-05-23 12:31:39 -05:00

1 line

109 B

Text

Raw Blame History

When orbit gets host info from osquery at startup, ignore and log osquery error when valid data is returned.