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 init scripts with product support #155

Closed
johnlawerance opened this issue Jul 7, 2017 · 0 comments
Closed

Fix init scripts with product support #155

johnlawerance opened this issue Jul 7, 2017 · 0 comments

Comments

@johnlawerance
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: All supported versions
  • Ruby: All supported versions
  • Distribution: All supported distros
  • Module version: 2.0.0

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

Change product from stash to bitbucket:
stash::product: 'bitbucket'

What are you seeing

When the init script runs it attempts to execute start-stash.sh which is named start-bitbucket.sh on bitbucket server.

What behaviour did you expect instead

It should pull in the variable from the module settings.

Output log

Error: /Stage[main]/Stash::Service/Service[stash]/ensure: change from stopped to running failed: Could not start Service[stash]: Execution of '/sbin/service stash start' returned 127: Starting stash: /etc/init.d/stash: line 55: /opt/grubhub/services/stash_installdir/atlassian-bitbucket-4.14.6/bin/start-stash.sh: No such file or directory

Any additional information you'd like to impart

Incoming fix for this.

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

No branches or pull requests

1 participant