Profiling runs fail locally on Fedora Linux.

[twoGiants]

Bug

Profiling runs fail locally on Fedora Linux. It fails before the profilers are attached and before "Sacura" is started.

The command is:

> export EVENT=alloc
./hack/run.sh profiler

Error

This is the last output before the script fails ends:

[2025-10-31 13:27:59,794] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2025-10-31 13:27:59,898] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2025-10-31 13:28:00,099] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
Error while executing topic command : Topic 'attack-ingress-single' already exists.
[2025-10-31 13:28:00,449] ERROR org.apache.kafka.common.errors.TopicExistsException: Topic 'attack-ingress-single' already exists.
 (kafka.admin.TopicCommand$)

Additional Context

• Fedora Linux 42

> java --version
openjdk 21.0.8 2025-07-15
OpenJDK Runtime Environment (Red_Hat-21.0.8.0.9-1) (build 21.0.8+9)
OpenJDK 64-Bit Server VM (Red_Hat-21.0.8.0.9-1) (build 21.0.8+9, mixed mode, sharing)

/kind help-wanted

[knative-prow]

@twoGiants: The label(s) kind/help-wanted cannot be applied, because the repository doesn't have them.

Details

In response to this:

Bug

Profiling runs fail locally on Fedora Linux. It fails before the profilers are attached and before "Sacura" is started.

The command is:

> export EVENT=alloc
./hack/run.sh profiler

Error

This is the last output before the script fails ends:

[2025-10-31 13:27:59,794] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2025-10-31 13:27:59,898] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
[2025-10-31 13:28:00,099] WARN [AdminClient clientId=adminclient-1] Connection to node -1 (localhost/127.0.0.1:9092) could not be established. Broker may not be available. (org.apache.kafka.clients.NetworkClient)
Error while executing topic command : Topic 'attack-ingress-single' already exists.
[2025-10-31 13:28:00,449] ERROR org.apache.kafka.common.errors.TopicExistsException: Topic 'attack-ingress-single' already exists.
(kafka.admin.TopicCommand$)

Additional Context

• Fedora Linux 42

> java --version
openjdk 21.0.8 2025-07-15
OpenJDK Runtime Environment (Red_Hat-21.0.8.0.9-1) (build 21.0.8+9)
OpenJDK 64-Bit Server VM (Red_Hat-21.0.8.0.9-1) (build 21.0.8+9, mixed mode, sharing)

/kind help-wanted

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-sigs/prow repository.

[twoGiants]

/kind bug
/help

[knative-prow]

@twoGiants:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/kind bug
/help

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-sigs/prow repository.

[namanONcode]

@knative-prow-robot @twoGiants assign me this

[namanONcode]

@twoGiants The error shows two issues

1.Kafka broker connection failures - Cannot connect to localhost:9092
2.Topic already exists error - Topic 'attack-ingress-single' already exists

The script is failing because it's trying to create a Kafka topic that already exists, and the topic creation command exits with an error code.

The connection warnings to localhost:9092 suggest Kafka may not be fully started when the topic creation runs. Consider adding a retry loop before creating topics

QUICK FIX : Modify the Kafka topic creation in hack/run.sh to handle pre-existing topics.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.