Package name isn't always drbd8-utils
http://elrepo.org/tiki/drbd84-utils

I can see that this module have a 0.2 release, but the last at puppetforge is a 4 year old 0.1 - shouldn't this module be upgraded on puppetforge?

Hi,

I'm currently using puppet with concat module version v4.1.1 (github master) and I'm getting this notice in puppet master:

Warning: Module 'puppetlabs-concat' (v4.1.1) fails to meet some dependencies:
'puppet-drbd' (v0.5.1-rc0) requires 'puppetlabs-concat' (>= 1.2.5 < 3.0.0)

If I use concat version 2.2.1 (latest version < 3.0.0) I get a lot of dependencies errors from other modules. I think you could increase required concat module version to a more recent one. I suppose you have tests to check it's ok, but on my side, no problem with concat v4.1.1.

Cheers !
Kyoshiro

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: 4.8.2-5~bpo8+1
• Ruby: 2.1.5+deb8u2
• Distribution: Debian Jessie (backports)
• Module version: 0.5.1-rc0 (guthub master)

this module once listed debian 7 in the metadata.json. We removed it because it's EOL. We need to check if recent debian versions work and add them back.

• enable issues
• allow access to @voxpupuli/collaborators
• normalise repository name
• fix links in README
• fix links in metadata.json
• enable in travis
• add to modulesync_config/modules
• add to plumbing/travis_secrets
• add .sync.yml
• modulesync
• release under new namespace!
• make master branch protected
• Require status checks to pass before merging
• Require branches to be up to date before merging (Include administrators)
• remove all webhooks except for travis
• remove all old teams that had access before

We should consider writing the drbd resources as types + provider

refreshonly can fail when there's some kind of hiccup in puppet. we must not rely on it (thanks @ffrank for writing this). Especially not for something as critical as drbd.

Is there any ETA for a release of version 5.3? The module has been set to 0.5.3-rc0 for almost 1.5 years. @smortex

The README states that this is tested on some Ubuntu version (but really old ones). The metadata.json does not have any entry for Ubuntu support. Which one is right and are there any plans to support Ubuntu 20.04?

Affected Puppet, Ruby, OS and module versions/distributions

• Puppet: not applicable
• Ruby: not applicable
• Distribution: Debian 10 (Buster), Fedora, Ubuntu
• Module version: v0.5.2

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

Use this module with configuration from example on a recent Debian 10 (Buster).

What are you seeing

Running the module will fail, because Debian 10 (Buster) does not have any package named drbd8-utils. Most other recent releases do not have such a package anymore either. Ubuntu used a transitional package in it's 18.04 LTS.

https://apps.fedoraproject.org/packages/s/drbd
https://packages.ubuntu.com/search?suite=all&searchon=names&keywords=drbd

What behaviour did you expect instead

The package name can be configured, but it would be much more user friendly, if the default package name would match the default of most distros.

Output log

Error: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install drbd8-utils' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package drbd8-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  drbd-utils

E: Package 'drbd8-utils' has no installation candidate
Error: /Stage[main]/Drbd/Package[drbd]/ensure: change from 'purged' to 'present' failed: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold install drbd8-utils' returned 100: Reading package lists...
Building dependency tree...
Reading state information...
Package drbd8-utils is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  drbd-utils

E: Package 'drbd8-utils' has no installation candidate

On the dependency list is concat listed. But the LVM Module is an dependency too.

I created a config from the example - and I can't find anything wrong, and yet the lvm is created an drbd service is started - but status is diskless/diskless.. it seems it's never put "up".

any hints to try and debug are welcome.. I'm still trying' to figure out, what the reason is for this.

I'm using drbd-8.4, on centos 6.

create logical volume for drbd

logical_volume { 'drbd':
ensure => present,
# grab from this existing volume
volume_group => "vg_$hostname",
size => '100G',
}

class { 'drbd': }
#needs firewall opening
firewall { "001 allow drbd": proto => "tcp", port => 7788, action => "accept", source => $fqdn ? { 'jaina.example.dk' => '192.168.99.2', 'jacen.example.dk' => '192.168.99.1', default => '127.0.0.1' } }

drbd::resource { 'drbd':
host1 => 'jaina.example.dk',
host2 => 'jacen.example.dk',
ip1 => '192.168.99.1',
ip2 => '192.168.99.2',
disk => "/dev/mapper/vg_$hostname-drbd",
port => '7788',
device => '/dev/drbd0',
manage => true,
verify_alg => 'sha1',
ha_primary => $fqdn ? { 'jaina.example.dk' => true, default => false},
initial_setup => $fqdn ? { 'jaina.example.dk' => true, default => false},
require => Logical_volume['drbd']
}
}

In the current documentation the value "initial_setup" is set to true. But there is no information, that this value should set be to "false" after the first initialize.

Every times the DRBD volume will be formated again with "initial_setup = true"

Are there any plans to test this on puppet 7 and change the metadata.json to support puppet 7?