-
Notifications
You must be signed in to change notification settings - Fork 74
Removing/Updating old publisher, ra, and pubsub resources #1380
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nachocano The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This won't actually work as the topic.spec.topic is immutable... |
…changed. That can only happen on updates to 0.16
RA and the old Pub/Sub subscription
RA and the old Pub/Sub subscription
/assign @Harwayne Integration are still failing due to monitoring, but that should have been fixed. Need to wait for 1 hour or so until we get a new nightly |
/retest |
2 similar comments
/retest |
/retest |
Synced with @grac3gao, it seems that the previous run picked a cluster with no workload identity enabled, so all tests failed... |
Installed 0.15, then created a few sources and a channel... Sent events, all worked... CAL topic: cloudauditlogssource-d56c6c3d-4ab4-4f38-8ded-9b207f51f1c5 --> cre-src_default_test-auditlogs_d56c6c3d-4ab4-4f38-8ded-9b207f51f1c5 scheduler topic: scheduler-0867c821-cf1c-4c2e-9909-5087f0d9e87e --> cre-src_default_test-scheduler_0867c821-cf1c-4c2e-9909-5087f0d9e87e storage topic: storage-111f1ef4-b734-4335-be58-fdf083e19e8d --> cre-src_default_test-storage_111f1ef4-b734-4335-be58-fdf083e19e8d |
Few problems I faced. The controller seems to be trying to export metrics to stackdriver, even custom metrics is disabled. Not sure if this is a problem from the upgrade itself or if it's in master. Failing to read the auth defaults from the new configMap: Failing to delete the old SD sink:
The Channel didn't work until I delete the subscription and created it again. Will keep on investigating |
Still getting errors trying to delete the SD sink. Given that is not a topic/subscription, but rather some SD internal stuff, I think is fine to leave it as is. As the code is structured, given that the sink should be in the status of the resource, it will keep on using that old sink name and things will keep on working. |
/test pull-google-knative-gcp-wi-tests |
/retest
…On Mon, Jul 6, 2020 at 8:20 PM Knative test reporter robot < ***@***.***> wrote:
The following jobs failed:
Test name Triggers Retries
pull-google-knative-gcp-wi-tests 0/3
Failed non-flaky tests preventing automatic retry of
pull-google-knative-gcp-wi-tests:
github.com/google/knative-gcp/test/e2e.TestCloudAuditLogsSourceWithTargetgithub.com/google/knative-gcp/test/e2e.TestGCPBrokerTracing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1380 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD65DELCLNYFST3YINJNFTR2KIBJANCNFSM4ORWNETQ>
.
|
/retest |
/retest
…On Mon, Jul 6, 2020 at 9:28 PM Knative test reporter robot < ***@***.***> wrote:
The following jobs failed:
Test name Triggers Retries
pull-google-knative-gcp-wi-tests 0/3
Failed non-flaky tests preventing automatic retry of
pull-google-knative-gcp-wi-tests:
github.com/google/knative-gcp/test/e2e.TestGCPBrokerTracing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1380 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD65DGUZRTAMYGI4NNACJLR2KQALANCNFSM4ORWNETQ>
.
|
/retest
…On Mon, Jul 6, 2020 at 10:06 PM Knative test reporter robot < ***@***.***> wrote:
The following jobs failed:
Test name Triggers Retries
pull-google-knative-gcp-wi-tests 0/3
Failed non-flaky tests preventing automatic retry of
pull-google-knative-gcp-wi-tests:
github.com/google/knative-gcp/test/e2e.TestGCPBrokerTracing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1380 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD65DAB2QJXAZY65POM75DR2KUOZANCNFSM4ORWNETQ>
.
|
The following jobs failed:
Automatically retrying due to test flakiness... |
The following is the coverage report on the affected files.
|
All sources working. Channel still does not mark the subscription ready when upgrading from 0.15. |
/lgtm |
/hold cancel Cancelling the hold as I was this in before the CI breaks again and I need to do a bunch of re-tests. |
Fixes #1217
Proposed Changes
I first tried deleting the PubSub resources instead of our wrappers K8s objects, but that has the problem that we cannot update them to use the newer topic names, as spec.topic is immutable.
Release Note
Docs