Activity

From 04/30/2018 to 05/29/2018

09:13 PM Feature #6901: foreman-cleanup command: That would be good candidate for inclusion in foreman-maintain. Martin Bacovsky
07:41 PM Feature #6901: foreman-cleanup command: We have a katello-remove script. It'd be good to make that generic enough to also allow cleanups of Foreman. Ewoud Kohl van Wijngaarden
07:46 PM Feature #4788: Plugin rpms not signed: We do have HTTPS enabled on yum.theforeman.org but don't use it by default in the repos. It should be easy to change ... Ewoud Kohl van Wijngaarden
07:38 PM Feature #4313 (Rejected): Replace EPEL dependency with Foreman repo: Given the current state of packaging I'm closing this. If there's sufficient demand from users I'd be happy to revisi... Ewoud Kohl van Wijngaarden
07:34 PM Bug #3211: Config /etc/httpd/conf.d/foreman.conf is not owned: I'm leaning to rejecting this as I don't see us changing this. Opinions? Ewoud Kohl van Wijngaarden
07:26 PM Feature #23613 (Resolved): Package react-debounce-input: Ewoud Kohl van Wijngaarden
03:05 PM Revision 82f1e07e (foreman-packaging): Bump rubygem-foreman_snapshot_management to 1.5.0: Matthias Dellweg

08:21 AM Revision 9e31024d (foreman-packaging): Implement generating dependencies while bumping gems: This extends the update-node-dependencies model to be generic. It can
now parse files with begin and end markers to g... Ewoud Kohl van Wijngaarden

07:01 PM Bug #23616 (Closed): require foreman-maintain in katello: Applied in changeset commit:foreman-packaging|18367969b6abf0f980118403647ba806b0f4a2d9. John Mitsch
07:01 PM Bug #23614 (Closed): Remove katello-backup/restore: Applied in changeset commit:foreman-packaging|18367969b6abf0f980118403647ba806b0f4a2d9. John Mitsch
06:42 PM Revision 18367969 (foreman-packaging): Fixes #23614 #23616 - Remove katello-backup and katello-restore.: Katello-backup and katello-restore have moved to foreman-maintain. The commands
in foreman-maintain support remote da... John Mitsch
06:04 AM Bug #19069: DNS and DHCP providers for libvirt fail to start: If you have a devel proxy, @bundle install@ should get you the gems you need - at least for me it does. Do you have a... Ondřej Pražák
12:00 AM Revision ed161b7a (foreman-packaging): Drop packages from comps not used anymore: Eric Helms

09:36 PM Bug #19069: DNS and DHCP providers for libvirt fail to start: I think this bug is still valid. I am facing this in the development environment. Rahul Bajaj

12:18 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: Here is an strace of the command if this helps:
https://gist.github.com/tek0011/ea691e3692d651c0e60a8211bf6b3b83 Jeff Sparrow
12:10 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: Ewoud Kohl van Wijngaarden wrote:
> No, that's new to me. I wonder if they all try to open the log file. I'd verify ... Jeff Sparrow
11:48 AM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: kerberos issue fix is to use cr: yum-config-manager --enable cr
Jeff Sparrow

12:45 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: Narrowed it down more. It seems like its all related to foreman_host_overview - If I comment out the other informati... Jeff Sparrow
12:32 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: Narrowed it down. I hit the deadlock error as soon as I rename/remove /usr/share/foreman/bundler.d/Gemfile.local.rb ... Jeff Sparrow
12:26 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: Well nevermind. I tried to re-run the db migrate and hit the first error listed in this ticket. Went to try and rem... Jeff Sparrow
12:22 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: I was able to get past the Deadlock error by removing all gems in /opt/rh/rh-ruby22/root/usr/local/share/gems/gems
... Jeff Sparrow

09:08 PM Revision c1a12129 (foreman-packaging): update smart_proxy_salt to 2.1.9: Michael Moll
09:03 PM Revision 32fad771 (foreman-packaging): update foreman_salt to 10.0.0: Michael Moll
08:19 PM Revision 5e3d7555 (foreman-packaging): update foreman_xen to 0.6.1: Michael Moll
02:10 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: No, that's new to me. I wonder if they all try to open the log file. I'd verify there's no process with that file ope... Ewoud Kohl van Wijngaarden
02:08 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: Thanks. Does that still pertain to the last error? The deadlock that happens after the plugins were removed? Jeff Sparrow
02:04 PM Bug #23529: Multiple Issues Upgrading from 1.16 to 1.17: I suspect you installed the foreman datacenter plugin manually. That depends on prawn. In 1.17 we moved from ruby 2.2... Ewoud Kohl van Wijngaarden
01:50 PM Bug #23529 (Resolved): Multiple Issues Upgrading from 1.16 to 1.17: I am trying to upgrade from 1.16 to 1.17 following the standard upgrade procedure as listed in the documentation.
... Jeff Sparrow
01:25 PM Revision 74e52662 (foreman-packaging): update foreman_xen to 0.6.1: Michael Moll

Also available in: Atom

Foreman » Packaging