[TRNSPRTPCE-456] Maint-signal for 400G provisioning Created: 10/May/21 Updated: 23/Feb/22 Resolved: 23/Feb/22 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Phosphorus |
| Type: | Bug | Priority: | High |
| Reporter: | Balagangadhar Bathula | Assignee: | Balagangadhar Bathula |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0 minutes | ||
| Time Spent: | 1 day, 4 hours | ||
| Original Estimate: | Not Specified | ||
| Description |
|
For honeynodes, even when maint-signal enable is set false, it is requiring a child object (testPattern) to be set. However in for devices in lab it error-out saying that testPattern should be provided, only when the test-signal is true. YANG model "when" statement in the NE throws an error. By distinguishing honeynode and other NEs, we can temporarily fix the problem, until we find the root-cause. |
| Comments |
| Comment by Balagangadhar Bathula [ 05/Jan/22 ] |
|
This issue still persists in the lab. As a solution can we disable the maint-testsignal? Please note that maint-testsignal is only enabled when the admin-state is set to maintenance. gthouenon any issue if we completely remove the maint-testsignal object in the renderer? Would honeynode work in such case? |
| Comment by Gilles Thouenon [ 06/Jan/22 ] |
|
Actually, I vaguely remember an issue with honeynode, but on the other hand, I see that your change successfully passes the gate with the 400G end2end functional test activated, and where we configure 400G interfaces on honeynode which is in version 7.1. So, a priori, this modification does not disturb so much honeynode, at least not for the moment. So, I am ok with this proposal. |