Bug #10209
closed
Canceling Status - Monitoring - Add View results in duplicate Default Views which can't be deleted
0%
Description
Canceling Status - Monitoring - Add View results in duplicate Default Views which can't be deleted:
Result is the following:
And none of those duplicate defaults can be deleted again, the following error is displayed: "Can't remove default view."
Also seem to happen if you click OK without entering av View name.
Updated by Fabián Burbano over 4 years ago
mastr boy wrote:
Canceling Status - Monitoring - Add View results in duplicate Default Views which can't be deleted:
I tried it ... To my misfortune hahhahahahahhahha
Also, if a view with a name is added and then deleted, when you add the view with the same name again, it is not created ... And no error message appears.
The solution, not very elegant, is to reverse the configuration.
Definitely here there is a code to debug
Updated by Jim Pingle over 4 years ago
- Project changed from pfSense to pfSense Packages
- Category set to Status_Monitoring
- Status changed from New to Duplicate
Duplicate of #9679
Updated by Fabián Burbano over 4 years ago
I ask:
If it is marked as a duplicate of a resolved bug, is this bug considered resolved?
It is definitely not resolved. It is an uncorrected feature in Bug #9679. As Jim Pingle wrote:
"The title case isn't related to this problem, but if you want to open a separate issue to investigate that, we can look into it."
Updated by Jim Pingle over 4 years ago
The duplicate and case issues are both resolved in the current version of the status monitoring code (there are separate issues out there for these and more similar variations). It's fixed on 2.4.5 and 2.5.0 snapshots, and you can also get the fixes by updating the status monitoring package at the CLI. Post on the forum if you need help, but there are no bugs like this left in the repository to fix.
Updated by Fabián Burbano over 4 years ago
I just tried it with the command: pkg upgrade -y pfSense-Status_Monitoring
Then the most elegant temporary solution is to execute the command in the console.
Updated from version pfSense-Status_Monitoring: 1.7.7 -> 1.7.11_1 [pfSense]
It is definitely absolutely fixed
Thanks for the info
Updated by mastr boy over 4 years ago
Jim Pingle wrote:
The duplicate and case issues are both resolved in the current version of the status monitoring code (there are separate issues out there for these and more similar variations). It's fixed on 2.4.5 and 2.5.0 snapshots, and you can also get the fixes by updating the status monitoring package at the CLI. Post on the forum if you need help, but there are no bugs like this left in the repository to fix.
I can also confirm that a working workaround is running "pkg upgrade -y pfSense-Status_Monitoring" in the cli.