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 were resolved between releases 23.3 and 23.4.

Resolved Issues in Juniper Cloud-Native Router Release 23.4

  • JCNR-4070: Core path not updated as per values.yaml—Previously, the core path was not updated as defined under the corePattern attribute in values.yaml file. It was necessary to define the core_pattern value on the host before deploying JCNR. This issue is now resolved. The core_pattern is now derived from the values.yaml file.

  • JCNR-4950: Notification for "Config Failure, Config OK, JCNR CLI Start, JCNR CLI Stop" are not triggering—Previously, the following JCNR notifications were not shown when triggered:

    • Config Failure—is triggered if there is a failure while providing custom configuration during JCNR deployment.

    • Config OK—is triggered while providing custom configuration during JCNR deployment.

    • JCNR CLI Start—is triggered when running cli in the cRPD shell.

    • JCNR CLI Stop—is triggered while exiting the CLI mode after entering exit in the cRPD shell.