But during an initial puppet run I end up (on the console):

symlink_realpath(/opt/dspace_src/latest) realpath() failed: No such file or directory
symlink_realpath(/opt/dspace_src/latest) realpath() failed: No such file or directory
symlink_realpath(/opt/dspace_src/latest) realpath() failed: No such file or directory
symlink_realpath(/opt/dspace_src/latest) realpath() failed: No such file or directory

And I then end up with a broken symlink during the initial run:

If I run the Puppet agent again then the Archive is extracted and everything is okay, i.e.:

So I’ve got an ordering problem here - and I’m not sure how to fix it for the initial Puppet run. Can anyone help ? I thought that by adding

require => Archive["/tmp/dspace-$dspace_version.tar.gz"],

that the Symlink should only be created after the Archive resource has finished successfully extracting the TGZ, but this doesn’t seem to be the case.

@Patrick Rynhart it's not an ordering problem. You say that after the initial run, the archive is not extracted as expected. That is your problem, not the order. Something about your code has that not being enforced on the first run.

(in other words, if you compare

extract then symlink

to

symlink then extract

, both cases end up with the archive extracted.)

@binford2k: I’ve reduced my manifest to as simple as possible to replicate the issue (and removed all substituted variables - i.e. everything is hardcoded)

class dspace_modern (
  $config = [],
) {
    file { '/opt':
      ensure => 'directory',
    }

    file { '/opt/dspace_src':
      ensure  => 'directory',
      owner   => 'tomcat',
      group   => 'tomcat',
      require => File['/opt'],
    }

    archive { '/tmp/dspace-7.5.tar.gz':
      source       => '<https://github.com/DSpace/DSpace/archive/refs/tags/dspace-7.5.tar.gz>',
      extract      => true,
      extract_path => '/opt/dspace_src',
      cleanup      => true,
      user         => 'tomcat',
      group        => 'tomcat',
      require      => File['/opt/dspace_src'],
    }

    file { '/opt/dspace_src/latest':
      ensure  => 'link',
      target  => '/opt/dspace_src/DSpace-dspace-7.5',   # When dspace-7.5.tar.gz is extracted (from above), it has directory 'DSpace-dspace-7.5' inside of it
      require => Archive['/tmp/dspace-7.5.tar.gz'],
    }
}

This message was deleted.

Can you see where the mistake is ? Because I’m not able to

Hello team, Can anyone help me to troubleshoot the below issue PC Pratyay Chaphekar Work notes•2023-03-22 221527 Hi Team, [root@puppetvts40002 ~]# puppet agent -vt Info: Using configured environment 'mgmt_production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Error: Facter: error while processing "/opt/puppetlabs/puppet/cache/facts.d/fg_parser.py" for external facts: child process returned non-zero exit status (1). Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Function Call, has_key(): expects the first argument to be a hash, got "" which is of type String (file: /etc/puppetlabs/code/environments/mgmt_production/main/roles/s_puppetvts4/manifests/vcamp/layers/firewall_rules_base.pp, line: 23, column: 10) (file: /etc/puppetlabs/code/environments/mgmt_production/main/roles/s_puppetvts4/manifests/vcamp/network.pp, line: 227) on node puppetvts40002.irv4.vtscloud.io Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run [root@puppetvts40002 ~]# w

same setup is working for other server but here its failing

This message was deleted.

This message was deleted.

This message was deleted.

See the

puppetlabs-mysql

module at https://forge.puppet.com/puppetlabs/mysql?src=slack&channel=puppet

Hello, everyone. I have a question about puppetboard (potentially bug), NOT puppet/puppetboard code. Should I ask #C0W1Y5VL0 or here? thank you.

See the

puppet-puppetboard

module at https://forge.puppet.com/puppet/puppetboard?src=slack&channel=puppet

probably #C0W1Y5VL0

Okay, thank you.

This message was deleted.

Can someone help me get this unstuck?

This message was deleted.

So confirmation mails contain two attachments, one

text/plain, 7bit, us-ascii

and one

text/html, quoted, us-ascii

. Mail user agents displaying html mails will likely render

&

as

&

and clicking or copying the link may work, but I'm reading the plain text part and thus of course copied the link verbatim, which is how I end up in a broken registration process.

Perhaps those generated mails should use a literal

&

instead of the URL encoded version in the plain text part? I'd be surprised if I was the first user running into this.

but i'm also suprised to land in the resend form as the error case, rather than getting a proper error message saying that the link doesn't work. unless you have know your way around URL encoding, that's hard to debug and looks like a systematic error that's too stupid to be true (yet you need to find a support/contact/slack to report and help yourself, as none of the steps in the signup/login process have a link or button to "need help?" or "something not working?" or so)

This message was deleted.

Hello, does anyone know of a nice off-the-shelf fact that pulls all Linux services systemd and sysV ?

Should be pretty quick to make one just thought there was on already out there.

Not a fact, per se.

puppet resource service

will return all services, but it isn't a defined, default fact.

Thats exactly what i'm looking to get as a fact so i can send it to splunk for reporting.