Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error during opening a navigation root item #5177

Closed
stevie-sy opened this issue Jan 25, 2024 · 1 comment · Fixed by #5185
Closed

Error during opening a navigation root item #5177

stevie-sy opened this issue Jan 25, 2024 · 1 comment · Fixed by #5185
Assignees
Labels
area/navigation Affects the navigation bug Something isn't working ref/NC
Milestone

Comments

@stevie-sy
Copy link

stevie-sy commented Jan 25, 2024

We did a big Upgrade from our environment:

  • Icinga (2.13.8 -> 2.14.2),
  • Icingaweb2 (2.11.4 -> 2.12.1)
  • moved to icingadb.

After this, we recognized, that we got an error clicking on an navigation item, created in the "navigation"-tab in the user account menu.

image

The root menu item is created like this:
image

and under this we created some custom views like this (a view with critical update service checks):
image

While the views works perfectly as usal, the root menu entry throws the error from above. A little workarround - so that colleagues are not shocked by the error message - is to write some nonsense into the url field.
image
So they only get a small message like "page not found".
image

These are the items in navigation.ini

[IT Custom Views]
type = "menu-item"
target = "_main"
users = "*"
groups = "*"
owner = "xxx"

[Critical Server Updatestatus (Liste)]
type = "menu-item"
parent = "IT Custom Views"
target = "_main"
url = "icingadb/services?(service.state.soft_state=2&host.vars.Verwalter~ST%2A)&(service.name_ci~%2Aupdatestatus%2A|service.name_ci~%2Aserverupdate%2A)&sort=host.display_name&columns=service.state.soft_state%2Cservice.state.last_state_change%2Cservice.icon_image.icon_image%2Cservice.display_name%2Cservice.host.display_name%2Cservice.state.output%2Cservice.state.performance_data%2Cservice.state.is_problem%2Chost.vars.verwalter&limit=100"
owner = "xxx"

Funny thing besides:
Doing this with an own module, you get a list with the child navigation object - like it should and it worked also before.
image

Your Environment

Include as many relevant details about the environment you experienced the problem in

  • Icinga Web 2 version and modules (System - About): 2.12.1
  • Web browser used: Firefox, Edge
  • Icinga 2 version used (icinga2 --version): 2.14.1
  • PHP version used (php --version): 8.0.3
  • Server operating system and version: RHEL9.3
@christoph2497
Copy link

ref/NC/806421

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/navigation Affects the navigation bug Something isn't working ref/NC
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants