[foreman-dev] Errr dureing installation - Erro durante instalação do foreman.
Alguém poderia me ajudar? Durante a instalação do foreman+Puppet, no CentOS, após executar o foreman-installer apareceram estes erros: Could not set home on user[foreman]: Execution of '/usr/sbin/usermod -d /usr/share/foreman foreman' returned 8: usermod: user foreman is currently used by process 2150 /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:235:in `execute' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider.rb:101:in `execute' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/nameservice.rb:286:in `set' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/provider/nameservice.rb:73:in `block (2 levels) in resource_type=' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:194:in `call_provider' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:501:in `set' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:561:in `sync' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:236:in `sync' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:134:in `sync_if_needed' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in `block in perform_changes' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:87:in `each' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:87:in `perform_changes' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:in `evaluate' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:230:in `apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:246:in `eval_resource' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `call' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block (2 levels) in evaluate' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:387:in `block in thinmark' /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:386:in `thinmark' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block in evaluate' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in `traverse' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:in `evaluate' /usr/share/gems/gems/kafo-1.0.5/modules/kafo_configure/lib/puppet/parser/functions/add_progress.rb:30:in `evaluate_with_trigger' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in `block in apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in `with_destination' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:142:in `as_logging_destination' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in `apply' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in `block in apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:224:in `block in benchmark' /opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `benchmark' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:in `apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:343:in `run_internal' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:in `block in run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:294:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:195:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:350:in `apply_catalog' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:274:in `block in main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:294:in `override' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:225:in `main' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/apply.rb:170:in `run_command' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `block in run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:542:in `exit_on_fail' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application.rb:358:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:132:in `run' /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in `execute' /opt/puppetlabs/puppet/bin/puppet:5:in `' /Stage[main]/Foreman::Config/User[foreman]/home: change from /home/foreman to /usr/share/foreman failed: Could not set home on user[foreman]: Execution of '/usr/sbin/usermod -d /usr/share/foreman foreman' returned 8: usermod: user
Re: [foreman-dev] Re: Revert removal of @host.params for host_param
Right now 1.15 is released. I decided not to document the deprecation as the consensus seems to maintain both ways of addressing this. The deprecations are still going to show up in the logs, so I suggest someone submits a PR to remove the deprecations and cherry-pick it for 1.15.1 2017年4月20日木曜日 10時19分19秒 UTC+9 Andrew Schofield: > > At the very least support both. This is a point release and this is a > pretty major change for a non-major release. > > As per the comment from Ewoud the bulk of people who will use this use it > in ERB and templates. The templates being probably the easiest to 'fix'. > Personally, keeping this permanently and proxying to me seems like the > right thing to do. This functionality has existed for years and is very > heavily documented all over the place. > > On Wednesday, April 19, 2017 at 12:39:40 PM UTC-4, Greg Sutcliffe wrote: >> >> On Wed, 2017-04-19 at 14:10 +0300, Tomer Brisker wrote: >> > Since it seems there wasn't an agreement on reverting this made in >> > time for 1.15, I'd say we should support both for now and reconsider >> > in the future pending a rewrite of the template engine using a proxy >> > object as we discussed. >> >> +1, supporting both seems like the way forward. >> >> 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] Re: 1.15.0 release status
Thanks - all packages are out now, freight cache needs to be updated by someone with access to deb.theforeman.org, see the steps in: http://projects.theforeman.org/projects/foreman/wiki/Release_Process#Completion-tasks Similarly, those who have permissions please update Twitter, IRC and Google+ , I've just posted the announcement to foreman-users On Thu, May 11, 2017 at 4:12 PM, Dominic Cleal wrote: > On 11/05/17 02:16, Daniel Lobato wrote: >> Thanks, it seems like either I don't understand the combination filter >> or it didn't work >> (https://github.com/theforeman/foreman-infra/blob/cb03c58b7b2bf3b5c61a125e4c32841a07a6a274/puppet/modules/jenkins_job_builder/files/theforeman.org/yaml/jobs/release_test.yaml#L33) >> >> combination-filter: 'os == "el7" || os == "f24" || os == "jessie" || >> (os == "stretch" && version != "1.14" && version != "1.15") || os == >> "trusty" || os == "xenial"' > > It should have been using major_version, fixed. > >> http://ci.theforeman.org/job/release_push_deb/ doesn't have a >> combination filter so it just publishes to the other 3 repos.(jessie >> trusty and xenial). > > Fixed, added stretch. > > -- > Dominic Cleal > domi...@cleal.org > > -- > 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. -- Daniel Lobato @dlobatog daniellobato.me GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 -- 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] Script to recycle passenger processes
It's just a script as cron job, if we agree that hourly is viable option (that's what I think). I think I could also backport it into 1.15 as "opt-in" (e.g. disabled by default) so people can easily test it. On Wed, May 10, 2017 at 1:58 PM, Bryan Kearney wrote: > On 05/10/2017 05:05 AM, Lukas Zapletal wrote: >> >> Check out the new version I just pushed into the gist! I hope you will >> like it. > > What is the process to go from gist to in 1.16? > > -- bk > > > -- > 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.
Re: [foreman-dev] Performance analysis deep-dive, what would you like to hear about?
Thanks for doing this. Ideas: - Rails ActiveRecord SQL debugging (eager loading and N+1 problems - how to spot them) - how we configure passenger by default and what are the limitations - how passenger handles memory-leaked processes (it doesn't - see my script) - how to enable slow SQL logging on PostgreSQL - drop a word about foreman-trace perhaps - utilizing information from Satellite 6 performance tuning guide LLZ On Tue, May 9, 2017 at 4:49 PM, Christopher Duryee wrote: > > > On Tue, May 9, 2017 at 9:01 AM, wrote: >> >> Hey, I want to do a performance analysis deep-dive. >> >> What I had in mind: >> >> 1. Installation of tooling in development environment >> 2. Simple request breakdown (view, sql) >> 3. Debugging API request >> 4. Time graph (flamegraph) >> 5. Memory consumption >> 6. Installation in prod env >> 7. Analyzing POST requests >> >> Feel free to ask questions and suggest topics that you want me to cover. > > > This list looks good, thanks for covering it. Can you also add how to check > if a foreman instance is maxed out on passenger workers via > passenger-status? > >> >> >> Shim. >> >> -- >> 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. -- 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.
Re: [foreman-dev] Re: 1.15.0 release status
On 11/05/17 02:16, Daniel Lobato wrote: > Thanks, it seems like either I don't understand the combination filter > or it didn't work > (https://github.com/theforeman/foreman-infra/blob/cb03c58b7b2bf3b5c61a125e4c32841a07a6a274/puppet/modules/jenkins_job_builder/files/theforeman.org/yaml/jobs/release_test.yaml#L33) > > combination-filter: 'os == "el7" || os == "f24" || os == "jessie" || > (os == "stretch" && version != "1.14" && version != "1.15") || os == > "trusty" || os == "xenial"' It should have been using major_version, fixed. > http://ci.theforeman.org/job/release_push_deb/ doesn't have a > combination filter so it just publishes to the other 3 repos.(jessie > trusty and xenial). Fixed, added stretch. -- Dominic Cleal domi...@cleal.org -- 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.