Skip to content
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

Add warning log message about which config files to try #1657

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

saschagrunert
Copy link
Member

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

If the specified --config does not exist, then crictl will try the binary directory as last resort. We now log that behavior so that end users don't think unintentionally they specified the wrong --config value:

> sudo ./build/bin/linux/amd64/crictl --config ~/downloads/crictl.yaml config --list
WARN[0000] Config "/home/x/downloads/crictl.yaml" does not exist, trying: "/home/s/go/src/sigs.k8s.io/cri-tools/build/bin/linux/amd64/crictl.yaml"
FATA[0000] load config file: stat /home/sascha/go/src/sigs.k8s.io/cri-tools/build/bin/linux/amd64/crictl.yaml: no such file or directory

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

If the specified `--config` does not exist, then crictl will try the
binary directory as last resort. We now log that behavior so that end
users don't think unintentionally they specified the wrong `--config`
value:

```
> sudo ./build/bin/linux/amd64/crictl --config ~/downloads/crictl.yaml config --list
WARN[0000] Config "/home/x/downloads/crictl.yaml" does not exist, trying: "/home/s/go/src/sigs.k8s.io/cri-tools/build/bin/linux/amd64/crictl.yaml"
FATA[0000] load config file: stat /home/sascha/go/src/sigs.k8s.io/cri-tools/build/bin/linux/amd64/crictl.yaml: no such file or directory
```

Signed-off-by: Sascha Grunert <[email protected]>
@k8s-ci-robot k8s-ci-robot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Oct 24, 2024
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 24, 2024
Copy link
Member

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

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

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 24, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert, SergeyKanzhelev

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

@k8s-ci-robot k8s-ci-robot merged commit 5593e6b into kubernetes-sigs:master Oct 24, 2024
34 checks passed
@saschagrunert saschagrunert deleted the warning-log branch October 24, 2024 17:43
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. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants