Icinga Web 1.6.1 Released

As the core team released 1.6.1, so do we. Download Icinga Web 1.6.1 on Sourceforge now. This release fixes many database related issues and in particular, resolves a authorisation dispatcher bug that hindered the import user function – cheers to user gpduck for the patch!
We also managed to slip in a new feature that should make many AD and LDAP users happy: Groups can now inherit attributes bottom-up, as well as top-down.

  • JS fixes
  • Fixes for counts in views #2192 #2164
  • Translation fixes #2163 #2148
  • UI fixes #2162
  • Database fixes for oracle
  • Doctrine DB manager connection fixes
  • Doctrine count queries
  • Performance for TO’s and permission data
  • Portal cronk JS only cronk
  • Group manager inheritance tree and selection fix
  • Empty field fixes (removed caching)
  • Auth dispatcher fix #2142
  • Doctrine connection based prefix bug fix
  • Oracle error prone order statements


  • Choice of group inheritance model #2188

Thanks to all who have reported bugs and patches, we appreciate your patience in the lead up to this release. Please keep in touch on the development tracker if any more issues arise and hop onto our user mailing list, IRC channel or the Icinga-Portal.org for help.

How to use Icinga bug report (redmine)

If you have been looking closely at the icinga front page you would have noticed a new button link on the right hand side of the site called “Report a Bug” below is what we are talking about…
As the code for Icinga is a continuous work in progress there is bound to be the occasion where you will encounter a bug! Now instead of just leaving this and assuming that the matter will just be resolved in the next release it’s best to open a bug report against what ever you find.
If you haven’t already done so, you will need to create an account, to do this you need to click on the Development drop down menu at the top of the Icinga website, then on Register for Icinga

You will then need to complete the form to create your account…

Once your account has been created you will be E-mailed an code that will enable you to the use the login …

Now that you have your account and you have logged in you will need to select the project that you wish to report against, to do this simply click on the projects link at the top of the page …

You will now have the option to select the current projects …

Now that you have selected the sub project (in this image it’s the Core) you now raise your bug by clicking on the “New Issue”

From here is where you will fill in all the details you can about the problem you have …

You can at any point click on “preview”, to review your work …

Once you are satisfied you have included all that you can to best describe the situation, then remember to click on “Create” you will then be redirected to the newly created bug report…

If you missed something don’t worry you can simply click on “Update” and add further information. remembering to click on “Submit” to add the update!