Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Restarting an atomic testing keeps the same Inject UUID #1847

Closed
RomuDeuxfois opened this issue Nov 12, 2024 · 0 comments · Fixed by #1901
Closed

Restarting an atomic testing keeps the same Inject UUID #1847

RomuDeuxfois opened this issue Nov 12, 2024 · 0 comments · Fixed by #1901
Assignees
@isselparra
Labels
bug use for describing something not working as expected solved The issue has been solved technical improvement Technical refactor or improvement is needed
Milestone
Release 1.10.0

Comments

@RomuDeuxfois
Copy link
Member

Description

When we restart an atomic testing, we keep the initial object and therefore its UUID.
This prevents us from looking for a single execution in the defender and sentinel logs based on the UUID of the inject (openbas-implant-UUID.exe).

By deleting and creating a new inject when we restart an atomic testing, this allows us to have a single execution.
@RomuDeuxfois RomuDeuxfois added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Nov 12, 2024
@EllynBsc EllynBsc removed the needs triage use to identify issue needing triage from Filigran Product team label Nov 12, 2024
@EllynBsc EllynBsc added this to the Release 1.9.0 milestone Nov 12, 2024
@isselparra isselparra self-assigned this Nov 20, 2024
@isselparra isselparra mentioned this issue Nov 21, 2024
Merged
5 tasks
@EllynBsc EllynBsc added the technical improvement Technical refactor or improvement is needed label Nov 21, 2024
isselparra added a commit that referenced this issue Nov 29, 2024
@isselparra
[backend/frontend] Restarting an atomic testing keeps the same Inject…
4273a9d 
… UUID (#1847)
@isselparra isselparra added the solved The issue has been solved label Nov 29, 2024
Dimfacion pushed a commit that referenced this issue Dec 2, 2024
@isselparra @Dimfacion
[backend/frontend] Restarting an atomic testing keeps the same Inject…
252b5c0 
… UUID (#1847)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@isselparra isselparra

Labels
bug use for describing something not working as expected solved The issue has been solved technical improvement Technical refactor or improvement is needed
Projects
None yet
Milestone
Release 1.10.0
Development

Successfully merging a pull request may close this issue.

[backend/frontend] Restarting an atomic testing keeps the same Inject UUID OpenBAS-Platform/openbas
3 participants
@isselparra @EllynBsc @RomuDeuxfois