Re: [foreman-dev] Cannot view full report | Openscap
The issue was opened as http://projects.theforeman.org/issues/20077 which is now considered resolved. The issue was that the given host did not have openscap smart proxy assigned. -- Marek On čtvrtek 22. června 2017 16:56:27 CEST sai krishna Khanday wrote: > Hello, > > Foreman Host OS: RHEL 7.3 > Foreman Version: 1.15.0 > Foreman OpenSCAP Plugin Version: 0.7 > > > When trying to view a full report in the Foreman UI, we are receiving the > following error: > > > ERF42-7625 [Foreman::Exception]: No OpenSCAP proxy found for > ForemanOpenscap::ArfReport with 996599 > > > There is no addition information regarding the error code. > > http://projects.theforeman.org/projects/foreman/wiki/ERF42-7625?parent=Error > Codes > > > I made sure smartproxy has openscap as active feature. Reports are > generated and uploaded but getting above error while trying to access full > report and even compliance openscap metrics is also blank. > > > I don't see any openscap error logs generated in > /var/log/foreman-proxy/proxy.log or /var/log/foreman/production.log > > > Thanks ! -- 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] #10089 - not so simple?
Hello, thanks for your contribution! I'd recommend opening the PR on github with the change, that way it will get attention of more reviewers. If you're not sure about the process, please find a description at [1]. My opinion on the change is that it should change the font only for text areas that contain the YAML/ JSON, therefore in this case only when parameter type is set to YAML/JSON. Thanks [1] https://www.theforeman.org/contribute.html#SubmitPatches -- Marek On neděle 25. června 2017 14:09:22 CEST Eric Anderton wrote: > New poster, long time Foreman user, and hopeful contributor here. > > As I've decided to take the plunge into contributing to Foreman, I figured > #10089 might be a good newbie task to pick off: > > http://projects.theforeman.org/issues/10089 - Use fixed-width font for > parameters > > """As some parameters are displayed as YAML, using a fixed-width font would > greatly ease reading and writing of such values. > Right now, indentation is too hard to get right and I usually have to edit > the parameter in an external editor then copy-paste the content in order to > avoid problems.""" > > --- > > My hunch is that this has been sitting open for two years now because > either it's really this simple, or there's some nuance here not documented > in the feature request. > > The code below sets textarea.form-control fields to monospace. Since > is used in a lot of places next to controls that are styled as > Helvetica, modifying all places where .form-control is used would cause > cosmetic issues. Plus, the lack of fixed-width input today is mostly an > issue for multi-line input (AFAIK). > > Example: > https://github.com/eanderton/foreman/commit/84657c11c0893b86b922dc0b70047863 > 9ea26217 > > I'm open to any additional suggestions on this one. Any feedback? > > Thanks, > - Eric Anderton -- 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] Nomination for an additional GitHub org owner
+1 On pondělí 26. června 2017 7:41:18 CEST Ondrej Prazak wrote: > +1 from me > > On Mon, Jun 26, 2017 at 3:16 AM, Tom McKay wrote: > > +1 for @ehelms > > > > On Fri, Jun 23, 2017 at 9:05 AM, Neil Hanlon wrote: > >> +1 from me :) > >> > >> On Fri, Jun 23, 2017 at 8:44 AM Greg Sutcliffe > >> > >> wrote: > >>> Hi all, > >>> > >>> Slightly different to our usual "nominate a new commiter" process, but > >>> I'm wondering if we need to appoint a new owner on our GitHub > >>> organisation? > >>> > >>> Currently, only Dominic and Ohad are owners, and they are both > >>> frequently busy with other things, which leads to some delays when > >>> adding in new repos or moving things about. 2 people is also a fairly > >>> high bus factor. I think it's time we added a third name to the owners > >>> - we don't have an official process for this, but I'm treating like > >>> commit access, so here's a nomination email. > >>> > >>> Obviously, this is mainly a role for maintenance - creating/forking > >>> repos, moving them, creating new teams, etc. rather than about merging > >>> code. I think a we have a few people that would be a good fit - my > >>> suggestion would be Eric Helms. He's experienced both in our structure > >>> & in GitHub-y stuff, and is in a different timezone, which helps if > >>> something comes up out of European hours. > >>> > >>> Any comments/concerns/upvotes? :) > >>> > >>> Cheers > >>> 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. > >> > >> -- > >> 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. > > > > -- > > 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. -- 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] Nomination for an additional GitHub org owner
+1 from me On Mon, Jun 26, 2017 at 3:16 AM, Tom McKay wrote: > +1 for @ehelms > > On Fri, Jun 23, 2017 at 9:05 AM, Neil Hanlon wrote: > >> +1 from me :) >> >> On Fri, Jun 23, 2017 at 8:44 AM Greg Sutcliffe >> wrote: >> >>> Hi all, >>> >>> Slightly different to our usual "nominate a new commiter" process, but >>> I'm wondering if we need to appoint a new owner on our GitHub >>> organisation? >>> >>> Currently, only Dominic and Ohad are owners, and they are both >>> frequently busy with other things, which leads to some delays when >>> adding in new repos or moving things about. 2 people is also a fairly >>> high bus factor. I think it's time we added a third name to the owners >>> - we don't have an official process for this, but I'm treating like >>> commit access, so here's a nomination email. >>> >>> Obviously, this is mainly a role for maintenance - creating/forking >>> repos, moving them, creating new teams, etc. rather than about merging >>> code. I think a we have a few people that would be a good fit - my >>> suggestion would be Eric Helms. He's experienced both in our structure >>> & in GitHub-y stuff, and is in a different timezone, which helps if >>> something comes up out of European hours. >>> >>> Any comments/concerns/upvotes? :) >>> >>> Cheers >>> 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. >>> >> -- >> 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. >> > > -- > 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. > -- 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] Nomination for an additional GitHub org owner
+1 for @ehelms On Fri, Jun 23, 2017 at 9:05 AM, Neil Hanlon wrote: > +1 from me :) > > On Fri, Jun 23, 2017 at 8:44 AM Greg Sutcliffe > wrote: > >> Hi all, >> >> Slightly different to our usual "nominate a new commiter" process, but >> I'm wondering if we need to appoint a new owner on our GitHub >> organisation? >> >> Currently, only Dominic and Ohad are owners, and they are both >> frequently busy with other things, which leads to some delays when >> adding in new repos or moving things about. 2 people is also a fairly >> high bus factor. I think it's time we added a third name to the owners >> - we don't have an official process for this, but I'm treating like >> commit access, so here's a nomination email. >> >> Obviously, this is mainly a role for maintenance - creating/forking >> repos, moving them, creating new teams, etc. rather than about merging >> code. I think a we have a few people that would be a good fit - my >> suggestion would be Eric Helms. He's experienced both in our structure >> & in GitHub-y stuff, and is in a different timezone, which helps if >> something comes up out of European hours. >> >> Any comments/concerns/upvotes? :) >> >> Cheers >> 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. >> > -- > 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. > -- 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] Re: Cannot view full report | Openscap
I haven't used the OpenSCAP feature in a while, but if I recall correctly, it relies on the SmartProxy to bring results back to foreman itself (just like everything else Foreman). Some things I would check: * SmartProxy configuration * Foreman configuration for SmartProxy (make sure that it shows up in the GUI) * Permissions on log files on the host where the SmartProxy is running -- 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] #10089 - not so simple?
New poster, long time Foreman user, and hopeful contributor here. As I've decided to take the plunge into contributing to Foreman, I figured #10089 might be a good newbie task to pick off: http://projects.theforeman.org/issues/10089 - Use fixed-width font for parameters """As some parameters are displayed as YAML, using a fixed-width font would greatly ease reading and writing of such values. Right now, indentation is too hard to get right and I usually have to edit the parameter in an external editor then copy-paste the content in order to avoid problems.""" --- My hunch is that this has been sitting open for two years now because either it's really this simple, or there's some nuance here not documented in the feature request. The code below sets textarea.form-control fields to monospace. Since is used in a lot of places next to controls that are styled as Helvetica, modifying all places where .form-control is used would cause cosmetic issues. Plus, the lack of fixed-width input today is mostly an issue for multi-line input (AFAIK). Example: https://github.com/eanderton/foreman/commit/84657c11c0893b86b922dc0b700478639ea26217 I'm open to any additional suggestions on this one. Any feedback? Thanks, - Eric Anderton -- 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] Cannot view full report | Openscap
Hello, Foreman Host OS: RHEL 7.3 Foreman Version: 1.15.0 Foreman OpenSCAP Plugin Version: 0.7 When trying to view a full report in the Foreman UI, we are receiving the following error: ERF42-7625 [Foreman::Exception]: No OpenSCAP proxy found for ForemanOpenscap::ArfReport with 996599 There is no addition information regarding the error code. http://projects.theforeman.org/projects/foreman/wiki/ERF42-7625?parent=ErrorCodes I made sure smartproxy has openscap as active feature. Reports are generated and uploaded but getting above error while trying to access full report and even compliance openscap metrics is also blank. I don't see any openscap error logs generated in /var/log/foreman-proxy/proxy.log or /var/log/foreman/production.log Thanks ! -- 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] Proposal to move "How to create a plugin" page to github.
Timo, Since we already are using the site to host the handbook, I think it would be nice if plugin writing guidelines would be there too. If we look at plugin writers as "core users", would the site be better suited for the task? ;) For the development workflow: First, if the docs PR is mentioned in the code PR (as it should), Github makes it pretty easy to follow the link for the code maintainer. IMHO there are two advantages for different repos 1. The docs PR is exposed to additional maintainers that could give additional input about the quality of the documentation itself (like styling, english e.t.c). 2. It decouples the lifecycles of the changes. Let's say that the code is already perfect, but the docs still need some work. I don't think we should not merge the code and wait for the docs to mature. Marek, I think a simple link in our readme file would be a quite good compromise for syncing code and docs repos. I suggest either "Plugins" or "How to contribute" chapters. It should also increase the visibility of the page. +1 to google optimization About template writing wiki: I don't want to derail this thread, but after we agree on a place for plugin writing wiki, I can start another one for template writing as well. One issue per commit, isn't it ;) On Friday, June 23, 2017 at 9:36:56 AM UTC+3, Marek Hulán wrote: > > > Am 22.06.17 um 11:16 schrieb Greg Sutcliffe: > > > +1 for moving the plugin documentation to the plugins part of the > > > website. I think that makes sense, and we can (as with other areas) > > > keep the wiki for footnotes, edge cases, and tips. > > > > > > Greg > > > > I'd suggest to add a Markdown file to the core repo. I believe code > > documentation is better suited to be in the code repo and the > > documentation can be reviewed alongside the code change in core by core > > maintainers. The website should be more for foreman users. But > > theforeman.org is fine with me as well. > > > > - Timo > > Having this info in the codebase itself sounds reasonable but I'd prefer > having it on one place with other pages such as template writing wiki. The > later is also useful for users and ideally will be moved to theforeman.org > one > day. > > If there was a reliable way to sync it from theforeman.org to core > codebase, > that would we great. If I had to choose between these two, then I find > theforeman.org better. I think Google would give better results for > potential > plugin writers too. > > -- > Marek > -- 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.
