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

Strange effects with wrong apiVersion/kind in SinkBinding subject #2464

Closed
rhuss opened this issue Jan 29, 2020 · 4 comments
Closed

Strange effects with wrong apiVersion/kind in SinkBinding subject #2464

rhuss opened this issue Jan 29, 2020 · 4 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@rhuss
Copy link
Contributor

rhuss commented Jan 29, 2020

Describe the bug

When using a subject in a SinkBinding that refers to either a non-podspecable resource (e.g. CronJob:batch/v1beta1) or a faulty resource describption (like Job:batch/v1beta1 instead of Job:batch/v1), then no error is returned, but the status of this binding remains:

status:
  conditions:
  - lastTransitionTime: "2020-01-29T15:09:09Z"
    status: Unknown
    type: Ready

Furthermore, this resource can not be deleted anymore, because the delete operation hangs forever. In addition, a namespace with this faulty sink binding can also not delete (the namespace sticks in "Terminating" status)

Expected behavior

I would expect:

  • A clear error indication describing that the subject specification is wrong. Either as part of the status conditions or, if possible, already by an admission controller when verifying the source.
  • It should be possible to delete such resource again.

To Reproduce
Steps to reproduce the behavior.

Just apply

apiVersion: sources.knative.dev/v1alpha1
kind: SinkBinding
metadata:
  name: bind-heartbeat-2
spec:
  subject:
    apiVersion: batch/v1
    # This is wrong, should be Job
    kind: CronJob
    selector:
      matchLabels:
        app: heartbeat-cron
  sink:
    ref:
      apiVersion: serving.knative.dev/v1
      kind: Service
      name: edisplay

Knative release version

Eventing 0.12.0

Additional context

Tried on minikube

@rhuss rhuss added the kind/bug Categorizes issue or PR as related to a bug. label Jan 29, 2020
@tzununbekov
Copy link
Member

fwiw, we're working on a fix
https://github.com/triggermesh/pkg/commit/76b1a0d8134f5a5d4172a8b95b0e6ce47b92c0f7

@github-actions
Copy link

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 Nov 25, 2020
@rhuss
Copy link
Contributor Author

rhuss commented Dec 3, 2020

/remove-lifecycle stale

@knative-prow-robot knative-prow-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 3, 2020
@slinkydeveloper
Copy link
Contributor

It sounds like this was fixed with https://github.com/triggermesh/pkg/commit/76b1a0d8134f5a5d4172a8b95b0e6ce47b92c0f7, reopen if you need it

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.
Projects
None yet
Development

No branches or pull requests

5 participants