Skip to content

Fix panic when Failsafe configs are set to empty list #10354

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

sridhartigera
Copy link
Member

Description

FailSafeInBoundPorts and FailSafeOutBoundPorts can be set to an empty list "[]". This results in felix panicking.
This PR fixes #10338

Related issues/PRs

Todos

  • Tests
  • Documentation
  • Release note

Release Note

TBD

Reminder for the reviewer

Make sure that this PR has the correct labels and milestone set.

Every PR needs one docs-* label.

  • docs-pr-required: This change requires a change to the documentation that has not been completed yet.
  • docs-completed: This change has all necessary documentation completed.
  • docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

  • release-note-required: This PR has user-facing changes. Most PRs should have this label.
  • release-note-not-required: This PR has no user-facing changes.

Other optional labels:

  • cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
  • needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

@sridhartigera sridhartigera added docs-not-required Docs not required for this change release-note-not-required Change has no user-facing impact labels May 5, 2025
@sridhartigera sridhartigera requested a review from a team as a code owner May 5, 2025 18:57
@marvin-tigera marvin-tigera added this to the Calico v3.31.0 milestone May 5, 2025
Expect(err).To(BeNil())
}
},
Entry("Empty", "", nil, true),
Copy link
Member

Choose a reason for hiding this comment

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

Interesting, I would have expected an empty string to be set the default - but I guess we have logic to detect "unset" vs "set but empty"?

If that's the case, I wonder if the right fix is just in documentation to set "" instead of "[]" - WDYT?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah. I am not sure. Given that FailsafeInboundHostPorts is a list of ProtoPort, [] does make sense.

Copy link
Member

Choose a reason for hiding this comment

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

It doesn't really, based on the env var syntax.

tcp:22,udp:1.1.1.1:22,3033 - this is a valid value, and it has no [ or ] in it at all!

It's a valid YAML representation, but this isn't YAML we're talking about.

Copy link
Member Author

Choose a reason for hiding this comment

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

Better to fix the docs.

Copy link
Member Author

Choose a reason for hiding this comment

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

It makes sense to set the value as [] in the felix config but when configured as an env var it must be set to "".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required Docs not required for this change release-note-not-required Change has no user-facing impact
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Parsing value for FailsafeInboundHostPorts: "[]" (from environment variable) panic: runtime error: slice bounds out of range [:-1]
4 participants