Open matzew opened 4 years ago
In the eventing controller
log I see something like:
{
"level": "info",
"ts": "2020-04-15T12:46:25.361Z",
"logger": "controller.event-broadcaster",
"caller": "record/event.go:274",
"msg": "Event(v1.ObjectReference{Kind:\"PingSource\", Namespace:\"default\", Name:\"test-ping-source2\", UID:\"9c85dc7b-fc75-438d-8f0a-3c5973afd4fd\", APIVersion:\"sources.knative.dev/v1alpha1\", ResourceVersion:\"1931\", FieldPath:\"\"}): type: 'Warning' reason: 'SinkNotFound' Sink not found: {\"ref\":{\"kind\":\"Service\",\"namespace\":\"default\",\"name\":\"event-display2\",\"apiVersion\":\"serving.knative.dev/v1\"}}",
"commit": "02bc516"
}
the ksvc
objects are READY
:
k get ksvc
NAME URL LATESTCREATED LATESTREADY READY REASON
event-display http://event-display.default.example.com event-display-rntw2 event-display-rntw2 True
event-display2 http://event-display2.default.example.com event-display2-rwscr event-display2-rwscr True
but the not so the sources:
k get sources
NAME READY REASON SINK AGE
pingsource.sources.knative.dev/test-ping-source False NotFound 14m
pingsource.sources.knative.dev/test-ping-source2 False NotFound 12m
when I kill the eventing controller
pod,
the sources are correctly reconciled and eventually will be true. but only when I kill the pod...
The first failure is expected. The watch on the ksvc kind fails.
Why it does not recover with the new source is interesting...
@matzew this scenario works with mtping because the receive adapter is created after the sink existence check. However there is no sink tracker, strange...
I'm getting a similar behavior on 0.16:
source.yaml:
apiVersion: sources.knative.dev/v1alpha2
kind: PingSource
metadata:
name: source
spec:
schedule: "* * * * *"
jsonData: '{"message": "Hello world from ping!"}'
sink:
ref:
apiVersion: serving.knative.dev/v1
kind: Service
name: service
service.yaml:
apiVersion: serving.knative.dev/v1
kind: Service
metadata:
name: service
spec:
template:
spec:
containers:
- image: docker.io/meteatamel/event-display:v1
error:
{"level":"info","ts":"2020-07-28T17:40:31.192Z","logger":"controller.event-broadcaster","caller":"record/event.go:281","msg":"Event(v1.ObjectReference{Kind:\"PingSource\", Namespace:\"default\", Name:\"source\", UID:\"0739a3e2-2f22-4b5e-b905-10a6292eb92a\", APIVersion:\"sources.knative.dev/v1alpha2\", ResourceVersion:\"5439586\", FieldPath:\"\"}): type: 'Warning' reason: 'SinkNotFound' Sink not found: {\"ref\":{\"kind\":\"Service\",\"namespace\":\"default\",\"name\":\"service\",\"apiVersion\":\"serving.knative.dev/v1\"}}","commit":"acdd118"}
kubectl get sources:
NAME READY REASON SINK AGE
pingsource.sources.knative.dev/source False NotFound 2m5s
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
.
Is there a solution to this problem ? I am using camel k and have the same issue. These are the steps I am doing.
echo "Creating the event watcher service account"
envsubst < createEventsSA.yaml | oc apply -f -
echo "Creating the event watcher role"
envsubst < eventWatcherRole.yaml | oc apply -f -
echo "Creating the event watcher role binding"
envsubst < eventWatcherRoleBinding.yaml | oc apply -f -
echo "Creating the event watcher channel"
envsubst < eventWatcherChannel.yaml | oc apply -f -
echo "Creating the event watcher apiserversource"
envsubst < eventWatcherapiserversource.yaml | oc apply -f -
and then I start the service but facing the same issue.
kamel run --dev --property 'quarkus.log.category."org.apache.camel".level'=DEBUG --dependency=camel-jackson --dependency=camel-rest NamespaceEventWatcher.java -n testproject
All Yaml files attached with the java code
@feitnomore @grantr - Can you pls assist here
/remove-lifecycle stale /reopen /triage accepted
@lionelvillard: Reopened this issue.
Describe the bug
create a ping source before a ksvc, and notice that it will never go to
READY
state.Expected behavior
once the
ksvc
is there, it should go to ready state.To Reproduce
Notice that none of the PingSources becomes Ready
Knative release version
0.14
Additional context
here is the yamls, I used:
ping.yaml
:ksvc.yaml
:ping2.yaml
:ksvc2.yaml
: