Re: [foreman-dev] Getting Foreman and Smart-Proxy to run in FIPS environment.

Do you have some examples how such an abort looks like with and without GDB? with gdb + .gdbinit: Program received signal SIGABRT, Aborted. 0x7fb45991e1f7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 56 return INLINE_SYSCALL (tgkill, 3, pid, selftid,

Re: [foreman-dev] Nominating cfouant for write access to hammer-cli-katello

+1 from me On Tuesday, November 21, 2017 at 11:40:48 AM UTC-5, Andrew Kofink wrote: > > I hereby nominate Christine Fouant to gain commit access to > hammer-cli-katello. She currently has 12 merged PRs >

[foreman-dev] Nominating cfouant for write access to hammer-cli-katello

I hereby nominate Christine Fouant to gain commit access to hammer-cli-katello. She currently has 12 merged PRs and has helped to review 11 merged PRs

Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Tue, Nov 21, 2017 at 11:10:41AM +0200, Ohad Levy wrote: On Tue, Nov 21, 2017 at 11:02 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: On Sun, Nov 19, 2017 at 09:35:04PM +0100, Ewoud Kohl van Wijngaarden wrote: On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy wrote:

Re: [foreman-dev] Getting Foreman and Smart-Proxy to run in FIPS environment.

Thanks, so ABRT is raised when a FIPS-enabled library (e.g. openssl) catches an attempt to use non-approved cipher. Do you have some examples how such an abort looks like with and without GDB? Why I am asking. Once we start supporting FIPS, I wonder how we are gonna provide support for users and

Re: [foreman-dev] Foreman instrumentation for telemetry proposal

Thanks for question, this will be completely opt-in via /etc/foreman/settings.yaml. You can turn off (default behavior when not set), or on via prometheus, statsd or logging implementation (for debugging purposes - sends stats to Rails log / production.log). On Mon, Nov 20, 2017 at 4:31 PM, Bryan

Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Tue, Nov 21, 2017 at 11:02 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Sun, Nov 19, 2017 at 09:35:04PM +0100, Ewoud Kohl van Wijngaarden wrote: > >> On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy wrote: >> >>> >>> Can anyone shed some light on ETA for 1.16

Re: Re: [foreman-dev] Re: 1.15.4 - 1.16 RC.1 - 1.17 status

On Sun, Nov 19, 2017 at 09:35:04PM +0100, Ewoud Kohl van Wijngaarden wrote: On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy wrote: Can anyone shed some light on ETA for 1.16 GA? I should have given an update earlier. So far we've been wanting to include the foreman tasks as a service