Skip to content

OADP-3562: Fix controller panic on secret key-value parsing#1529

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
stillalearner:fix_oadp3562
Oct 1, 2024
Merged

OADP-3562: Fix controller panic on secret key-value parsing#1529
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
stillalearner:fix_oadp3562

Conversation

@stillalearner
Copy link
Copy Markdown
Contributor

Fixes -> https://issues.redhat.com/browse/OADP-3562

Tested successfully with empty value for key.

status:
conditions:

  • lastTransitionTime: "2024-09-24T09:04:15Z"
    message: secret parsing error in key AZURE_STORAGE_ACCOUNT_ACCESS_KEY
    reason: Error
    status: "False"
    type: Reconciled

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 24, 2024
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Sep 24, 2024

@stillalearner: This pull request references OADP-3562 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.18.0" version, but no target version was set.

Details

In response to this:

Fixes -> https://issues.redhat.com/browse/OADP-3562

Tested successfully with empty value for key.

status:
conditions:

  • lastTransitionTime: "2024-09-24T09:04:15Z"
    message: secret parsing error in key AZURE_STORAGE_ACCOUNT_ACCESS_KEY
    reason: Error
    status: "False"
    type: Reconciled

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested review from kaovilai and mpryc September 24, 2024 09:16
Copy link
Copy Markdown

@mateusoliveira43 mateusoliveira43 left a comment

Choose a reason for hiding this comment

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

Thanks @stillalearner !

But lets ensure we never make this mistake again. Please add loggercheck to .golangci.yaml, as described

# - ineffassign
# - misspell

   # - ineffassign
+  - loggercheck
   # - misspell

Running linters on master with this change, the error is caught

$ make lint
PATH/bin/golangci-lint run
controllers/registry.go:475:47: odd number of arguments passed as key-value pairs for logging (loggercheck)
		r.Log.Info("Could not parse secret for %s", key)
		                                            ^
make: *** [Makefile:553: lint] Error 1

Copy link
Copy Markdown

@mateusoliveira43 mateusoliveira43 left a comment

Choose a reason for hiding this comment

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

For next PRs, do not forget to use the project's PR template for the PR's description

Some examples of using it

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 24, 2024
Copy link
Copy Markdown
Member

@kaovilai kaovilai left a comment

Choose a reason for hiding this comment

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

/lgtm

@kaovilai
Copy link
Copy Markdown
Member

/hold for CI fix

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 24, 2024
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 24, 2024
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Sep 24, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kaovilai, mateusoliveira43, shubham-pampattiwar, stillalearner

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [kaovilai,mateusoliveira43,shubham-pampattiwar]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mateusoliveira43
Copy link
Copy Markdown

/unhold
E2E tests are working again

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 30, 2024
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD ce8546d and 2 for PR HEAD 8d9f5f5 in total

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Oct 1, 2024

@stillalearner: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot openshift-merge-bot Bot merged commit 5b0b9fc into openshift:master Oct 1, 2024
stillalearner added a commit to stillalearner/oadp-operator that referenced this pull request Oct 9, 2024
stillalearner added a commit to stillalearner/oadp-operator that referenced this pull request Oct 9, 2024
openshift-merge-bot Bot pushed a commit that referenced this pull request Oct 9, 2024
openshift-merge-bot Bot pushed a commit that referenced this pull request Oct 9, 2024
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants