Plugins » Katello

Forgot to say, katello 3.3 stable and foreman 1.14.2

foreman-installer --scenario foreman-proxy-content \
  --foreman-proxy-content-certs-tar /root/pulpnode01.tld-certs.tar\
  --certs-update-all\
  --certs-regenerate true\
  --foreman-proxy-content-pulp-oauth-secret     ""\
  --foreman-proxy-content-parent-fqdn           "pulpmaster.tld"\
  --foreman-proxy-register-in-foreman           "true"\
  --foreman-proxy-foreman-base-url              "https://pulpmaster.tld"\
  --foreman-proxy-trusted-hosts                 "pulpmaster.tld"\
  --foreman-proxy-trusted-hosts                 "pulpnode01.tld"\
  --foreman-proxy-oauth-consumer-key            ""\
  --foreman-proxy-oauth-consumer-secret         ""\
  --foreman-proxy-puppet false\
  --foreman-proxy-content-puppet false\
  --foreman-proxy-puppetca false\
  --foreman-proxy-tftp false\
  --foreman-proxy-templates false

For Katello 3.4.3 the Error message changed a little because its now in a different line:

[ERROR 2017-07-24 16:02:55 main]  Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Error while evaluating a Resource Statement, Duplicate declaration: File[/etc/foreman-proxy/ssl_key.pem] is already declared in file /usr/share/foreman-installer/modules/foreman_proxy/manifests/config.pp:145; cannot redeclare at /usr/share/katello-installer-base/modules/certs/manifests/keypair.pp:23 at /usr/share/katello-installer-base/modules/certs/manifests/keypair.pp:23:5  at /usr/share/katello-installer-base/modules/certs/manifests/foreman_proxy.pp:84 on node pulpnode.srv.muenchen.de

So to explain this problem a little further, selecting not to install a puppetca/puppet proxy causes this if statement: https://github.com/theforeman/puppet-foreman_proxy/blob/beb803df7245c0203a6fc11f25aab47af7870f4b/manifests/config.pp#L116

to run into the else part of the if where the sslkeys are File resources. These resources are already declared in https://github.com/Katello/puppet-certs/blob/master/manifests/foreman_proxy.pp#L84-L91

so question is where should they be declared - does foreman_proxy need a switch to disable the management?

I posted under https://projects.theforeman.org/issues/22443

However, my struggles appear to be the same... no workaround... huh.

@eric sorenson Hansen: if I recall right you can just comment out one of the resources that's duplicate - but in general this is a design issue because you're not meant to run a proxy without puppet

So it looks like you should pass in foreman_proxy::manage_puppet_group => false when you disable puppet. With the installer it should be exposed as --foreman-proxy-manage-puppet-group false. Can you verify this solves it for you? If it does we should do this in hiera by default I think.