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.

Sign up for GitHub

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

Jump to bottom

Installation of kafka-webhook-eventing on CentOS 7 is not successful #7951

Closed
Taylorzhao opened this issue May 30, 2024 · 2 comments
Closed

Installation of kafka-webhook-eventing on CentOS 7 is not successful #7951

Taylorzhao opened this issue May 30, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/needs-user-input Issues which are waiting on a response from the reporter

Comments

@Taylorzhao
Copy link

Describe the bug
Install respectively on CentOS 7 and Ubuntu. It is normal on Ubuntu, but on CentOS 7, kafka-webhook-eventing keeps reporting the error as shown in the figure.
image
This is the system information, and the installed version is 1.14.
image

Information on a successful Ubuntu installation
image
@Taylorzhao Taylorzhao added the kind/bug Categorizes issue or PR as related to a bug. label May 30, 2024
@pierDipi
Copy link
Member

pierDipi commented Jun 6, 2024

@Taylorzhao is not clear to us why this is happening, are you still seeing the same issue? can you provide more information?

Sometimes, the webhook is slow to start and takes longer to reconcile the secret, so changing the delay here can help

eventing/config/core/deployments/webhook.yaml

Line 130 in f9156c8

initialDelaySeconds: 120

@pierDipi pierDipi added the triage/needs-user-input Issues which are waiting on a response from the reporter label Jun 6, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Sep 5, 2024

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.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 5, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/needs-user-input Issues which are waiting on a response from the reporter
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Taylorzhao @pierDipi