#theforeman

good morning

ceegee: o/

dLobatog: ??

dLobatog: whats going on?

it's meant to be a person waving, the 'o' is the head

ah :)

hm, the foreman hooks are still a bit strange to me. I need to create a post-install script for a specific type of host (XenServer) with host-specific information in it. I created /usr/share/foreman/config/hooks/host/managed/create/01_test.sh and rebuilt a host, but the hook was not executed. the plugin foreman_hooks seems to be installed correctly, because its listed in the plugins in foreman ui.

any hints? maybe the hook is not working if a system already exists and I just rebuild it?

rebuilding isn't creating, there are build (after_build/before_provision) hooks for that, see the docs

Dom

D

fgfff

sorry

little network outage

Dominic: I have read the docs (https://github.com/theforeman/foreman_hooks) but in my opinion it lacks some information. for example host/managed/create, at which point of creating / provisioning a host I have reached this state? This document is only helpful if you already know something about the topic.

when you press "Submit" on the new host form

Dominic: okay, so it would be helpful if the docs contain a list with exactly this information, e.g. state create is reached when pressing submit ....

anyway

manual execution of the hook works fine, but on creating a new host in the UI it doesnt

can I safely assume that foreman-installer takes care of the changes in rpmnew files or do I need to review them all on a 1.11 -> 1.12 and katello 3.0 -> 3.1 update?

i've noticed that on a clean installation of katello 3.1, the "foreman-rake katello:reindex" command is no more present. Is it normal?

lzhou: it was renamed to katello:reimport

dLobatog: ah ok, so the katello:reimport does the same things as the katello reindex? why was renominated then?

lzhou: I'm not sure why it was renamed, sorry. this is where it was added. https://github.com/Katello/katello/pull/6192

Hey guys, facing a problem importing environments/classes in 1.12.3 with puppet 4.7.0. Foreman-Proxy gets a ([RestClient::NotAcceptable]: 406 Not Acceptable) message and Puppetmaster.log says: Puppet Denying access: Forbidden request: /puppet/v3/resource_type/* [search]

therm_: https://theforeman.org/manuals/1.12/index.html#... shows the auth.conf changes required to permit access

but /etc/puppetlabs/puppetserver/conf.d/auth.conf contains this one : {

match-request: {

path: "/puppet/v3/resource_type"

type: path

method: [get, post]

}

allow: "*"

sort-order: 500

name: "puppetlabs resource type"

},

please use a pastebin for lots of text. It's possible then that you're not using the HOCON file, it isn't the default.

hmm, my hook is still not working :(

DLobatog: thanks for the help and the link :)

what is the difference between host/base and host/managed? I can not find any docs with descriptions of that

host/base is a parent of host/managed. I wouldn't suggest using it.

actually I have a very simple script located in host/managed/update

I exepected that this script will be executed when I edit a host and change the comment for example

Finished discovering 1 hooks for Host::Managed#update

at least this looks okay, but I can not figure out why nothing happens

the directory structure under hooks belongs to foreman:foreman, just like the script itself which is executeable of course

Dominic: do I misunderstand the usage of the hook and host/managed/update? it would be great to get it working

no

do you have any hints what else I can look for?

read the logs and recheck your configuration