06-24-2022 02:49 AM
Wouldn't it be nice if the Developer actually fixed this bug, instead of having customers opening TAC cases after each and every upgrade and servicepack-installation?
A permanent fix is fairly easy to apply
- make sure that the newly added "printeradmin user" is removed from Linux
- and apply the old user/Group id on the chrony.
- This cant be soo hardto create a script to verify this settings and change them where nessessary.
Curently tac fixes the problem by utilizing Root access to the affected node.creating a new UID for chrony, starts the daemon and this works untill next upate/Patch is done on the node.
It's is mine expectations only or is it in general really annoying how "sloppy" the bugfixes are handeled..
11-22-2022 02:31 AM - edited 11-22-2022 03:32 AM
Hi jsteffensen
We are facing the same issue after updating ISE 3.0p4 > 3.0p6
It is completely incapable to have to open a new TAC case every time.
It is time consuming and costs money for something that should be fixed for good.
Or we can bill Cisco directly for the time spent to have to implement the fix again.
03-21-2023 11:10 PM
We have this problem too, after upgrading from 2.6 to 2.7 patch 9 ... any workaround or any know the steps ?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide