Skip to content

bareos Resource file conventions changed with version 22 #133

@jdreffein

Description

@jdreffein

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: *
  • Ruby: *
  • Distribution: *
  • Module version: *

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

upgrade packages for bareos from 21 to 22 (no matter how).

What are you seeing

client does not start anymore.
package deploys bareos-fd.d/client/myself.conf instead of former bareos-fd.d/client/bareos-fd.conf (which is still used and created by module). From then there are two config files while there must only be one.

What behaviour did you expect instead

switch to new naming convention for bareos version 22 (also see pull request #129 by https://github.com/aba-rechsteiner which hasn't included this yet)

Output log

bareos-df: Fatal Error at filed/filed.cc:322 because:
bareos-fd: Only on Client resource permitted in /etc/bareos/bareos-fd.d//.conf

Any additional information you'd like to impart

https://docs.bareos.org/Configuration/CustomizingTheConfiguration.html#resource-file-conventions

Resource file conventions
Each configuration resource has to use its own configuration file.

The path of a resource file is COMPONENT.d/RESOURCETYPE/RESOURCENAME.conf.

The name of the configuration file is identical with the resource name:

e.g.

bareos-dir.d/director/bareos-dir.conf

bareos-dir.d/pool/Full.conf

Exceptions:

The resource file bareos-fd.d/client/myself.conf always has the file name myself.conf, while the name is normally set to the hostname of the system.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions