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

Linux install script broken and hap-sup loaders not looking for correct init type for kernel2 systems(sysvinit vs upstart) #201

Closed
sam1el opened this issue Feb 10, 2020 · 2 comments

Comments

@sam1el
Copy link
Collaborator

sam1el commented Feb 10, 2020

Cookbook version

Habitat version 1.5.1

Chef-client version

15.1.36

Platform Details

Centos 6 sysvinit (can be either)
Redhat 6 upstart (can be either)
Ubuntu 11.04 sysvinit (can be either)

Scenario:

Installing habitat supervisor as a service and wait for service start up to load packages.

Steps to Reproduce:

creates simple recipe to load hab-sup as a service and install a package or load a service from builder.

hab_sup 'Test-run' do
  license 'accept'
end

hab_package 'core/git'

Expected Result:

habitat is installed, installs hab-sup as a service for the correct init type the system requires, installs the package

Actual Result:

The install resource does not install the correct version of hab because it is not passing the kernel2 flag to the shell script. Due to this, it is unable to pull install hab-sup or install the correct packages

@welcomebot
Copy link

Hey There
It looks like this is the first issue you've filed against the chef-cookbooks project. I'm here to offer you a bit of extra help to make sure we can quickly get back to you.
Make sure you've filled out all the fields in our issue template. Make sure you've provided us with the version of chef-client you're running, your operating system and the version of the cookbook. If you're not using the most up to date version of the cookbook then please make sure to update first. Lots of things change between versions even if you're issue isn't listed in the changelog. Finally please give us a detailed description of the issue you're having. The more we know about what you're trying to do, what actually happens, and how you can reproduce the problem, the better.

If you're looking for more immediate troubleshooting help make sure to check out #general on the Chef Community Slack. There's plenty of folks there willing to lend a helping hand. Thanks for the first issue. We hope we can get back to you soon with a solution.

@sam1el
Copy link
Collaborator Author

sam1el commented Feb 11, 2020

PR to follow shortly

@sam1el sam1el mentioned this issue Feb 21, 2020
4 tasks
@tas50 tas50 closed this as completed Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants