markt-de / puppet-ds_389 Goto Github PK

• Test module with version 2.4.3
• Add unit tests for 2.4.x
• Add acceptance tests for 2.4.x (if packages are available)

Hi

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: 
Error while evaluating a Resource Statement, Evaluation Error: 
Resource type not found: Ssl_pkey (file: /etc/puppetlabs/code/environments/production/modules/ds_389/manifests/instance.pp, line: 283, column: 22) (file: /etc/puppetlabs/code/environments/production/site/role/manifests/ybcentos8.pp, line: 72) 

# Create nss db.
-> exec { "Create cert DB: ${server_id}":
  command     => "certutil -N -d ${instance_path} -f ${temp_pass_file}",
  path        => $ds_389::path,
  refreshonly => true,
  notify      => Ssl_pkey["Generate CA private key: ${server_id}"],
}

# Generate the private key for the CA.
-> ssl_pkey { "Generate CA private key: ${server_id}":
  ensure => 'present',
  name   => $ca_key,
  size   => 4096,
}

Think there is a case issue ?

Hello, I'm hoping you can help and show me what I'm doing wrong. I tried configuring a replication consumer but I didn't get the expected results.

CentOS Linux release 8.3.2011
Puppet 6.19.0
puppet-ds_389 2.5.0

I configured my instance as follows:

  class { 'ds_389':
    dnf_module_name    => '389-directory-server',
    dnf_module_version => 'stable/default',
  }

  ds_389::instance { 'directory':
    backup_enable => true,
    root_dn       => 'cn=Directory Manager',
    root_dn_pass  => lookup(root_dn_pass),
    suffix        => 'dc=server,dc=com',
    cert_db_pass  => lookup(cert_db_pass),
    server_id     => $facts['networking']['hostname'],
    replication   => {
      'replication_pass' => lookup(replication_dn_pass),
      'role'             => 'consumer',
    },
  }

I opened the cockpit UI and clicked on "389 Directory Server", then clicked on "Replication". The web UI said there was no replication agreement for the suffix.

I expected there to be a replication agreement configured.

Since 389-ds-base 2.1.0, The 389 ldap directory server supports two kind of underlying database:

• Berkeley Database (BerkeleyDB)
• Lightning Memory-Mapped Database Manager (LMDB)

Starting from version 3.0.0 New instances are no longer created with BerkeleyDB by default but with LMDB.

See FAQ about BerkeleyDB backend deprecation and using LMDB backend.

For 389-ds-base >= 2.1.0 and < 3.0.0 the resource ds_389::instance should provide an option for selecting the database engine. For this in creation of the template file for the instance in section [slapd] there should be a key/value pair with the key 'db_lib' and a value of either 'bdb' (BerkeleyDB) or 'mdb' (LMDB). The default value should be 'mdb'.