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

Add support for Debian 9, drop debian 8 #139

Merged
merged 5 commits into from
Mar 28, 2018

Conversation

bastelfreak
Copy link
Member

No description provided.

@bastelfreak bastelfreak added the enhancement New feature or request label Sep 30, 2017
.travis.yml Outdated
sudo: required
- rvm: 2.4.2
bundler_args: --without development
env: PUPPET_VERSION="~> 5.0" CHECK=acceptance BEAKER_set="docker/debian-9" bundle exec rake acceptance
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

beaker-puppet_install_helper uses a different syntax. How this even worked in the past is a mystery to me but if you read https://github.com/puppetlabs/beaker-puppet_install_helper#run_puppet_install_helper then it suggests you need explicit version numbers.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

to clarify: This never worked and was a copy and paste issue

@ekohl
Copy link
Member

ekohl commented Oct 4, 2017

I honestly think setting Puppet versions is pretty broken with the acceptance tests. I'd much rather set the repo collection to pc1 or puppet5. For not just leave it out and use the default so we at least test something on debian 5?

@bastelfreak
Copy link
Member Author

Current state: In general everything is working. Also this PR fixes #140. Debian 8 seems to be a bit strange. After the package installation the daemon is started, but not via unit file (which is also missing in 3.8, but that is EOL anyway)? So puppet tries to start the daemon, bind to the tcp socket fails because it is already running -> everything is broken. Personally I would drop Debian 8 support. It is legacy, Debian 9 is working. Objections?

@bastelfreak
Copy link
Member Author

Also the unit files are really really bad. They still rely on the legacy sysv scripts. The mentionted issues result in the usage of official glusterfs repos on Debian 8. Maybe it works if we use the debian-own packages for glusterfs, on debian 8 only. But implementing that would be really really painful and adds a lot of additional logic to the modul. Also the shipped glusterfs version in Debian 8 is, of course, EOL.

@ekohl
Copy link
Member

ekohl commented Oct 25, 2017

👍 to dropping Debian Jessie.

bastelfreak added a commit to bastelfreak/puppet-gluster that referenced this pull request Oct 25, 2017
the packages for debian 8 are broken. Details are in
voxpupuli#139. Also it is EOL and
we support Debian 9.
@ekohl
Copy link
Member

ekohl commented Oct 30, 2017

Given #138 (comment) I think we should just update to the newest repo version instead of dropping Jessie since Debian still supports it.

@ekohl
Copy link
Member

ekohl commented Mar 26, 2018

This need a rebase now. Could you also add the nodesets to .sync.yml?

@bastelfreak bastelfreak changed the title Add acceptance tests on Debian 9 + run on latest ruby/puppet Add support for Debian 9, drop debian 8 Mar 28, 2018
@bastelfreak
Copy link
Member Author

I also dropped debian 8 from the metadata.json. We already dropped official support for it and purged it from the travis acceptance test matrix. We just forgot the entry in the metadata.json

@llowder llowder merged commit 9e39af1 into voxpupuli:master Mar 28, 2018
@bastelfreak bastelfreak deleted the debian9 branch March 28, 2018 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants