-
Notifications
You must be signed in to change notification settings - Fork 682
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
CHEF-3917 Troubleshooting Page for Chef Licensing issues/errors #6612
Conversation
✅ Deploy Preview for chef-inspec ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
This error encountered with Chef InSpec, version 6 or higher, is specifically related to `licenses.yaml` file. | ||
It indicates that the version of file format used in the file is either unsupported or is invalid. | ||
It is a requirement for `licenses.yaml` file to use the latest supported file format version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't seen a license.yaml
file in the install docs in #6574. We should add reference to this file there or delete these two sections here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We definitely need these 2 sections here because these errors can happen. So maybe we should include this on install docs. Thoughts @clintoncwolfe ?
|
||
- Service Availability: If it's a Local Licensing Service, ensure that it's properly configured and operational. Any misconfigurations or issues with the local service could lead to connection problems. | ||
|
||
- URL Configuration: Verify that the URL configured in Chef InSpec is correct. If the URL is configured using an environment variable, check the value for environment variable `CHEF_LICENSE_SERVER` to confirm the configured URL. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would the inspec license list
command help with this? I ask because there's also the --chef-license-server
CLI option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think inspec license list
can not be used for this purpose. And yes we have this --chef-license-server
CLI option as well, but how to check the server URL value if it was set using this CLI option? I did not have any easy resolution on this. So, I only mentioned this for ENV usage.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If someone uses the env variable, is that stored in the InSpec config file?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The value is set only in env and not in inspec config. But we store this value in licenses.yaml
I think this is ready to go aside from the merge conflict. |
Signed-off-by: Nik08 <nikita.mathur@progress.com>
Signed-off-by: Nik08 <nikita.mathur@progress.com>
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com>
Signed-off-by: Clinton Wolfe <clintoncwolfe@gmail.com> Co-authored-by: Ian Maddaus <IanMadd@users.noreply.github.com>
Signed-off-by: Ian Maddaus <ian.maddaus@progress.com>
1ce248e
to
926216f
Compare
Description
Troubleshooting Page for Chef Licensing issues/errors
Related Issue
Types of changes
Checklist: