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

Rebuild your new Yum repository after changing the packages

-
If you have done any  changes  to your local  repository  packages, adding new ones or deleting some, you can just simply update your yum sqlite metadata database for your changes to take effect, rather than creating the whole repository again which takes time if you have  thousands  of packages in your repository.  Here is how we rebuild our yum repository. 1. After you are done with adding/removing packages to your local repo, then: # createrepo --update /path/to/repo_dir 2. On the  client  side, you need to clean up the cached yum meta data in order to see the changes after repo rebuild: # yum clean all 3. Now update the  client  yum cache  # yum update
Read more

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

Linux and AIX user non expiry and force password change at first login

-
In Linux, if you want to set the password for an account to never expire, here is the command: # chage -I -1 -m 0 -M 99999 -E -1 username  And to force a user to change his password upon first login: # chage -d0 username Current status of the account can be checked via chage command : # chage -l username  Last password change                                    : Jun 18, 2013 Password expires                                        : never Password inactive                                       : never Account expires                                         : never Minimum number of days between password change          : 0 Maximum number of days between password change          : 99999 Number of days of warning before password expires       : 7 For AIX, to set the password to non expiry and force the user to change his password upon first login: # chuser expires=0 maxage=0 username  To check the username status in AIX: # lsuser -f username
Read more