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

CI: When cilium-cli container fails, get logs #1426

Open
squeed opened this issue Mar 1, 2023 · 0 comments
Open

CI: When cilium-cli container fails, get logs #1426

squeed opened this issue Mar 1, 2023 · 0 comments
Assignees
Labels
area/CI Continuous Integration testing issue or flake ci/flake Issues tracking failing (integration or unit) tests.

Comments

@squeed
Copy link
Contributor

squeed commented Mar 1, 2023

For example, look at https://github.com/cilium/cilium-cli/actions/runs/4302151503/jobs/7500262699 -- the only log entry provided is Error from server: Get "https://10.122.240.4:10250/containerLogs/kube-system/cilium-cli-fqz8k/test?timestamps=true": No agent available. In reality, thanks to GCP's log aggregation, the real failure was

"looks like "https://helm.cilium.io" is not a valid chart repository or cannot be reached: Get "https://helm.cilium.io/index.yaml": tls: failed to verify certificate: x509: certificate signed by unknown authority"

So, we should add a workflow step that dumps the logs of all cilium-cli containers. Optionally on failure, but probably all the time --there isn't that much logging.

@squeed squeed added area/CI Continuous Integration testing issue or flake ci/flake Issues tracking failing (integration or unit) tests. labels Mar 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI Continuous Integration testing issue or flake ci/flake Issues tracking failing (integration or unit) tests.
Projects
None yet
Development

No branches or pull requests

2 participants