Problem:
getting a record exists when trying to install, this happened after changing the subnet for the provision setup of foreman.
Create DHCP Settings for centos-agent.mtl.labs.mlnx task failed with the following error: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::Conflict]: 409 Conflict) for proxy https://l-foreman-01.mtl.labs.mlnx:8443/dhcp
this a log from proxy-log:
023-02-22T17:21:43 073b2aae [W] Record 10.7.161.0/10.7.161.10 already exists: Proxy::DHCP::Collision: Record 10.7.161.0/10.7.161.10 already exists
i made sure there are no record of this in leases, but after digging in google i believe i need to execute foreman-rake tasks to clean this record for me but none of what i found seem to work for me
please help.
Foreman and Proxy versions:
foreman 3.3.1
foreman-proxy-3.3.1-1.el8.noarch
rubygem-foreman_ansible-7.1.0-3.fm3_3.el8.noarch
foreman-cli-3.3.1-1.el8.noarch
foreman-debug-3.3.1-1.el8.noarch
foreman-installer-3.3.1-2.el8.noarch
rubygem-hammer_cli_foreman-3.3.0-1.el8.noarch
rubygem-foreman-tasks-6.0.2-1.fm3_3.el8.noarch
foreman-postgresql-3.3.1-1.el8.noarch
foreman-dynflow-sidekiq-3.3.1-1.el8.noarch
rubygem-hammer_cli_foreman_puppet-0.0.6-1.fm3_3.el8.noarch
foreman-vmware-3.3.1-1.el8.noarch
foreman-service-3.3.1-1.el8.noarch
rubygem-foreman_remote_execution-7.1.0-1.fm3_3.el8.noarch
foreman-release-3.3.1-1.el8.noarch
rubygem-foreman_puppet-4.0.1-1.fm3_3.el8.noarch
rubygem-foreman_setup-8.0.1-2.fm3_3.el8.noarch
foreman-3.3.1-1.el8.noarch
Other relevant data:
