[foreman-dev] 1.17 Installation on Ubuntu 14.04 - Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status widget loading".. Never Completes

2017-10-11 Thread Lisa Kachold 
I have setup TheForeman 1.17.1-0 in a Development install on AWS.

ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux-gnu] (gem/bundler 
errors using other versions)
WEBrick 1.3.1
ALL Ports open from Server to my IP

I changed Rails to listen on all interfaces as:

require 'rails/commands/server'
module Rails
  class Server
alias :default_options_bk :default_options
def default_options
  default_options_bk.merge!(Host: '0.0.0.0')
end
  endend


Missing Dashboard Menu MouseOver Drop Downs && "Host Configuration Status 
widget loading".. Never Completes

Output from Log:

00:36:43 rails.1   | started with pid 19240

00:36:43 webpack.1 | started with pid 19241

00:36:45 webpack.1 | { [Error: ENOENT: no such file or directory, open 
'.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }

00:36:45 webpack.1 | Project is running at http://localhost:3808/

00:36:45 webpack.1 | webpack output is served from /webpack/

00:36:51 rails.1   | DEPRECATION WARNING: `config.serve_static_files` is 
deprecated and will be removed in Rails 5.1.

00:36:51 rails.1   | Please use `config.public_file_server.enabled` instead.

00:36:51 rails.1   |  (called from  at 
/root/foreman/config/application.rb:218)

00:36:51 rails.1   | => Booting WEBrick

00:36:51 rails.1   | => Rails 5.0.6 application starting in development on 
http://0.0.0.0:5000

00:36:51 rails.1   | => Run `rails server -h` for more startup options

00:36:51 rails.1   | 2017-10-12T00:36:51  [app] [W] DEPRECATION WARNING: 
ActiveRecord::Base.raise_in_transactional_callbacks= is deprecated, has no 
effect and will be removed without replacement. (called from  at /root/foreman/config/environment.rb:5)

00:36:55 rails.1   | The Apipie cache is turned off. Enable it and run 
apipie:cache rake task to speed up API calls.

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] WARNING: Pry will not 
work with foreman gem, use script/foreman-start-dev

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] DEPRECATION WARNING: 
before_filter is deprecated and will be removed in Rails 5.1. Use 
before_action instead. (called from  at 
/root/foreman/config/environment.rb:5)

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] DEPRECATION WARNING: 
after_filter is deprecated and will be removed in Rails 5.1. Use 
after_action instead. (called from  at 
/root/foreman/config/environment.rb:5)

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] DEPRECATION WARNING: 
before_filter is deprecated and will be removed in Rails 5.1. Use 
before_action instead. (called from  at 
/root/foreman/config/environment.rb:5)

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] DEPRECATION WARNING: 
after_filter is deprecated and will be removed in Rails 5.1. Use 
after_action instead. (called from  at 
/root/foreman/config/environment.rb:5)

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] DEPRECATION WARNING: 
alias_method_chain is deprecated. Please, use Module#prepend instead. From 
module, you can access the original method using super. (called from  at /root/foreman/config/environment.rb:5)

00:36:58 rails.1   | 2017-10-12T00:36:58  [app] [W] DEPRECATION WARNING: 
Using a dynamic :controller segment in a route is deprecated and will be 
removed in Rails 5.2. (called from block in  at 
/root/foreman/config/routes.rb:17)

00:36:59 rails.1   | [2017-10-12 00:36:59] INFO  WEBrick 1.3.1

00:36:59 rails.1   | [2017-10-12 00:36:59] INFO  ruby 2.4.2 (2017-09-14) 
[x86_64-linux-gnu]

00:36:59 rails.1   | [2017-10-12 00:36:59] INFO  WEBrick::HTTPServer#start: 
pid=19242 port=5000

00:37:08 webpack.1 | Hash: 1d1afa88f456ce25e96c

00:37:08 webpack.1 | Version: webpack 3.6.0

00:37:08 webpack.1 | Time: 22521ms

00:37:08 webpack.1 | Asset   Size  ChunksChunk 
Names

00:37:08 webpack.1 | bundle.js17.5 MB   0  [emitted]  [big]  
bundle

00:37:08 webpack.1 | vendor.js75.7 kB   1  [emitted] 
vendor

00:37:08 webpack.1 |bundle.css81.7 kB   0  [emitted] 
bundle

00:37:08 webpack.1 | manifest.json  153 bytes  [emitted] 

00:37:08 webpack.1 |   [55] ./webpack/assets/javascripts/foreman_tools.js 
4.22 kB {0} [built]

00:37:08 webpack.1 |  [322] multi 
(webpack)-dev-server/client?http://localhost:3808 webpack/hot/dev-server 
./webpack/assets/javascripts/bundle.js 52 bytes {0} [built]

00:37:08 webpack.1 |  [323] 
(webpack)-dev-server/client?http://localhost:3808 7.23 kB {0} [built]

00:37:08 webpack.1 |  [371] (webpack)/hot/dev-server.js 1.61 kB {0} [built]

00:37:08 webpack.1 |  [373] ./webpack/assets/javascripts/bundle.js 1.46 kB 
{0} [built]

00:37:08 webpack.1 |  [414] 
./node_modules/expose-loader?jstz!./node_modules/jstz/index.js 88 bytes {0} 
[built]

00:37:08 webpack.1 |  [420] 
./node_modules/expose-loader?JsDiff!./node_modules/diff/lib/index.js 94 
bytes {0} [built]

00:37:08 webpack.1 |  [431] ./webpack/assets/javascripts/bundle_flot.js 240 
bytes {0} [built]

00:37:08

Re: [foreman-dev] Redmine running slowly

2017-10-11 Thread Ohad Levy 
On Wed, Oct 11, 2017 at 7:39 PM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:

> On Wed, Oct 11, 2017 at 07:36:39PM +0300, Ohad Levy wrote:
>
>> On Oct 11, 2017 5:40 PM, "Greg Sutcliffe" 
>> wrote:
>>
>> Update on migration:
>>
>> http://51.15.192.166 is now live for your testing pleasure, with a copy
>>
>>
>> Any chance to update/enable https in the process?
>>
>
> That is the plan, but first we want to know it's working. If you can
> create DNS records we can already test the process with letsencrypt:
>
> redmine01.theforeman.org A 51.15.192.166
> redmine01.theforeman.org  2001:bc8:4400:2300::5:e03


both should be resolved.

Ohad

>
>
> Thanks!
>>
>> of the DB from a few days ago. Email is currently disabled, so you
>> can't spam anyone. There's still a few small tasks to sort out that
>> will keep me busy, but if you want to see if you can break it, go
>> ahead.
>>
>> Sadly, SMTP outbound is blocked by default on Scaleway, which I didn't
>> realise until about 20 mins ago. I've raised a ticket to lift this so
>> Redmine can send email, but until that's resolved we can't complete the
>> migration.
>>
>> Once email is confirmed working, we'll schedule a maintenance window,
>> where I will stop the Openshift instance and make a final DB dump. Ohad
>> will then do a DNS switch, and as soon as it comes back you should all
>> be good to go.
>>
>> Stay tuned for further updates. I'll announce the maintenance window
>> before I start.
>>
>
> --
> 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] Redmine running slowly

2017-10-11 Thread Ewoud Kohl van Wijngaarden 

On Wed, Oct 11, 2017 at 07:36:39PM +0300, Ohad Levy wrote:

On Oct 11, 2017 5:40 PM, "Greg Sutcliffe"  wrote:

Update on migration:

http://51.15.192.166 is now live for your testing pleasure, with a copy


Any chance to update/enable https in the process?


That is the plan, but first we want to know it's working. If you can 
create DNS records we can already test the process with letsencrypt:


redmine01.theforeman.org A 51.15.192.166
redmine01.theforeman.org  2001:bc8:4400:2300::5:e03


Thanks!

of the DB from a few days ago. Email is currently disabled, so you
can't spam anyone. There's still a few small tasks to sort out that
will keep me busy, but if you want to see if you can break it, go
ahead.

Sadly, SMTP outbound is blocked by default on Scaleway, which I didn't
realise until about 20 mins ago. I've raised a ticket to lift this so
Redmine can send email, but until that's resolved we can't complete the
migration.

Once email is confirmed working, we'll schedule a maintenance window,
where I will stop the Openshift instance and make a final DB dump. Ohad
will then do a DNS switch, and as soon as it comes back you should all
be good to go.

Stay tuned for further updates. I'll announce the maintenance window
before I start.


--
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] Redmine running slowly

2017-10-11 Thread Ohad Levy 
On Oct 11, 2017 5:40 PM, "Greg Sutcliffe"  wrote:

Update on migration:

http://51.15.192.166 is now live for your testing pleasure, with a copy


Any chance to update/enable https in the process?

Thanks!

of the DB from a few days ago. Email is currently disabled, so you
can't spam anyone. There's still a few small tasks to sort out that
will keep me busy, but if you want to see if you can break it, go
ahead.

Sadly, SMTP outbound is blocked by default on Scaleway, which I didn't
realise until about 20 mins ago. I've raised a ticket to lift this so
Redmine can send email, but until that's resolved we can't complete the
migration.

Once email is confirmed working, we'll schedule a maintenance window,
where I will stop the Openshift instance and make a final DB dump. Ohad
will then do a DNS switch, and as soon as it comes back you should all
be good to go.

Stay tuned for further updates. I'll announce the maintenance window
before I start.

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.

Re: [foreman-dev] Redmine running slowly

2017-10-11 Thread Greg Sutcliffe 
Update on migration:

http://51.15.192.166 is now live for your testing pleasure, with a copy
of the DB from a few days ago. Email is currently disabled, so you
can't spam anyone. There's still a few small tasks to sort out that
will keep me busy, but if you want to see if you can break it, go
ahead. 

Sadly, SMTP outbound is blocked by default on Scaleway, which I didn't
realise until about 20 mins ago. I've raised a ticket to lift this so
Redmine can send email, but until that's resolved we can't complete the
migration. 

