Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-31316

satellite-installer fails when foreman-proxy-dhcp is enabled

XMLWordPrintable

    • Platform
    • 2
    • False
    • foreman-installer-3.14.0-1
    • Moderate
    • None
    • None
    • None
    • No Coverage
    • Yes

      Description of problem:

      • First satellite-installer run to enable the dhcp server works fine
      • A second satellite-installer run fails with error message "Unknown variable: 'foreman_proxy::https_port'"
         

      How reproducible:

      • Fresh install of Satellite 6.17 Snap 1
         

      Is this issue a regression from an earlier version:
      Yes, this worked before
       

      Steps to Reproduce:

      1. Configure Satellite to be the DHCP server for the network

        # satellite-installer --scenario satellite \
  --foreman-proxy-dhcp=true \
  --foreman-proxy-dhcp-gateway="192.168.6.250" \
  --foreman-proxy-dhcp-range="192.168.6.200 192.168.6.240" \
  --foreman-proxy-dhcp-nameservers="192.168.6.25" \
  --foreman-proxy-dhcp-option-domain="example.com"

      2. The DHCP server is now configured and running

      3. Run a normal satellite installer

         # satellite-installer --scenario satellite

      Actual behavior:
      The second run fails with error:

      2025-02-24 09:57:32 [ERROR ] [configure] Evaluation Error: Unknown variable: 'foreman_proxy::https_port'. (file: /usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydhcp.pp, line: 116, column: 42) on node satellite.example.com

      Expected behavior:
      Further satellite-installer runs should work fine

      Business Impact / Additional info:

      • Adoption blocker if not fixed by GA
         

              ekohlvan@redhat.com Ewoud Kohl van Wijngaarden
              rhn-support-smeyer Stefan Meyer
              Radek Mynar Radek Mynar
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: