agent: runtime error when AGENT_POLICY is enabled on s390x
BbolroC opened this issue · comments
Hyounggyu Choi commented
Description of problem
The following runtime error has been observed on s390x when AGENT_POLICY
is enabled for kata-agent
:
{"msg":"announce","level":"INFO","ts":"2024-05-14T10:11:13.59409992Z","pid":"317046","name":"kata-agent","subsystem":"root","version":"0.1.0","source":"agent","api-version":"0.0.1","agent-version":"3.4.0","extra-features":"[\"agent-policy\", \"guest-pull\", \"seccomp\"]","config":"AgentConfig { debug_console: false, dev_mode: false, log_level: Info, hotplug_timeout: 3s, debug_console_vport: 0, log_vport: 0, container_pipe_size: 0, server_addr: \"vsock://-1:1024\", passfd_listener_port: 0, unified_cgroup_hierarchy: false, tracing: false, supports_seccomp: true, https_proxy: \"\", no_proxy: \"\", guest_components_rest_api: Resource }","agent-commit":"3.4.0"}
{"msg":"https_proxy is not set (environment variable not found)","level":"INFO","ts":"2024-05-14T10:11:13.606600028Z","name":"kata-agent","source":"agent","pid":"317046","subsystem":"image","version":"0.1.0"}
{"msg":"no_proxy is not set (environment variable not found)","level":"INFO","ts":"2024-05-14T10:11:13.606621094Z","pid":"317046","version":"0.1.0","source":"agent","subsystem":"image","name":"kata-agent"}
Aborted (core dumped)
A working agent should run like:
{"msg":"announce","level":"INFO","ts":"2024-05-14T10:11:32.950484195Z","pid":"317185","name":"kata-agent","version":"0.1.0","source":"agent","subsystem":"root","agent-commit":"3.4.0","agent-version":"3.4.0","extra-features":"[\"guest-pull\", \"seccomp\"]","config":"AgentConfig { debug_console: false, dev_mode: false, log_level: Info, hotplug_timeout: 3s, debug_console_vport: 0, log_vport: 0, container_pipe_size: 0, server_addr: \"vsock://-1:1024\", passfd_listener_port: 0, unified_cgroup_hierarchy: false, tracing: false, supports_seccomp: true, https_proxy: \"\", no_proxy: \"\", guest_components_rest_api: Resource }","api-version":"0.0.1"}
{"msg":"https_proxy is not set (environment variable not found)","level":"INFO","ts":"2024-05-14T10:11:32.961566247Z","pid":"317185","version":"0.1.0","subsystem":"image","source":"agent","name":"kata-agent"}
{"msg":"no_proxy is not set (environment variable not found)","level":"INFO","ts":"2024-05-14T10:11:32.96158746Z","pid":"317185","source":"agent","name":"kata-agent","subsystem":"image","version":"0.1.0"}
{"msg":"starting uevents handler","level":"INFO","ts":"2024-05-14T10:11:32.961617328Z","source":"agent","name":"kata-agent","pid":"317185","version":"0.1.0","subsystem":"uevent"}
{"msg":"ttRPC server started","level":"INFO","ts":"2024-05-14T10:11:32.977351902Z","name":"kata-agent","source":"agent","subsystem":"rpc","pid":"317185","version":"0.1.0","address":"vsock://-1:1024"}
... listening ...
This leads to a crash for a guest VM and makes all e2e tests for the platform failing.
For now, we should disable the feature on s390x until the issue is resolved.
Hyounggyu Choi commented
I'm closing this because the issue is resolved by #9632.