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

on VMWare, UUID is created in framework.properties that is overwritten by rundeck #451

Closed
Micsi opened this issue Aug 24, 2020 · 0 comments · Fixed by #520
Closed

on VMWare, UUID is created in framework.properties that is overwritten by rundeck #451

Micsi opened this issue Aug 24, 2020 · 0 comments · Fixed by #520

Comments

@Micsi
Copy link

Micsi commented Aug 24, 2020

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: 6.17.0
  • Ruby:
  • Distribution: Debian 10
  • Module version: 5.4.0

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

on a VMWare VM...

  class { 'rundeck':
    key_storage_type      => 'db',
    projects_storage_type => 'db',
    database_config       => {
      'type'            => 'mysql',
      'url'             => 'jdbc:mysql://localhost/rundeck?autoReconnect=true&serverTimezone=Europe/Berlin',
      'username'        => $dbusr,
      'password'        => $dbpw,
      'driverClassName' => 'com.mysql.cj.jdbc.Driver',
    },
    auth_config           => $auth_config,
    ssl_enabled           => false,
    grails_server_url     => "https://$rundeck_url",
    sshkey_manage         => true,
  }

From time to time, rundeck adds a new line to framework.properties with a different UUID along with comments that the Server UUID was autocreated by Rundeck.
On the next Puppet run, the original file is recreated, triggering a service restart.

Unfortunately, I cannot tell what exactly triggers the write of the config file in rundeck. I restarted rundeck, logged in and looked at the config, but the framework.properties is unchanged.
But I see the below changes happening and saw a file as described after a --noop run that would have recreated framework.properties.

What are you seeing

On a VMWare VM /etc/frameworks.properties is generated with a line

rundeck.server.uuid = VMware-42 19 5f 0b fd 14 94 b1-28 ## ## ## ## ## ## ##

which is the result of the fact 'serialnumber' on that host, used in rundeck::params:

$rdeck_uuid = $facts['serialnumber'] ? {
    '0'     => fqdn_uuid($::fqdn),
    undef   => fqdn_uuid($::fqdn),
    default => $facts['serialnumber'],
  }

What behaviour did you expect instead

A framework.properties should be created, that will not be changed by rundeck

Output log

Notice: /Stage[main]/Rundeck::Config::Global::Framework/File[/etc/rundeck/framework.properties]/content: content changed '{md5}c28d469bfcec60ae4bc928c1bb9af33c' to '{md5}a4744c761e153f1637193272ec540e92'
Notice: /Stage[main]/Rundeck::Service/Service[rundeckd]: Triggered 'refresh' from 1 event

Any additional information you'd like to impart

Why can't we use fqdn_uuid($::fqdn) as default? I think this should always return a valid UUID?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant