Error 400 on SERVER: Invalid parameter dns_realm on Class[Foreman_proxy]

Sankara · December 6, 2016, 7:42pm

Hi

I am trying to install and configure foreman-proxy 1.12 (in one of the
node, say compile master) using the module available at
https://forge.puppet.com/theforeman/foreman_proxy/3.0.1/compatibility

While running “puppet agent -t” (to install and configure foreman-proxy) ,
I am getting the below error on my node. Can you please help me to find
what could be the issue?

Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Invalid parameter dns_realm on Class[Foreman_proxy] at
/dev/modules/fmanproxy/manifests/config.pp:128 on node poc-agent.local
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

config.pp:128 ===> The line#128 in config.pp file is a close curly brace of
the class “class { '::foreman_proxy':”

Further details

I have separate machine for CA, CM, Foreman

I have the below to achieve this

I have my own module called fmanproxy which will invoke the external
module.

Why do I have my own module?
To customise/set the variables and values which I want to pass to
external module

What I have in my module? Or how I am calling external module classes?

the init.pp file in my module fmanproxy, I have the below
    class fmanproxy (
        &lt;ALL my Variables&gt;
        $dns_realm                  = $fmanproxy::params::dns_realm,
        .
        .
        .

    } inherits ::fmanproxy::params {

      # validate parameters here

      class { &#39;::fmanproxy::install&#39;: } -&gt;
      class { &#39;::fmanproxy::config&#39;: } ~&gt;
      class { &#39;::fmanproxy::service&#39;: } -&gt;
      Class[&#39;::fmanproxy&#39;]
    }

···

=================================================

the install.pp file in my module fmanproxy, I have the below
    class fmanproxy::install {
        <Setting up my custom REPO and installing, nothing else>
    }

the config.pp file in my module fmanproxy, I have the below
    class fmanproxy::config {
      class { '::foreman_proxy':
        bind_host                    => $::fmanproxy::bind_host,
        bmc                          => $::fmanproxy::bmc,
        dns_realm                    => $::fmanproxy::dns_realm,
        .
        .
        .
        .

    
    } ## End of class ::foreman_proxy

      # Install the foreman_proxy
        include ::foreman_proxy

    } ## End of fmanproxy::config

=================================================

the service.pp file in my module fmanproxy, I have nothing
    class fmanproxy::service {
      # include ::foreman_proxy::service
    }

=================================================

the params.pp file in my module fmanproxy, I have the variables as below
    class fmanproxy::params {
        $custom_repo = true
        $dns_zone    = $::domain
        $dns_realm   = upcase($dns_zone)
        .
        .
        .
        .
    } ## End of Main class

=================================================

What I have in my Puppetfile

I have added the below line to download the module
    mod 'theforeman/foreman_proxy', '3.0.1'

I have the below lines to download my custom module
    mod "fmanproxy",
      :git => “MY_REPO_URL”,
      :ref => ‘MY_BRANCH_NAME’

Thanks

Sankara

Dominic_Cleal2 · December 7, 2016, 9:39am

> Hi
>
> I am trying to install and configure foreman-proxy 1.12 (in one of the
> node, say compile master) using the module available at
> https://forge.puppet.com/theforeman/foreman_proxy/3.0.1/compatibility
>
> While running “puppet agent -t” (to install and configure
> foreman-proxy) , I am getting the below error on my node. Can you please
> help me to find what could be the issue?
>
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Invalid parameter dns_realm on Class[Foreman_proxy] at
> /dev/modules/fmanproxy/manifests/config.pp:128 on node poc-agent.local
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run

You're supplying a parameter that isn't on the foreman_proxy class.

> the config.pp file in my module fmanproxy, I have the below
> class fmanproxy::config {
> class { '::foreman_proxy':
> bind_host => $::fmanproxy::bind_host,
> bmc => $::fmanproxy::bmc,
> dns_realm => $::fmanproxy::dns_realm,

dns_realm isn't a valid parameter on the foreman_proxy class. Check
against the list of valid parameters in the manifest:

github.com

theforeman/puppet-foreman_proxy/blob/3.0.1/manifests/init.pp

# Install, configure and run a foreman proxy
#
# === Parameters:
#
# $repo::                       This can be stable, rc, or nightly
#
# $gpgcheck::                   Turn on/off gpg check in repo files (effective only on RedHat family systems)
#                               type:boolean
#
# $custom_repo::                No need to change anything here by default
#                               if set to true, no repo will be added by this module, letting you to
#                               set it to some custom location.
#                               type:boolean
#
# $version::                    foreman package version, it's passed to ensure parameter of package resource
#                               can be set to specific version number, 'latest', 'present' etc.
#
# $ensure_packages_version::    control extra packages version, it's passed to ensure parameter of package resource
#                               can be set to 'installed', 'present', 'latest', 'absent'
#

This file has been truncated. show original

I'm unsure which you intend to set, probably either dns, realm or dns_zone.

> } ## End of class ::foreman_proxy
>
> # Install the foreman_proxy
> include ::foreman_proxy

Unnecessary - you're already including it by using class {
'::foreman_proxy': … }.

···

On 06/12/16 19:42, Sankara wrote:

–
Dominic Cleal
dominic@cleal.org

Sankara · December 8, 2016, 9:33pm

Thanks Dominic, the issue I reported is resolved after removing the
parameters but now getting different error. I will create a new post with
my new error.

···

On Wednesday, December 7, 2016 at 1:39:46 AM UTC-8, Dominic Cleal wrote: > > On 06/12/16 19:42, Sankara wrote: > > Hi > > > > I am trying to install and configure foreman-proxy 1.12 (in one of the > > node, say compile master) using the module available at > > https://forge.puppet.com/theforeman/foreman_proxy/3.0.1/compatibility > > > > While running “puppet agent -t” (to install and configure > > foreman-proxy) , I am getting the below error on my node. Can you please > > help me to find what could be the issue? > > > > Error: Could not retrieve catalog from remote server: Error 400 on > > SERVER: Invalid parameter dns_realm on Class[Foreman_proxy] at > > /dev/modules/fmanproxy/manifests/config.pp:128 on node poc-agent.local > > Warning: Not using cache on failed catalog > > Error: Could not retrieve catalog; skipping run > > You're supplying a parameter that isn't on the foreman_proxy class. > > > the config.pp file in my module fmanproxy, I have the below > > class fmanproxy::config { > > class { '::foreman_proxy': > > bind_host => $::fmanproxy::bind_host, > > bmc => $::fmanproxy::bmc, > > dns_realm => $::fmanproxy::dns_realm, > > dns_realm isn't a valid parameter on the foreman_proxy class. Check > against the list of valid parameters in the manifest: > > > https://github.com/theforeman/puppet-foreman_proxy/blob/3.0.1/manifests/init.pp > > I'm unsure which you intend to set, probably either dns, realm or > dns_zone. > > > > } ## End of class ::foreman_proxy > > > > # Install the foreman_proxy > > include ::foreman_proxy > > Unnecessary - you're already including it by using class { > '::foreman_proxy': .. }. > > -- > Dominic Cleal > dom...@cleal.org >