Skip to content

Investigate issues with android images generated on July 15th #3594

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.

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

Open
3 tasks
riarenas opened this issue Jul 24, 2024 · 1 comment
Open
3 tasks

Investigate issues with android images generated on July 15th #3594

riarenas opened this issue Jul 24, 2024 · 1 comment
Assignees
Labels
Ops - Service Maintenance Used to track issues related to maintaining the services .NET Eng Supports

Comments

@riarenas
Copy link
Member

Currently, all the android queues are unmonitored due to the latest images generated for the android queues failing to produce a heartbeat in Helix.

The goal of this issue is to figure out why the machines are not heartbeating, and do any fixes needed so that we can resume deployment of the android queues.

This might involve also investigating #1448 and #1415, but part of the work is to determine if those issues are related.

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

@riarenas riarenas added Ops - Service Maintenance Used to track issues related to maintaining the services .NET Eng Supports Ops - P2 Operations task, priority 2 labels Jul 24, 2024
@ilyas1974 ilyas1974 removed the Ops - P2 Operations task, priority 2 label Jul 26, 2024
@ilyas1974 ilyas1974 assigned meghnave and unassigned ilyas1974 Mar 19, 2025
@ilyas1974
Copy link

Making this part of #3593 as changing the way we address these queues may resolve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ops - Service Maintenance Used to track issues related to maintaining the services .NET Eng Supports
Projects
None yet
Development

No branches or pull requests

3 participants