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

Local run fails #77

Closed
FedeDP opened this issue Feb 7, 2024 · 6 comments
Closed

Local run fails #77

FedeDP opened this issue Feb 7, 2024 · 6 comments
Labels
bug Something isn't working

Comments

@FedeDP
Copy link
Collaborator

FedeDP commented Feb 7, 2024

Describe the bug

I was testing new ghcr images, and i discovered that we are no more able to run kernel-testing framework locally because of:

failed: [localhost] (item={'name': 'ubuntu-5.8', 'kernel': 'ghcr.io/falcosecurity/kernel-testing/ubuntu-kernel:5.8-x86_64-main', 'rootfs': 'ghcr.io/falcosecurity/kernel-testing/ubuntu-image:5.8-x86_64-main', 'arch': 'x86_64'}) => {"ansible_loop_var": "item", "changed": false, "cmd": ["ignite", "run", "--config", "./roles/bootstrap/files/ubuntu-5.8.yaml", "--runtime", "docker"], "delta": "0:00:27.892242", "end": "2024-02-07 16:18:03.571150", "item": {"arch": "x86_64", "kernel": "ghcr.io/falcosecurity/kernel-testing/ubuntu-kernel:5.8-x86_64-main", "name": "ubuntu-5.8", "rootfs": "ghcr.io/falcosecurity/kernel-testing/ubuntu-image:5.8-x86_64-main"}, "msg": "non-zero return code", "rc": 1, "start": "2024-02-07 16:17:35.678908", "stderr": "", "stderr_lines": [], "stdout": "time=\"2024-02-07T16:17:35+01:00\" level=info msg=\"Starting image import...\"\ntime=\"2024-02-07T16:17:57+01:00\" level=info msg=\"Imported OCI image \\\"ghcr.io/falcosecurity/kernel-testing/ubuntu-image:5.8-x86_64-main\\\" (1.3 GB) to base image with UID \\\"6e27ede8caf5ca28\\\"\"\ntime=\"2024-02-07T16:17:58+01:00\" level=info msg=\"Imported OCI image \\\"ghcr.io/falcosecurity/kernel-testing/ubuntu-kernel:5.8-x86_64-main\\\" (47.3 MB) to kernel image with UID \\\"9316b9fc3efe25d6\\\"\"\ntime=\"2024-02-07T16:18:01+01:00\" level=info msg=\"Created VM with ID \\\"502a2c4fb695c2d0\\\" and name \\\"ubuntu-5.8-here-goes-the-id\\\"\"\ntime=\"2024-02-07T16:18:02+01:00\" level=info msg=\"Pulling image \\\"weaveworks/ignite:dev\\\"...\"\ntime=\"2024-02-07T16:18:03+01:00\" level=fatal msg=\"Error response from daemon: manifest for weaveworks/ignite:dev not found: manifest unknown: manifest unknown\"", "stdout_lines": ["time=\"2024-02-07T16:17:35+01:00\" level=info msg=\"Starting image import...\"", "time=\"2024-02-07T16:17:57+01:00\" level=info msg=\"Imported OCI image \\\"ghcr.io/falcosecurity/kernel-testing/ubuntu-image:5.8-x86_64-main\\\" (1.3 GB) to base image with UID \\\"6e27ede8caf5ca28\\\"\"", "time=\"2024-02-07T16:17:58+01:00\" level=info msg=\"Imported OCI image \\\"ghcr.io/falcosecurity/kernel-testing/ubuntu-kernel:5.8-x86_64-main\\\" (47.3 MB) to kernel image with UID \\\"9316b9fc3efe25d6\\\"\"", "time=\"2024-02-07T16:18:01+01:00\" level=info msg=\"Created VM with ID \\\"502a2c4fb695c2d0\\\" and name \\\"ubuntu-5.8-here-goes-the-id\\\"\"", "time=\"2024-02-07T16:18:02+01:00\" level=info msg=\"Pulling image \\\"weaveworks/ignite:dev\\\"...\"", "time=\"2024-02-07T16:18:03+01:00\" level=fatal msg=\"Error response from daemon: manifest for weaveworks/ignite:dev not found: manifest unknown: manifest unknown\""]}

Basically, weaveworks/ignite:dev was shutted down; our libs tests do work because that image is cached on the cncf nodes where the tests run.
IMHO we should at the very least compeltely quit relying on weaveworks images.
We use:

weaveworks/ignite-kernel:5.14.16

in ansible-playbooks/group_vars/all/vars.yml
and

weaveworks/ubuntu-kernel:5.14.16

in builder and modernprobe-builder Dockerfile.kernel.
Also, we should patch https://github.com/therealbobo/ignite to use our own weaveworks/ignite:dev image as default (or a parameter could be enforced using --sandbox-image cli option).

@poiana
Copy link

poiana commented Feb 7, 2024

There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@FedeDP
Copy link
Collaborator Author

FedeDP commented Feb 7, 2024

/kind bug

@poiana
Copy link

poiana commented Feb 7, 2024

@FedeDP: The label(s) kind/bug cannot be applied, because the repository doesn't have them.

In response to this:

/kind bug

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@FedeDP FedeDP added bug Something isn't working and removed needs-kind labels Feb 7, 2024
@FedeDP
Copy link
Collaborator Author

FedeDP commented Feb 7, 2024

Also, we should patch https://github.com/therealbobo/ignite to use our own weaveworks/ignite:dev image as default (or a parameter could be enforced using --sandbox-image cli option).

Regarding this last point, weaveworks/ignite:dev is provided by calling ignite-spawn make target on ignite repo: make ignite-spawn.
We can assume that our cncf nodes will always have it; we should probably document this one, until we free ourselves from ignite at least.

@FedeDP
Copy link
Collaborator Author

FedeDP commented Feb 8, 2024

/close

Added more bullet points to the tracking issue: falcosecurity/libs#1224

@poiana poiana closed this as completed Feb 8, 2024
@poiana
Copy link

poiana commented Feb 8, 2024

@FedeDP: Closing this issue.

In response to this:

/close

Added more bullet points to the tracking issue: falcosecurity/libs#1224

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants