https://www.puppet.com/community logo
Join Slack
Powered by
# puppet
  • c
  • c
    ?
  • c
    Know that I’m just orienting myself to your configuration
  • s
    This message was deleted.
    y
    c
    • 3
    • 4
  • c
  • c
    @dmnfortytwo
  • d
    As for requirements: some packages were missing (libgtk2.0-0 libjpeg62 libossp-uuid16 libxslt1.1), installing didn't help.
  • d
    No, /tmp isn't mounted with noexec, I also tried another newly created directory.
  • s
    This message was deleted.
    d
    • 2
    • 1
  • v
    looking into puppet code, you either don't have syslog ruby library or don't have user with '0' uid for what it worth, I run aarch agents just fine
    Copy code
    # facter os
{
  architecture => "aarch64",
  family => "RedHat",
  hardware => "aarch64",
  name => "Amazon",
  release => {
    full => "2",
    major => "2"
  },
  selinux => {
    enabled => false
  }
}
  • d
    I have user with zero uid (root as usual). As for ruby lib - shouldn't it be packaged into puppetserver? I've just tried to install ruby-syslog-logger and it didn't help. BTW, facter and puppet work fine, only puppetserver fails.
  • y
    Puppet server only runs on x86_64
  • a
    I’m at a loss. Have tried so many things to figure out why this dependency cycle exists. I cannot find anything in my Puppet code / Hiera data that would result in Puppet adding an autorequire as shown in the cycles chart. If I move the user creation for bar into the base profile and then create both users from the same profile, it works. The two accounts are in no way connected to each other. Ideas?
  • s
    This message was deleted.
    a
    d
    +2
    • 5
    • 30
  • b
    those are a lot of arrows
  • d
    @Yorokobi then why does official package has 'all' architecture?
  • y
    You'll have to ask the .deb packaging folks that one.
  • s
    This message was deleted.
    y
    • 2
    • 2
  • s
    This message was deleted.
    y
    d
    • 3
    • 4
  • y
    https://puppet.com/docs/pe/2021.6/supported_operating_systems.html#supported_operating_systems_and_devices-supported-primary-server-platforms Just under the heading it states
    All primary server platforms require an x86-64 architecture.
  • d
    For help with non-supported operating systems, architectures, or JRE versions, join our Community Slack.
    😀
  • b
    https://tickets.puppetlabs.com/browse/SERVER-2539 during the last core office-hours we collected some ideas for speeding up pluginsync (which is a requirement for syncing custom datatypes which is a requirement for using them in deferred functions). I collected the different ideas we had. If you've some thoughts please comment.
  • b
    I have a few class modules that have dependencies on users being created before the class module running, I know that I can do: User['my_user'] -> Class['my_class'] but is there a way to specify all user resources be created ie: User[*] -> Class['my_class'] ?? Users are going to come and go and the class module writes files to the users' home directories, ssh_keys, etc so the class module needs to ensure that all users are created.
  • d
    User <| |> -> Class['my_class']
  • v
    There are collectors, but I would stay away from them this
  • v
    They will realize all virtual users if you have any
  • d
    Collectors are awesome if you keep them in mind 🙂
  • b
    Thanks. I am using collectors already but I'm not very familiar with how they really work. I'll give your suggestion a try.
  • v
    Presumably users are created by 
    class { 'corp::profile::users':
    , you can set relationship with this class
  • b
    I'm creating users with create_resources(user, lookup('users'),,{})
1...353637...428Latest