Setting up Code Manager and running in to problem with r10k_api_user needing key and web hook failing test pushes

[evan....@noaa.gov]

As the title says this is dealing with Code Manager. First I followed the directions in the gitlab module to setup gitlab, and that much worked up to testing code pushes. At this point it was apparent the the r10k_api_user had a problem do to no ssh key, and that the web hook trigger is not working. I am not sure where how to go about debugging this as the only error I have found is the un helpful:

500

Whoops, something went wrong on our end.

---

Try refreshing the page, or going back and attempting the action again.

Please contact your GitLab administrator if this problem persists.

This looks like something is configured wrong on the gitlab side by I need help in hunting it down.

Evan

[evan....@noaa.gov]

Discovered the solution. Turns out port 8170 was closed on the Puppet server firewall. The logs were not very helpful in finding this, and the error had me looking in the wrong place to begin with as it was on the Master and not the GitLab server despite the error.

[Lindsey Smith]

On Mon, Mar 7, 2016 at 1:41 PM, <evan....@noaa.gov> wrote:

Discovered the solution. Turns out port 8170 was closed on the Puppet server firewall. The logs were not very helpful in finding this, and the error had me looking in the wrong place to begin with as it was on the Master and not the GitLab server despite the error.

Thanks for the update and I'm glad you were able to get it working. If I understand correctly, the GitLab webhook was firing as expected after a commit but didn't do anything because it was firewalled off from the Code Manager API endpoint on the master?

 

On Friday, March 4, 2016 at 4:23:58 PM UTC-6, evan....@noaa.gov wrote:

As the title says this is dealing with Code Manager. First I followed the directions in the gitlab module to setup gitlab, and that much worked up to testing code pushes. At this point it was apparent the the r10k_api_user had a problem do to no ssh key, and that the web hook trigger is not working. I am not sure where how to go about debugging this as the only error I have found is the un helpful:

500

Whoops, something went wrong on our end.

---

Try refreshing the page, or going back and attempting the action again.

Please contact your GitLab administrator if this problem persists.

This looks like something is configured wrong on the gitlab side by I need help in hunting it down.

Evan

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/3644378e-59ee-4f00-99c2-6b48a7aea26d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.