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

Fix ldap for dev vm. #3309

Merged
merged 1 commit into from May 12, 2022
Merged

Fix ldap for dev vm. #3309

merged 1 commit into from May 12, 2022

Conversation

lbakerchef
Copy link
Contributor

@lbakerchef lbakerchef commented May 11, 2022

SUMMARY:

The ldap config for the dev vm was not working. This is a quick fix
until a deeper dive can be arranged.

NOTE:

Note that in addition to this change, you must currently make the following change in dev/defaults.yml to enable ldap (it is unknown why the change is not being picked up in config.yml):

   ldap:
-    start: false
+    start: true

THE ERROR:

Several errors were encountered, depending on whatever permute of config
settings were tried. Here are a few:

$ vagrant status
Current machine states:

ldap                      not created (virtualbox)
chef-server               running (virtualbox)
==> ldap: Running provisioner: chef_zero...
    ldap: Installing Chef (latest)...
Vagrant could not detect Chef on the guest! Even after Vagrant
attempted to install Chef, it could still not find Chef on the system.
Please make sure you are connected to the Internet and can access
Chef's package distribution servers. If you already have Chef
installed on this guest, you can disable the automatic Chef detection
by setting the 'install' option in the Chef configuration section of
your Vagrantfile:

    chef.install = false

Signed-off-by: Lincoln Baker lbaker@chef.io

Description

[Please describe what this change achieves]

Issues Resolved

[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]

Check List

@lbakerchef lbakerchef requested review from a team as code owners May 11, 2022 21:07
@lbakerchef lbakerchef self-assigned this May 11, 2022
@netlify
Copy link

netlify bot commented May 11, 2022

👷 Deploy Preview for chef-server processing.

Name Link
🔨 Latest commit fa23662
🔍 Latest deploy log https://app.netlify.com/sites/chef-server/deploys/627c30afc6fc94000941cd0e

The ldap config for the dev vm was not working.  This is a quick fix
until a deeper dive can be arranged.

NOTE:

In addition to this change, you must currently make the
following change in dev/defaults.yml to enable ldap (it is unknown
why the change is not being picked up in config,yml):

   ldap:
-    start: false
+    start: true

ERRORS:

Several errors were encountered, depending on whatever permute of config
settings were tried.  Here are a few:

$ vagrant status
Current machine states:

ldap                      not created (virtualbox)
chef-server               running (virtualbox)

==> ldap: Running provisioner: chef_zero...
    ldap: Installing Chef (latest)...
Vagrant could not detect Chef on the guest! Even after Vagrant
attempted to install Chef, it could still not find Chef on the system.
Please make sure you are connected to the Internet and can access
Chef's package distribution servers. If you already have Chef
installed on this guest, you can disable the automatic Chef detection
by setting the 'install' option in the Chef configuration section of
your Vagrantfile:

    chef.install = false

Signed-off-by: Lincoln Baker <lbaker@chef.io>
@sonarcloud
Copy link

sonarcloud bot commented May 11, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@jashaik jashaik merged commit 2837ba2 into main May 12, 2022
@jashaik jashaik deleted the lbaker/fix-dev-vm-ldap branch May 12, 2022 09:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants