#theforeman

Hi there , Question related delete host in Foreman , Normally should foreman_proxy triggerd by foreman to delete host puppet ca ?

installation has unattended: true option . and sudoers file has foreman-proxy ALL = (root) NOPASSWD : /opt/puppetlabs/bin/puppet cert * Defaults:foreman-proxy !requiretty

or otherways can I send API call to smart proxy to delete host puppet ca ?

ping!

i still get errors when creating a new vm in vmware <NoPermission: Permission to perform this operation was denied.> (i did not get this messages before the update) + when using the remote-execution plugin: <Failed to initialize: Dynflow::ExecutionPlan::Steps::Error - The only applicable proxy ... is down>

Alucard616: what distro?

centos 7

Alucard616: is the smart_proyx_dynflow_core service running on your system?

inecas: sek

inecas: yep

Alucard616: what about smart-proxy service?

sry, foreman-proxy

inecas: it runs also (foreman-tasks, too)

is the provisioning task (especially for a compute resource) now a dynaflow task ?

ikonia: nope

Alucard616: how many proxies do you have around?

inecas: none. i have only one server

Hi there , Question related delete host in Foreman , Normally should foreman_proxy triggerd by foreman to delete host puppet ca ?

installation has unattended: true option . and sudoers file has foreman-proxy ALL = (root) NOPASSWD : /opt/puppetlabs/bin/puppet cert * Defaults:foreman-proxy !requiretty

or otherways can I send API call to smart proxy to delete host puppet ca ?

Alucard616: anything interesting in /var/log/foreman-proxy/smart_proxy_dynflow_core.log (I recommend restarting smart_proxy_dynflow_core service and watching the logs)

inecas: https://thepasteb.in/p/58hgEgQ3DW2cv

Alucard616: is the service running now and listening on port 8000?

inecas: yes and no. nothing on port 8000

Alucard616: anything in the journal for the service?

inecas: https://thepasteb.in/p/Q1hBOBEAMzzC8

inecas: these are the only messages besides starting and stopping

Alucard616: ps -Af | grep smart_proxy

inecas: <foreman+ 26346 1 0 15:16 ? 00:00:00 ruby /usr/bin/smart_proxy_dynflow_core -d -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid>

Alucard616: ah, sry, could you check 8008 port instead

inecas: np np^^ <tcp 0 0 127.0.0.1:8008 0.0.0.0:* LISTEN 26346/ruby>

inecas: <ruby 26346 foreman-proxy 8u IPv4 215916 0t0 TCP localhost:8008 (LISTEN)>

Alucard616: how about `curl -k --cert /etc/foreman-proxy/foreman_ssl_cert.pem --key /etc/foreman-proxy/foreman_ssl_key.pem https://localhost:8008/tasks/count`

Alucard616: how does your /etc/smart_proxy_dynflow_core/settings.yml looks like?

Alucard616: it seems like an issue with the service not listenign on 0.0.0.0

inecas: https://thepasteb.in/p/LghNKNp2KK6fZ

inecas: sec

inecas: https://thepasteb.in/p/76hElExGP6RiV

inecas: https://thepasteb.in/p/y8h6Z6zOOZNIO

inecas: sorry. my browser did not respond^^

Alucard616: have you run the installer after the update?

inecas: no. i haven't

Alucard616: https://paste.fedoraproject.org/paste/NhhWIH7Rd...

Alucard616: this is how the production setting file should look like

inecas: i'll test that, sec

Alucard616: you might need to update the foreman_url, the problem is, since installer was not used at the beginning, it's pretty hard for me to find where the issue with settings is

inecas: i see. i didn't know, that i have to run the foreman-installer again, after an update to e.g. 1.13.x to 1.14.x

i have come a cross what seems to be a bug. When i delete hosts, their DNS record remains. If I create a new host with the same name, it fails to overwrite. and the rollback also fails.

Create IPv4 DNS record for labb01.se-ix.delta.prod task failed with the following error: ERF12-2357 [ProxyAPI::ProxyException]: Unable to set DNS entry ([RestClient::Conflict]: 409 Conflict) for proxy http://foreman.se-ix.delta.prod:8443/dns

Failed to perform rollback on DHCP conflicts removal for labb01.se-ix.delta.prod - Must define a hostname

Raboo: ERF12-2357 has a wiki page - see http://theforeman.org/projects/foreman/wiki/ERF...

shouldn't foreman overwrite dns records?

inecas: that didn't help. I'll create a clone an let foreman-installer rerun

Alucard616: have you used the installer to install the remote execution plugin?

Raboo: normally it allows to override, but in this case it failed, it could be a bug

inecas: I'm not sure about it

hola muchachos! :D

hopefully I'm working on integration between foreman and gpu instance @google

but i have a question that will help me to test it out

what do i need to do in order connecting existing instance (that wasn't created by foreman) to foreman

please help

DaveTaboola: do you use puppet?

inecas: nope, that made things worse ^^ i think I'll perform a rollback and check the update again

ohadlevy ok, i will report it then