Foreman bug Warning Infinity

-
Yet another bug in newly installed Foreman,

While browsing diffrent parts of foreman gui, I get this error:

We're sorry, but something went wrong!

Warning!
Infinity

And in the logs:

# cat /var/log/foreman/production.log
Started GET "/hosts?search=last_report+%3E+%225+minutes+ago%22+and+status.enabled+%3D+true+and+status.applied+%3D+0+and+status.failed+%3D+0+and+status.pending+%3D+0" for 10.8.204.208 at 2015-06-26 14:53:12 +0200
2015-06-26 14:53:12 [I] Processing by HostsController#index as HTML
2015-06-26 14:53:12 [I]   Parameters: {"search"=>"last_report > \"5 minutes ago\" and status.enabled = true and status.applied = 0 and status.failed = 0 and status.pending = 0"}
2015-06-26 14:53:12 [I]   Rendered hosts/_list.html.erb (8.9ms)
2015-06-26 14:53:12 [I]   Rendered hosts/index.html.erb within layouts/application (12.8ms)
2015-06-26 14:53:12 [W] Operation FAILED: Infinity
2015-06-26 14:53:12 [I]   Rendered common/500.html.erb within layouts/application (4.1ms)
2015-06-26 14:53:12 [I]   Rendered layouts/base.html.erb (1.1ms)
2015-06-26 14:53:12 [I] Completed 500 Internal Server Error in 35ms (Views: 6.1ms | ActiveRecord: 0.0ms)


To solve this issue, the value for entries_per_page need to be set to a non 0 value:

Administer > Settings > General > entries_per_page 0 -> 20





Comments

Post a Comment

Popular posts from this blog

Running Docker Wildfly/JBoss Application Server in Debug mode via Eclipse

-
I have recently built the whole Development Environment of Java Enterprise Edition (J2EE) project on multiple Docker containers. It has saved the hassle of setting up a dev env for new developers. All it takes to setup the environment is to clone our github repositories and run the Docker images. I will explain the setup in a future post. Build Wildfly Docker Image with Debugging Enabled So basically in order to run the Wildfly in debug mode, we need to add --debug  flag to the Wildfly standalone.sh  startup script. Also we need to expose port 8787  in our image as it's the default port for Wildfly JVM debug mode. 1. Create or change your Wildfly Dockerfile as follows: $ cat Dockerfile FROM jboss/wildfly: 10.0 . 0 .Final EXPOSE 8787 CMD [ "/opt/jboss/wildfly/bin/standalone.sh" , "-b" , "0.0.0.0" , "-bmanagement" , "0.0.0.0" , "--debug" ] 2. Build and tag the image: $ docker build -t wildfly-debug . 3.
Read more

Building RPM OpenSSH 7.1p1 on RHEL/CentOS 6.5

-
After I've implemented the OpenVAS vulnerability assessment system, I've made a complete vulnerability testing on the environment for both Linux and Wintel servers. The result for the all Linux servers were Red :) Severity 10.0(High). The reason was the OpenSSH version 5. Test result: High  (CVSS: 8.5) NVT: OpenSSH Multiple Vulnerabilities (OID: 1.3.6.1.4.1.25623.1.0.806052) Product detection result: cpe:/a:openbsd:openssh:5.3 by SSH Server type and version (OID: 1.3.6.1.4.1.25623.1.0.10267) Summary This host is running OpenSSH and is prone to multiple vulnerabilities. Vulnerability Detection Result Installed version: 5.3 Fixed version: 7.0 Impact Successful exploitation will allow an attacker to gain privileges, to conduct impersonation attacks, to conduct brute-force attacks or cause a denial of service. Impact Level: Application Solution Upgrade to OpenSSH 7.0 or later. For updates refer to http://www.openssh.com Affected Software/OS OpenSSH vers
Read more