Once email is confirmed working, we'll schedule a maintenance window,
where I will stop the Openshift instance and make a final DB dump. Ohad
will then do a DNS switch, and as soon as it comes back you should all
be good to go.

Stay tuned for further updates. I'll announce the maintenance window
before I start.

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: Bundler is unable to solve deps for fresh checkout

2017-10-11 Thread Lisa Kachold 
I had all these same issues in a 16.04 Ubuntu LTS (on AWS) with Ruby 2.1 
and 6.  

There were a few hurdles after the upgrade/downgrade to 2.4 also.  

I still have a JavaScript issue, as the pull downs don't render, so I am 
rerunning tests.

I have modified Foreman to listen on all ports.

I have my history file from my install if you want to contact me directly.

On Thursday, September 21, 2017 at 12:41:00 AM UTC-7, Lukas Zapletal wrote:
>
> I just upgraded, but I think putting Gemfile.lock (even an older one 
> from 1.14 stable branch) could work. Weird really. 
>
> On Wed, Sep 20, 2017 at 6:57 PM, Daniel Lobato  > wrote: 
> > http://ci.theforeman.org/view/Release%20pipeline/job/release_tarballs 
> > 
> > seems to have suffered from this today (Monday 1.15.4 tarballs were 
> built 
> > just fine) 
> > 
> > Did you find any other way to fix this? Switching to 2.4 could be an 
> option, 
> > probably 
> > putting a  Gemfile.lock on every tagged release isn't a bad idea either. 
> > 
> > On Thursday, September 14, 2017 at 3:13:29 PM UTC+2, Lukas Zapletal 
> wrote: 
> >> 
> >> Hey, 
> >> 
> >> when I do fresh foreman clone with clean Ruby version (tried 2.0.0 and 
> >> 2.4.1), bundle install is not able to resolve dependencies and loops 
> >> forever. I am using latest stable bundler, tried also pre1 version. 
> >> 
> >> Can someone confirm and provide a workaround? I think copying 
> >> Gemfile.lock from someone else should do it. Can someone attach a 
> >> pastebin me one? I currently have my workstation down (CPU in RMA) and 
> >> got clean setup. 
> >> 
> >> If this is confirmed, it is quite an issue for newcomers. The second 
> >> command new developer is asked to execute fails hard. Any suggestions? 
> >> 
> >> LZ 
> >> 
> >> -- 
> >> 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...@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] Redmine running slowly

2017-10-11 Thread Greg Sutcliffe 
Things are no better today, and I'm out of patience with Openshift.
I've spun up an instance on Scaleway that should be able to cope and am
in the process of creating a copy of Redmine there. Once it's ready
I'll stop Openshift, re-import the db and cut over the DNS.

Continue to use Redmine as normal for now, I'll update when we're ready
to do the final cutover.

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.

[foreman-dev] FOSDEM / CfgMgmtCamp 2018 - Call for Presentations!

2017-10-11 Thread Greg Sutcliffe 
Hi all,

It's that time of year again - the call for presentations for our
yearly conference season is now open!

FOSDEM - https://penta.fosdem.org/submission/FOSDEM18
CfgmgmtCamp - http://cfgmgmtcamp.eu/#cfp

This year is the 5th CfgMgmtCamp, and we want to make it the best yet.
So in addition to the usual developer updates, new plugins, and
community news talks, I'm very keen to hear from *users* - that's you!

Submit your success stories (or horror stories!), things you learned in
the trenches, or interesting ways you've put Foreman to use, and we'll
make sure that the users get a voice in this years Foreman track.

See you there!
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] Redmine running slowly

2017-10-11 Thread Lukas Zapletal 
Thanks guys for doing this.

If things go terribly wrong, we still have an account on EC2 where we
run our koji.

On Tue, Oct 10, 2017 at 9:21 PM, Greg Sutcliffe
 wrote:
> On Tue, 2017-10-10 at 10:50 -0400, Andrew Kofink wrote:
>> Me as well. It's quite difficult to work this way.
>
> Yeah, I know :(
>
> Openshift aren't saying much other than that this is mainly due to the
> number of people that decided to upgrade to Silver Tier to avoid the
> sunset of v2. That's putting a lot of load on the v2 cluster, which
> obviously is hitting us.
>
> As Ewoud said, we've made a change today in how we process the
> underlying cron jobs that should reduce the amount of IO we were doing
> - if there's any kind of quota-ing going on, that should help. We're
> seeing that bring the time taken to run the cron down to about 10mins
> (starting at the top of the hour). That should improve things during
> that period. Sadly I did make a mistake during a manual part of the
> changes that impacted the DB, but that should be resolved now.
>
> Base load now seems to be down to around 7-9 which is better but still
> too high. Sadly the v3 resources are unlikely to be available before
> November, which is a limiter. If things are not better in the next day
> or two, then on Thu or Fri I may migrate it to our Scaleway account
> anyway, as we have capacity there, although I'd rather not migrate
> twice...
>
> 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.



-- 
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.