Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Resolved Issues

This section provides information about issues that we resolved between release 23.1 and 23.2.

Resolved Issues in Juniper Cloud-Native Router Release 23.2

  • JCNR-3541: core-facing on access interface is not removing the interface from no local switching—Previously, when an access interface with the no-local-switching key enabled was configured to core-facing, then the no-local-switching functionality continued to be enabled on the access interface. This issue is resolved.

  • JCNR-3595: vf_isolated remains true for access interface even after deleting no-local-switching from BD after vRouter restart—Previously, in a workload access interface with no-local-switching enabled for the bridge domain, after the vRouter was restarted and no-local-swithing functionality was removed from cRPD, the access interface would continue to have the no-local-switching key enabled. This issue is resolved.

  • JCNR-3600: Redundant syslog ng container on helm upgrade—Previously, after a helm upgrade, the newly created syslogng pod continued to be in pending state. This issue is resolved.

  • JCNR-3652: Agent pod missing "ss" causing the below Error in agent logs—Previously, the following error was visible in the contrail-vrouter-agent.log file. This issue is resolved.