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

Default cni_config_dir doesn't appear to be honored. #9028

Closed
angrycub opened this issue Oct 5, 2020 · 2 comments · Fixed by #10870
Closed

Default cni_config_dir doesn't appear to be honored. #9028

angrycub opened this issue Oct 5, 2020 · 2 comments · Fixed by #10870

Comments

@angrycub
Copy link
Contributor

angrycub commented Oct 5, 2020

Nomad version

Nomad v0.12.5 (514b0d6)

Operating system and Environment details

centos 7

Issue

Documentation says that /opt/cni/config is default configuration path; however if it is not explicitly set, the fingerprinter returns client.fingerprint_mgr: CNI config dir is not set or does not exist, skipping: cni_config_dir=

I do see that there is a default being set in

CNIConfigDir: "/opt/cni/config",

So I'm not sure why we aren't seeing the expected default.

@grumpy-programmer
Copy link

grumpy-programmer commented Oct 10, 2020

I confirm that. Today I have to define cni_path & cni_config_dir in client config:

client {
  cni_path = "/opt/cni/bin"
  cni_config_dir = "/opt/cni/config"
}

Default values are overriten in agent convertClientConfig function:

conf.CNIPath = agentConfig.Client.CNIPath
conf.CNIConfigDir = agentConfig.Client.CNIConfigDir

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants