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.

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

Unable to retrieve the results from sonobuoy after the successful test getting "could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources" for k3s distro #1980

Open
shyamreddy333 opened this issue Jul 17, 2024 · 4 comments

Comments

@shyamreddy333
Copy link

What steps did you take and what happened:
[A clear and concise description of what the bug is.]
Unable to retrieve the results from sonobuoy after the successful test runs that we had run in the remote machine using the kubeconfig file but while retrieving the results getting ""could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources: Get "https://:/api?timeout=32s": dial tcp : i/o timeout"

Earlier we used Service principal to sign into the azure and spin up the remote machine and we able to test and retrieve the results successfully at runtime from the remote machine but due to security waves we started using user assigned identity to the remote machine.

What did you expect to happen:

After using the UMI the sonobuoy run command working fine but not able to retrieve the results.

Anything else you would like to add:
2024-07-17T07:44:02.0920231Z 07:44:02 Sonobuoy plugins have completed. Preparing results for download.
2024-07-17T07:44:22.0918035Z 07:44:22 azure-arc-platform global complete passed
2024-07-17T07:44:22.0918491Z 07:44:22 azure-arc-agent-cleanup global complete passed
2024-07-17T07:44:22.0918727Z 07:44:22 Sonobuoy has completed. Use sonobuoy retrieve to get results.
2024-07-17T07:44:52.1094225Z time="2024-07-17T07:44:52Z" level=error msg="could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources: Get "https://:6443/api?timeout=32s": dial tcp :6443: i/o timeout"

Environment:

  • Sonobuoy version: v0.57.1
  • Kubernetes version: (use kubectl version): 1.28.10
  • Kubernetes installer & version: 1.28.10
  • Cloud provider or hardware configuration: Azure
  • OS (e.g. from /etc/os-release): Ubuntu 22.02
  • Sonobuoy tarball (which contains * below)
@shyamreddy333
Copy link
Author

Hi Could you please help on the above regarding the timeout issue, Much appreciated your responce, Thanks!

@v-vegujjula
Copy link

Hi, is there any update on the status? Please acknowledge if work is being done on it.

@shyamreddy333
Copy link
Author

Someone could you please help on this on priority as we are blocking with the conformance test and unable to progress on the work, Thanks!

@shyamreddy333 shyamreddy333 changed the title Unable to retrieve the results from sonobuoy after the successful test getting ""could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources: Get \"https://<Remote-machine-public-IP>:<port>/api?timeout=32s\": dial tcp <Remote-machine-public-IP>: i/o timeout"" Unable to retrieve the results from sonobuoy after the successful test getting "could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources" for k3s Aug 6, 2024
@shyamreddy333 shyamreddy333 changed the title Unable to retrieve the results from sonobuoy after the successful test getting "could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources" for k3s Unable to retrieve the results from sonobuoy after the successful test getting "could not create sonobuoy client: couldn't get sonobuoy api helper: could not get api group resources" for k3s distro Aug 6, 2024
@issimo1
Copy link

issimo1 commented Oct 17, 2024

Hi! I have used sonobuoy before, and this issue seems to be related to the configuration. Looking at logs https://:6443/api?timeout=32s,its lacks ip value. Checking environment value maybe can resolve

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

No branches or pull requests

3 participants