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.

Sign up for GitHub

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

Jump to bottom

During upgrades, Plugins may be falsely reported as incompatible #5495

Closed
TheWitness opened this issue Sep 23, 2023 · 1 comment
Closed

During upgrades, Plugins may be falsely reported as incompatible #5495

TheWitness opened this issue Sep 23, 2023 · 1 comment
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Milestone
1.2.26

Comments

@TheWitness
Copy link
Member

Describe the bug

This is an edge case, but say for example you are upgrading a Cacti schema that may have multiple plugins installed, and the Cacti install that you are installing against, does not have any of these plugins present. In that case, Cacti generates a false log message as shown in the image below. This error message should be corrected.

image

To Reproduce

See the steps above.

Expected behavior

Cacti should generate and error and disable the plugin, but the error should be accurate.
@TheWitness TheWitness added bug Undesired behaviour confirmed Bug is confirm by dev team labels Sep 23, 2023
@TheWitness TheWitness added this to the 1.2.26 milestone Sep 23, 2023
TheWitness added a commit that referenced this issue Sep 23, 2023
@TheWitness
Fixing #5495 - Upgrade language inacurate
30d7cc6 
Upon upgrade, cacti falsely assumes that a plugin is not compatible, when it could simply not be present
@TheWitness TheWitness added the resolved A fixed issue label Sep 23, 2023
@TheWitness
Copy link
Member Author

Discovered verifying this bug.

#5482

TheWitness added a commit that referenced this issue Sep 23, 2023
@TheWitness
Fixing #5495 - Upgrade language inacurate
236d1ab 
Upon upgrade, cacti falsely assumes that a plugin is not compatible, when it could simply not be present
@netniV netniV changed the title Upon upgrade, cacti falsely assumes that a plugin is not compatible, when it could simply not be present During upgrades, Plugins may be falsely reported as incompatible Dec 16, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Mar 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Projects
None yet
Milestone
1.2.26
Development

No branches or pull requests
1 participant
@TheWitness