-
Notifications
You must be signed in to change notification settings - Fork 571
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
Host doesn't visible in UI after creating using API #6927
Labels
Comments
6 tasks
Thanks for the report. We have a combined tracking issue #6012 for this, since this isn't the first issue about this problem. Closing therefore. |
This was referenced Feb 5, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
Situation from subject happens time to time only.
I'm not able to exactly reproduce it but usual scenario is following:
Both actions finish successfully but host isn't displayed in UI.
A configuration file for affected host is created in /var/lib/icinga2/api/packages/_api/xxx/conf.d/hosts.
Just for example this is configuration for host which is actually missing in UI:
and also I'm able to see information about the host using API:
Once the icinga is reloaded host is visible in UI.
Expected Behavior
See the host in UI without reload.
Context
We have started using API for adding hosts to icinga because the old solution (using classic configuration files) required reload of icinga which in our setup caused issues.
Your Environment
icinga2 --version
):Operating System and version:
CentOS Linux release 7.5.1804 (Core) - more details above in System information:
Enabled features (
icinga2 feature list
):icinga2 daemon -C
):For better readability I have removed 445 lines containing warning/ApplyRule.
The important thing is that it says:
[2019-01-31 17:03:54 +0100] information/ConfigItem: Instantiated 9 Hosts.
While in UI is only 8 hosts visible.
icinga2 object list --type Endpoint
icinga2 object list --type Zone
The text was updated successfully, but these errors were encountered: