GitLab/Chef Server Conflict?

How to Use GitLab
1

Hello. I have installed GitLab Community Edition 11.3.5 (c74e8d940d3) on a DigitalOcean droplet. Everything was working fine, but then I went to install the latest version of standalone Chef Server and it looks like there is a conflict.

WhenI executed the Chef Server command line utility to create an admin user for the standalone Chef Server installation, I got this error:

root@ops:/opt/opscode/embedded/service# chef-server-ctl user-create schism Schism Lc lc@egfrazier.com 'linlab1254pl!' --filename ~/schism.pem
ERROR: Unprocessable Entity
Response: <!DOCTYPE html>
<html>
<head>
  ...Some HTML and CSS Code
<body>
  <a href="/">
    <img src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMjEwIiBoZWlnaHQ9IjIxMCIgdmlld0JveD0iMCAwIDIxMCAyMTAiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy8yMDAwL3N2ZyI+CiAgPHBhdGggZD0iTTEwNS4wNjE0IDIwMy42NTVsMzguNjQtMTE4LjkyMWgtNzcuMjhsMzguNjQgMTE4LjkyMXoiIGZpbGw9IiNlMjQzMjkiLz4KICA8cGF0aCBkPSJNMTA1LjA2MTQgMjAzLjY1NDhsLTM4LjY0LTExOC45MjFoLTU0LjE1M2w5Mi43OTMgMTE4LjkyMXoiIGZpbGw9IiNmYzZkMjYiLz4KICA8cGF0aCBkPSJNMTIuMjY4NSA4NC43MzQxbC0xMS43NDIgMzYuMTM5Yy0xLjA3MSAzLjI5Ni4xMDIgNi45MDcgMi45MDYgOC45NDRsMTAxLjYyOSA3My44MzgtOTIuNzkzLTExOC45MjF6IiBmaWxsPSIjZmNhMzI2Ii8+CiAgPHBhdGggZD0iTTEyLjI2ODUgODQuNzM0Mmg1NC4xNTNsLTIzLjI3My03MS42MjVjLTEuMTk3LTMuNjg2LTYuNDExLTMuNjg1LTcuNjA4IDBsLTIzLjI3MiA3MS42MjV6IiBmaWxsPSIjZTI0MzI5Ii8+CiAgPHBhdGggZD0iTTEwNS4wNjE0IDIwMy42NTQ4bDM4LjY0LTExOC45MjFoNTQuMTUzbC05Mi43OTMgMTE4LjkyMXoiIGZpbGw9IiNmYzZkMjYiLz4KICA8cGF0aCBkPSJNMTk3Ljg1NDQgODQuNzM0MWwxMS43NDIgMzYuMTM5YzEuMDcxIDMuMjk2LS4xMDIgNi45MDctMi45MDYgOC45NDRsLTEwMS42MjkgNzMuODM4IDkyLjc5My0xMTguOTIxeiIgZmlsbD0iI2ZjYTMyNiIvPgogIDxwYXRoIGQ9Ik0xOTcuODU0NCA4NC43MzQyaC01NC4xNTNsMjMuMjczLTcxLjYyNWMxLjE5Ny0zLjY4NiA2LjQxMS0zLjY4NSA3LjYwOCAwbDIzLjI3MiA3MS42MjV6IiBmaWxsPSIjZTI0MzI5Ii8+Cjwvc3ZnPgo="
       alt="GitLab Logo" />
  </a>
  <h1>
    422
  </h1>
  <div class="container">
    <h3>The change you requested was rejected.</h3>
    <hr />
    <p>Make sure you have access to the thing you tried to change.</p>
    <p>Please contact your GitLab administrator if you think this is a mistake.</p>
    <a href="javascript:history.back()" class="js-go-back go-back">Go back</a>
  </div>
  <script>
    (function () {
      var goBack = document.querySelector('.js-go-back');

      if (history.length > 1) {
        goBack.style.display = 'inline';
      }
    })();

  </script>
</body>
</html>

Even though the command is meant to create an admin user on Chef standalone server, I am getting an error from GitLab.

I remember that chef-client ran when I installed GitLab and Iguess an instance of Chef Server was installed with GitLab as well. However, after installing GitLab and prior to installing standalone Chef Server, I used Chef’s usual utilities to try to detect if Chef Server was installed and did not find it.

My questions are:

  • What would be best practice in this scenario (running GitLab and standalone Chef Server on the same host) that will allow me to work directly with my Chef Server. Where is the GitLab installed Chef located?
  • Is there a way to install GitLab without including Chef addons automatically? When I installed GitLab,chef-client ran as part of the initial configuration process. Is there a documented way to make these configurations manually, without the assistance of Chef? This would allow me to later install Chef server without any conflicts.

Thank you in advance for any insights provided.
egfraz