Skip to content

Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) #936

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

Merged
merged 1 commit into from
Mar 29, 2021

Conversation

syedriko
Copy link
Contributor

@syedriko syedriko commented Mar 6, 2021

Description

Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate)

  • Upgraded Kafka to 2.7.0
  • Switched the kafka logforwarding test to run over TLS
  • The Kafka broker certificate chain is Server - Intermediate CA - Root CA
  • Added Java Key Store generation functions

/cc @alanconway
/assign @jcantrill

Links

@openshift-ci-robot openshift-ci-robot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 6, 2021
@syedriko syedriko changed the title WIP: Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) Mar 9, 2021
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 9, 2021
@syedriko
Copy link
Contributor Author

syedriko commented Mar 9, 2021

/test e2e-operator

@syedriko
Copy link
Contributor Author

syedriko commented Mar 9, 2021

@jcantrill Could you bless this

Copy link
Contributor

@jcantrill jcantrill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@@ -138,7 +141,7 @@ func NewBrokerStatefuleSet(namespace string) *apps.StatefulSet {
Containers: []v1.Container{
{
Name: kafkaBrokerContainerName,
Image: "solsson/kafka:2.4.1",
Image: "solsson/kafka@sha256:754cd2e82bbddd37a81d214be33fd15eb429913f9ac51dedf89d446876b95ffc",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we using a specific sha in stead of a more digestible version number that is easier to document?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no tag for 2.7.0, it's just "latest". Between latest and sha I picked sha.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not actually sure it's a good idea to rely on images from Docker Hub now that they introduced rate limiting. We could start with copying these to quay. Or better yet switch to Strimzi.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if you have concerns, feel free to push to quay.io/openshift-logging. Seems reasonable for us to have a controlled copy of the image against which we test.

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 9, 2021
@jcantrill jcantrill added release/5.1 backport/5.0 backport/4.6 and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 9, 2021
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 11, 2021
@syedriko
Copy link
Contributor Author

/test e2e-operator

4 similar comments
@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko
Copy link
Contributor Author

/test e2e-operator

3 similar comments
@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko
Copy link
Contributor Author

/test e2e-operator

@syedriko syedriko changed the title Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) Bug 1904380: Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) Mar 18, 2021
@openshift-ci-robot
Copy link

@syedriko: This pull request references Bugzilla bug 1904380, which is invalid:

  • expected the bug to target the "4.8.0" release, but it targets "4.6.z" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1904380: Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 18, 2021
@syedriko syedriko changed the title Bug 1904380: Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) Mar 18, 2021
@openshift-ci-robot openshift-ci-robot removed bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Mar 18, 2021
@openshift-ci-robot
Copy link

@syedriko: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate)

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@syedriko
Copy link
Contributor Author

/test e2e-operator

@openshift-ci-robot openshift-ci-robot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2021
…ls with error "state=error: certificate verify failed (unable to get local issuer certificate)

- Upgraded Kafka to 2.7.0 and pushed images to quay.io
- Switched the kafka logforwarding test to run over TLS
- The Kafka broker certificate chain is Server - Intermediate CA - Root CA
- Added Java Key Store generation functions
- Removed Kafka consumer output to stdio to avoid recursive logs
@syedriko
Copy link
Contributor Author

@jcantrill yea? nay?

Copy link
Contributor

@alanconway alanconway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanconway, syedriko

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 29, 2021
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 24a0432 into openshift:master Mar 29, 2021
@syedriko
Copy link
Contributor Author

/cherrypick release-5.0

@openshift-cherrypick-robot

@syedriko: #936 failed to apply on top of branch "release-5.0":

Applying: Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) - Upgraded Kafka to 2.7.0 and pushed images to quay.io - Switched the kafka logforwarding test to run over TLS - The Kafka broker certificate chain is Server - Intermediate CA - Root CA - Added Java Key Store generation functions - Removed Kafka consumer output to stdio to avoid recursive logs
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	vendor/modules.txt
Falling back to patching base and 3-way merge...
Auto-merging vendor/modules.txt
CONFLICT (content): Merge conflict in vendor/modules.txt
Auto-merging go.sum
Auto-merging go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate) - Upgraded Kafka to 2.7.0 and pushed images to quay.io - Switched the kafka logforwarding test to run over TLS - The Kafka broker certificate chain is Server - Intermediate CA - Root CA - Added Java Key Store generation functions - Removed Kafka consumer output to stdio to avoid recursive logs
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherrypick release-5.0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@syedriko syedriko deleted the bz_1904380 branch June 3, 2021 18:06
pmoogi-redhat pushed a commit to pmoogi-redhat/cluster-logging-operator that referenced this pull request Apr 26, 2022
Bug 1904380 - Forwarding logs to Kafka using Chained certificates fails with error "state=error: certificate verify failed (unable to get local issuer certificate)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport/4.6 backport/5.0 lgtm Indicates that a PR is ready to be merged. release/5.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants