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

When reindexing, a Data Source that could be un-orphaned may not always be unorphaned #5381

Closed
TheWitness opened this issue Jun 19, 2023 · 0 comments
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team porting required Requires porting to develop resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

I've found that if I manually set a Data Source to orphaned, there is no way to get it out of orphan status again.

Expected behavior

Cacti should catch this case and act accordingly.

@TheWitness TheWitness added bug Undesired behaviour confirmed Bug is confirm by dev team labels Jun 19, 2023
@TheWitness TheWitness added this to the v1.2.25 milestone Jun 19, 2023
TheWitness added a commit that referenced this issue Jun 19, 2023
* Orphaned Data Source Link not Working
* Once a Data Source is orphaned there are cases where it will not become un-orphaned upon reindex
TheWitness added a commit that referenced this issue Jun 19, 2023
* Orphaned Data Source Link not Working
* Once a Data Source is orphaned there are cases where it will not become un-orphaned upon reindex
@TheWitness TheWitness added resolved A fixed issue porting required Requires porting to develop labels Jun 19, 2023
@netniV netniV changed the title Once a Data Source is orphaned there are cases where it will not become un-orphaned upon reindex When reindexing, a Data Source that could be un-orphaned may not always be unorphaned Sep 3, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Dec 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team porting required Requires porting to develop resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant