Cisco Bug: CSCup93196 - EC: Cannot restart PCG source defintion, PCG Name doesn't show
Jun 23, 2020
- Headend System Releases
Known Affected Releases
Symptom: FOR 188.8.131.52 Cannot tear down PCG source definition. Nothing happens, except a information pop-up on the bottom left saying "For input string:" followed by the access criteria - screenshot attached. (This information pop-up also shows up when in page to edit the PCG source definition.) The source definition actually gets torn down. When going back into the source definition (edit page), the PCG Name dropdown list isn't populated, so this source definition cannot be restarted. It will need to be deleted. Once deleted, and rebuilt again (same information as before), it will cause a traceback error (screenshot attached). Steps to reproduce: - Start by using an EC that is a build before 184.108.40.206. - Create a PCG source definition. - Upgrade the EC to 220.127.116.11. - Go to the edit page of the PCG source definition created earlier. (No PCG Name is listed). - Attempt to tear down the PCG source definition. (Tears down successfully without letting you know, and pops-up an information in the UI, "For input string:" followed by the access criteria.) - Navigate away from the page, and go back to the edit page again for the PCG source definition. (PCG Name drop down isn't populated, so you can't start this source definition again). - Delete the source definition. - Recreate the source definition using the same information, and click "Save". (Traceback page is displayed). This issue is not present when creating PCG source definitions that have never been created before the upgrade. Example of this issue is on Vodultra: IP: 10.90.179.179 UI login: root / Public123 Command line login: root / generic Example of affected PCG source definition: Session ID: 0B:04:06:AE:16:51 21167 Access Criteria: 0B0406B7164F -------------------------------------------------------------------- FOR 18.104.22.168 When an active PCG session gets built before the upgrade, then is carried over to the upgrade in 22.214.171.124, it cannot be restarted after it has been torn down. Deleting the PCG session and rebuilding it will work fine from then on. Procedures to reproduce: - Build an active PCG source definition before the upgrade (in this case, it was built before 126.96.36.199). - Upgrade the EC to 188.8.131.52. - Tear down the PCG source definition and navigate away from the page. - Go back to the edit page for that PCG source definition. - The "PCG Name" drop down menu is empty, and cannot restart the PCG source definition. Work around is to delete the PCG source definition and rebuilt it. After it has been rebuilt, it will no longer have this issue. Affected EC is vodsters. Please see me (Son Tran) as I know which PCG source defs were made before the upgrade (before 184.108.40.206). These sessions have been there before 220.127.116.11, then upgraded to .12, and now .13. Conditions: When tearing down active PCG source defs that were built before the upgrade.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases