Re: [foreman-users] [foreman-announce] Katello 3.5.0 (a.k.a. Schwarzbier) is Here!

Thanks to all involved! Updates applied easier than ever before. Nice little speed bump in spots. Cheers L. -- "The antidote to apocalypticism is *apocalyptic civics*. Apocalyptic civics is the insistence that we cannot ignore the truth, nor should we panic about it. It is a shared

Re: [foreman-users] Upgrading 1.15.6 -> 1.16.0 causes 'no such middleware error'

But I had to remove tfm-rubygem-foreman_default_hostgroup My fix is in this post https://groups.google.com/forum/m/?source=mog=us#!topic/foreman-users/bWfJJ-xyzGE -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group

[foreman-users] [foreman-announce] Katello 3.5.0 (a.k.a. Schwarzbier) is Here!

Katello 3.5.0 is now available; It works with the recently released Foreman 1.16.0. This release fixes 28 bugs since 3.5 RC2 - thanks to all who tested and reported issues! Installation instructions: https://theforeman.org/plugins/katello/3.5/installation/index.html Upgrade instructions:

[foreman-users] Foreman Internal DB assigned ip space issue

I've noticed a bug in foreman when assigning IP space using the "Internal DB". We currently want both ipv4 and ipv6 space to match when assigned. Something like this. 10.0.0.230 :XXX:XXX:5::0:230 If you set the range of ipv4 space to 10.0.0.230 to 10.0.0.250 and :XXX:XXX:5::0:230 to

[foreman-users] Re: Upgrade from 1.15.6 to 1.16

I think I'm having the same problem. It's the same error in the same place. Here's the user group topic On Wednesday, December 6, 2017 at 7:10:18 PM UTC-6, Jeff Stasko wrote: > > Any of the foreman-rake runs are failing how do