#theforeman

Hmm, anyone here had issues with db:migrate when going from 3.0 to 3.2 ?

revellion, whats the error?

revellion: the docs recommend going through 3.1 first :/

dLobatog: oh, snapshot rollback to 3.0 then maybe?

sean797: the error i got was AddMissingViewPermissions: migrating, and a ton of red text trace ontop

dLobatog: i naively thought i could go a minor release step up at once. But i might be mistaken. just like i was with 2.4.2 -> 2.4.4 -> 3.0 ?

I mean, it might work - it's just not tested on the release process

dLobatog: btw reference to that docs post?. didn't see it in the upgrade notes

revellion: https://theforeman.org/manuals/1.13/index.html#...

dLobatog: thanks for the reference. i focused too much on the katello upgrading instructions that i forgot to check the foreman side of it aswell

revellion: it's not obvious, feel free to submit changes to the docs if you found anything to complicated

dLobatog: i've started to realise that, our internal wiki has grown a bit to catch a few gotchas already. one i discovered was that the advice to yum update foreman-release-scl on 3.0 applies quite aswell to 3.1 and 3.2 also

dLobatog: a college of mine has started to contribute through github some pieces lately. martencassel. a good guy at documenting.

revellion: we'd be happy to get all of those gotchas into the official docs or fix the usability so they are solved for everyone :)

revellion: ah good :) it's really just a matter of submitting your edits here - https://github.com/theforeman/theforeman.org/ - easy enough I think

hi all, i'm working on ovirt network integration to ease host creation on ovirt backend. The goal is to map automaticaly selected oVirt network when a foreman network is selected on host creation, based on VLAN ID. This is a part of #10539. I've a POC for the backend side (mapping subnet to ovirt networks and provide them as json array like it's done for subnet), but i didn't work ATM on the ui side. Before investing more time on it, i wanted to know

if the foreman project have some interest on it

bagasse: #10539 is http://theforeman.org/issues/10539 "Feature #10539: Automatically assign oVirt name and network - Foreman"

It needed some small improvments on rbovirt too, but that is ready i think for a PR

bagasse: patches are welcomed :)

bagasse: also, for dev related questions, there is #theforeman-dev channel

ohadlevy: ok, i will ask on -dev chan

what is the proper location for overriding the PassengerMaxPoolSize (and related) params? I tried the 05-foreman-ssl.conf but it still seems to pick the config from 25-puppet.conf

both are in a seperate vhost

ah, poolsize is server wide, maxinstances is per app

Anyone know why foreman report uploads would successfully forward but not the foreman facts?

hey all! Anyone working on the integration of bond and bridge support in the debian preseed finish script? https://github.com/theforeman/community-templat...

else I'll do some experiment

and start coding something. I'd rather not duplicate the work :)

guy: do you get an error?

ohadlevy: In the proxy log, I get a 500 error telling me to look in the production log. In there, the error is Action failed: Error: null value in column "chef_proxy_id" violates not-null constraint

guy: ah, ok chef specific issue, maybe mhulan knows, hopefully he'll be back online soon...

spidern: that would be highly appreciated!

mhulan: Hey it's me again haha. I have a problem with chef where foreman reports is successfully forwarding but foreman facts isn't. I'm getting a 500 response from foreman telling me to look in the production log. In there, the error is Action failed: Error: null value in column "chef_proxy_id" violates not-null constraint

mhulan: and thanks in advance!!

guy: oh, what version of Foreman and foreman_chef are you running?

mhulan: Chef client version 12.13.37 and foreman 1.12.3

mhulan: oh foreman_chef hang on

guy: hm, weird, the constraint was not defined in the migration, what DB backed do you use?

@mhulan: I'm not sure, do you know where I could find that?