You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to add upgrade integration tests where endpoint security is installed. We need to test both the tamper protected and unprotected cases and the .tar.gz, RPM, and DEB package types.
As part of this addition, the logging around forwarding the upgrade action to endpoint needs to be increased to the info level.
h.log.Debugf("handlerUpgrade: after action dispatched '%+v', err: %v", a, err)
iferr!=nil {
returnerr
}
} else {
// Log and continue
h.log.Debugf("No components running for %v action type", a.Type())
}
}
There have been several recent cases where tamper protected agent upgrades have failed due to invalid uninstall tokens. The root cause is currently unknown, but missing logging and inadequate automated testing are definitely contributing to these problems.
The text was updated successfully, but these errors were encountered:
It would also help if Agent logged its PID, at least at startup. We can see in the endpoint logs when Agent disconnects and reconnects, and are logging its PID each time it connects, but right now we have to search for matching Agent logs by timestamp only.
We need to add upgrade integration tests where endpoint security is installed. We need to test both the tamper protected and unprotected cases and the .tar.gz, RPM, and DEB package types.
As part of this addition, the logging around forwarding the upgrade action to endpoint needs to be increased to the info level.
elastic-agent/internal/pkg/agent/application/actions/handlers/handler_action_upgrade.go
Lines 58 to 74 in 49745a7
There have been several recent cases where tamper protected agent upgrades have failed due to invalid uninstall tokens. The root cause is currently unknown, but missing logging and inadequate automated testing are definitely contributing to these problems.
The text was updated successfully, but these errors were encountered: