Actions
Bug #12989
closedOMAPI key data passed to foreman-installer does not end up in dhcp.yml
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
-
Description
Hello there!
It appears that OMAPI key/secret options passed to foreman-installer are being ignored:
[root@spc01 ~]# foreman-installer --foreman-proxy-dhcp=true --foreman-proxy-dhcp-config=/dhcp/conf/dhcpd.conf --foreman-proxy-dhcp-leases=/dhcp/conf/dhcpd.leases --foreman-proxy-dhcp-key-name=omapi-key --foreman-proxy-dhcp-key-secret=$OMAPI_SECRET --foreman-proxy-dhcp-server=dhcp.domain.com --foreman-proxy-dhcp-omapi-port=9999 Installing Done [100%] [..............................................] Success! * Foreman is running at https://spc01.domain.com Initial credentials are admin / changeme * Foreman Proxy is running at https://spc01.domain.com:8443 * Puppetmaster is running at port 8140 The full log is at /var/log/foreman-installer/foreman-installer.log [root@spc01 ~]#
However, other options are just fine. Here's the resulting file:
[root@spc01 ~]# cat /etc/foreman-proxy/settings.d/dhcp.yml --- # Enable DHCP management :enabled: https # valid vendors: # - isc # - native_ms (Microsoft native implementation) # - virsh (simple implementation for libvirt) :dhcp_vendor: isc :dhcp_server: dhcp.domain.com :dhcp_config: /dhcp/conf/dhcpd.conf :dhcp_leases: /dhcp/conf/dhcpd.leases #:dhcp_key_name: secret_key_name #:dhcp_key_secret: secret_key :dhcp_omapi_port: 9999 [root@spc01 ~]#
Actions