bug(sync): armis updater incorrectly updating compliance status #396

Closed
opened 2026-03-28 04:24:10 +00:00 by mfreeman451 · 1 comment
Owner

Imported from GitHub.

Original GitHub issue: #1203
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1203
Original created: 2025-07-07T21:48:07Z


We have two devices in our ASQ query being returned, one is reachable via serviceradar the other is not, we mark the one that we cannot reach as not being in compliant, and the one we can reach as being compliant, even though we have implemented a specific fix for this.

Imported from GitHub. Original GitHub issue: #1203 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1203 Original created: 2025-07-07T21:48:07Z --- We have two devices in our ASQ query being returned, one is reachable via serviceradar the other is not, we mark the one that we cannot reach as not being in compliant, and the one we can reach as being compliant, even though we have implemented a specific fix for this.
Author
Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1203#issuecomment-3050058431
Original created: 2025-07-08T19:22:07Z


closing as completed

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1203#issuecomment-3050058431 Original created: 2025-07-08T19:22:07Z --- closing as completed
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar#396
No description provided.