puppet-gitlab icon indicating copy to clipboard operation
puppet-gitlab copied to clipboard

/Stage[main]/Gitlab::Install/Package[gitlab-omnibus]/ensure: created\nError: Could not enable gitlab-runsvdir:

Open GrabAByte opened this issue 6 years ago • 4 comments

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 4.10
  • Ruby:
  • Distribution: RedHat 7.2
  • Module version: 3.0.2

How to reproduce (e.g Puppet code you use)

Run puppet on fresh install of Gitlab using this module

What are you seeing

gitlab appears to attempt to enable the gitlab-runsvdir service before it is ready.

What behaviour did you expect instead

the runsvdir service is enabled and the puppet run is successful

Output log

11:36:20 [Deploy - RedHat (Default)] "Notice: /Stage[main]/Gitlab::Install/Package[gitlab-omnibus]/ensure: created", 11:36:20 [Deploy - RedHat (Default)] "Error: Could not enable gitlab-runsvdir: ", 11:36:20 [Deploy - RedHat (Default)] "Error: /Stage[main]/Gitlab::Service/Service[gitlab-runsvdir]/enable: change from false to true failed: Could not enable gitlab-runsvdir: ", 11:36:20 [Deploy - RedHat (Default)] "Notice: /Stage[main]/Gitlab::Service/Exec[gitlab_reconfigure]: Dependency Service[gitlab-runsvdir] has failures: true",

Any additional information you'd like to impart

GrabAByte avatar Mar 04 '19 13:03 GrabAByte

What happens if you run the agent again right after this failure? I have a hunch I'd like to confirm...

LongLiveCHIEF avatar Mar 04 '19 20:03 LongLiveCHIEF

The problem I have is this integrated into our Jenkins Build pipeline - the puppet run itself is controlled via an ansible task, the puppet code is packaged into a deployable artefact (ISO), which requires a clean run it without failure. The pipeline fails if the puppet run task returns an exit 1.

If we deploy onto an existing box with gitlab installed for an upgrade it is successful. But on a fresh installation it always fails, which is always the scenario for CI Build.

GrabAByte avatar Mar 05 '19 12:03 GrabAByte

@LongLiveCHIEF if this is ran again right after it works, but this is not the solution I need..

GrabAByte avatar Mar 16 '19 20:03 GrabAByte

I know it's not the solution. I should have clarified that that's not why I was asking. The hunch I had was around what causes the issue, and how it would present itself.

LongLiveCHIEF avatar Mar 27 '19 18:03 LongLiveCHIEF