Skip to content

Retina agent pods crash looping after node upgrade (AKS) #1439

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
matthew-duval opened this issue Mar 17, 2025 · 2 comments · May be fixed by #1499
Open

Retina agent pods crash looping after node upgrade (AKS) #1439

matthew-duval opened this issue Mar 17, 2025 · 2 comments · May be fixed by #1499

Comments

@matthew-duval
Copy link

Describe the bug
After a node upgrade to AKSUbuntu-2004gen2fipscontainerd-202503.02.0 my retina agents are crash looping.

To Reproduce
Steps to reproduce the behavior:

  1. Create a private AKS cluster (v1.30.4) with Azure monitor enabled
  2. Ensure your system node pool uses the AKSUbuntu-2004gen2fipscontainerd-202503.02.0 node image version
  3. Observe the retina agent pods crash looping.

Expected behavior
The retina service to run as expected.

Screenshots

Image

Platform (please complete the following information):

  • OS: AKSUbuntu-2004gen2fipscontainerd-202503.02.0
  • Kubernetes Version: [e.g. 1.30.4]
  • Host: AKS
  • Retina Version: v0.0.25

Additional context
Add any other context about the problem here.

@nddq
Copy link
Contributor

nddq commented Mar 20, 2025

this might be a kernel issue, the kprobe is trying attach to a non-existence kernel func i think?

@anubhabMajumdar anubhabMajumdar linked a pull request Apr 1, 2025 that will close this issue
7 tasks
@anubhabMajumdar anubhabMajumdar linked a pull request Apr 1, 2025 that will close this issue
7 tasks
@ZhuowenNie
Copy link

May I know when will fix this issue, we met the same issue for AKSUbuntu-2004gen2fipscontainerd-202503.13.0"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

3 participants