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

Sequence will still use In-memory channel even if it is not installed #7886

Closed
Leo6Leo opened this issue May 2, 2024 · 3 comments
Closed
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-user-input Issues which are waiting on a response from the reporter

Comments

@Leo6Leo
Copy link
Member

Leo6Leo commented May 2, 2024

Describe the bug
Sequence will still use In-memory channel even if it is not installed.

After switching to the Kafka Channel and removing the in-memory-channel, the sequence still attempts to use the in-memory channel. Ideally, it should default to using the installed channel. Detailed Logs and procedures to reproduce will be added soon here.

Expected behavior
A clear and concise description of what you expected to happen.

To Reproduce
Steps to reproduce the behavior.

Knative release version

Additional context
Add any other context about the problem here such as proposed priority

@Leo6Leo Leo6Leo added the kind/bug Categorizes issue or PR as related to a bug. label May 2, 2024
@pierDipi
Copy link
Member

pierDipi commented May 8, 2024

@Leo6Leo we need more details here

@pierDipi pierDipi added the triage/needs-user-input Issues which are waiting on a response from the reporter label May 8, 2024
@pierDipi
Copy link
Member

@Leo6Leo can you add more details here?

@Leo6Leo
Copy link
Member Author

Leo6Leo commented May 15, 2024

Thank you for the reminder @pierDipi!

I just tried to test it out from scratch, and find out that was a mistake. The reason why the issue happens is because I didn't change the name of the channel template in the Sequence yaml. After updating it, everything works as expected.

Sorry for the inconvenience! Now closing this issue.

@Leo6Leo Leo6Leo closed this as not planned Won't fix, can't repro, duplicate, stale May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/needs-user-input Issues which are waiting on a response from the reporter
Projects
None yet
Development

No branches or pull requests

2 participants