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

Director branches: Cloned host loses its corresponding services and service sets #2897

Closed
raviks789 opened this issue Jul 23, 2024 · 0 comments · Fixed by #2898
Closed

Director branches: Cloned host loses its corresponding services and service sets #2897

raviks789 opened this issue Jul 23, 2024 · 0 comments · Fixed by #2898
Assignees
Labels
Milestone

Comments

@raviks789
Copy link
Collaborator

raviks789 commented Jul 23, 2024

Steps to reproduce:

  1. Create a Director Branch called test
  2. Activate the Director Branch test
  3. Clone any host with services
  4. Navigate to single services -> You could see that the services are cloned but not associated with the cloned host

Currently the service sets are not visible in Director Branches. So to check whether the service sets are properly associated with the cloned host. Query the database and check the host column for the service set of type 'object', which should not be empty.

SELECT object_name, object_type, host FROM branched_icinga_service_set WHERE object_name = <service set name>;
@raviks789 raviks789 changed the title Director branches: Cloned host loses its services Director branches: Cloned host loses its services and service sets Jul 23, 2024
@raviks789 raviks789 changed the title Director branches: Cloned host loses its services and service sets Director branches: Cloned host loses the corresponding services and service sets Jul 23, 2024
@raviks789 raviks789 changed the title Director branches: Cloned host loses the corresponding services and service sets Director branches: Cloned host loses its corresponding services and service sets Jul 23, 2024
@raviks789 raviks789 self-assigned this Aug 5, 2024
@raviks789 raviks789 added the bug label Aug 5, 2024
@raviks789 raviks789 added this to the v1.11.2 milestone Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant