#theforeman

mmoll: fresh installation on a new vm. virgin permissions on all directories. i can su to foreman-proxy and cat the pem file in prvate_keys... but registration STILL fails

Unable to communicate with the proxy: Permission denied @ rb_sysopen - /etc/puppetlabs/puppet/ssl/private_keys/example.pem

sleepingkangaroo: it might also be the foreman user... is that coming from the proxy or the foreman log?

console

foreman server is on another system

mmoll: there's no foreman instance on this vm

it's connecting to another server. selinux is disabled, iptables as well

on both servers

the rest is running as root, I think... no real idea, except to check which component is realy getting that error

foreman-proxy belongs to: d foreman-proxy

uid=498(foreman-proxy) gid=498(foreman-proxy) groups=498(foreman-proxy),500(puppet)

using the foreman_proxy puppet module to install

it's a bit more complicated...

to register the proxy, an API request to the foreman instane is sent, which in turn conencts to the proxy to query its features

so there are multiple points where certs are used

i see

mmoll: isn't only puppet and foreman-proxy as users though?

sleepingkangaroo: again, as a start, check the proxy log. if it's not there, it might be the API request to register it

or something else...

anyway, it's nearly 4 AM here, l8er...

mmoll: foreman-proxy proxy.log shows the cert

this is hella frustrating

mmoll: i had a space in the proxy's registered name :\

argh fail … we are not using lifecycle env yet, so only Library is used. Somebody synced a repository that should not have been synced … result we have versions issues bla bla bla … It's a Jboss repo so not a custom repo, and katello does not want me to remove packages from the product …

is there a way to say something like: please filter out all packages of the last sync , before creating a new content view ?

Bardack: I don't quite follow what you want to accomplish, you want content views to only have a subset packages of a product?