Re: [foreman-dev] Getting Foreman and Smart-Proxy to run in FIPS environment.
I added a bunch of (more) granular-level issues to http://projects.theforeman.org/issues/3511 tracker. Cheers, -d On Wed, Nov 22, 2017 at 2:13 PM, Dmitri Dolguikh wrote: > On Wed, Nov 22, 2017 at 9:33 AM, James Shewey wrote: > >> You may not be getting an ABRT because ruby was patched some time ago to >> catch this ABRT and a handler was created to make this a non-fatal error >> (ruby used to just core dump - see https://bugzilla.redhat.com/sh >> ow_bug.cgi?id=717709). I suspect that is why you aren't seeing the >> expected signal further down the stack. >> > > This doesn't explain the behaviour I'm seeing -- an exception would be > caught and logged, and foreman would continue to run. I'm seeing the app > exit without any stacktraces or core-dumps. I'm not using system ruby > either. > > -d > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Discourse - next steps / actions
Hi all, I'll try to keep this brief, at least by my standards :) Firstly, I think it's clear that the discussion is leaning towards implementing Discourse for at least one, and possibly both, of the mailing lists. Many people have contributed - I'd like to thank them all for keeping this from descending into a flamewar :) We do need to give the users list a little longer for feedback (it's only been a week), but I think here we can start to talk about the migration planning. Since we all (or most?) need to start getting used to Discourse, I've written up a draft migration plan there: https://community.theforeman.org/t/draft-migration-plan-theoretical/7550 I've just updated it to reflect the latest discussions. No doubt I have missed something though, so I've made it into a wiki post - feel free to edit with suggestions. There are two things I'd like to get input from people on: # Moderators I need a small team of moderators to deal with running the forum. I don't expect it to take up much time, but it is important that more people than just me know how things work. 3-4 people (including me) is probably enough to start with. So, volunteers needed! Don't make me start picking on people :) # Choice of lists to migrate As above, we have to decide if we migrate both lists or just one. I see significant benefits on having everyone on the same platform (top 2 - the @groups feature is very useful for discussions, and the discoverability of dev discussions for users helps them to get involved and grow our dev community). However, I know others are more cautious than I. Again, since we'll all likely be using Discourse in some capacity, I've gone ahead and created a poll on Discourse for us. Please do leave your feedback! Votes by email-response (here or on Discourse) are of course acceptable for those allergic to UIs, I will add them in ;) https://community.theforeman.org/t/poll-which-lists-should-migrate-to-discourse/7598 I've not covered foreman-announce - we use this so infrequently, and posting rights are heavily restricted, so I think we can decide what to do with it later. Hang in there, we're getting to the fun bit! :) Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] 1.17 branching - status update
Thanks please announce the branching day a day ago and ask to stop merging breaking changes, so we can test our plugins with the "candidate" for branching. That would be super nice! LZ On Thu, Nov 23, 2017 at 2:03 PM, Ondrej Prazak wrote: > Hi, > this is just a quick summary of where we stand with 1.17, please feel free > to correct me if I got something wrong. > > foreman_selinux, smart-proxy, installer and modules have no blockers - at > least none that we know of. > > Blockers for foreman are dynflow and Rails 5.1 as already stated previously > [1]. I tried to get in touch with the person who opened a PR to fix > turbolinks [2], but I got no response, so I opened a PR directly against > turbolinks [3]. foreman-task needs to get rid of alias_method_chain [4] and > katello needs to update accordingly [5]. > > > O. > > [1] https://groups.google.com/forum/#!topic/foreman-dev/3G9GuQ6d8ms > [2] https://github.com/dobtco/turbolinks-classic/pull/1 > [3] https://github.com/turbolinks/turbolinks-classic/pull/679 > [4] https://github.com/theforeman/foreman-tasks/pull/300 > [5] https://github.com/Katello/katello/pull/7083 > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] 1.17 branching - status update
Hi, this is just a quick summary of where we stand with 1.17, please feel free to correct me if I got something wrong. foreman_selinux, smart-proxy, installer and modules have no blockers - at least none that we know of. Blockers for foreman are dynflow and Rails 5.1 as already stated previously [1]. I tried to get in touch with the person who opened a PR to fix turbolinks [2], but I got no response, so I opened a PR directly against turbolinks [3]. foreman-task needs to get rid of alias_method_chain [4] and katello needs to update accordingly [5]. O. [1] https://groups.google.com/forum/#!topic/foreman-dev/3G9GuQ6d8ms [2] https://github.com/dobtco/turbolinks-classic/pull/1 [3] https://github.com/turbolinks/turbolinks-classic/pull/679 [4] https://github.com/theforeman/foreman-tasks/pull/300 [5] https://github.com/Katello/katello/pull/7083 -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
