4 Resolved and Known Bugs
This chapter lists the resolved and known bugs for Oracle Communications Cloud Native Core release 3.26.1.2xx.0.
These lists are distributed to customers with a new software release at the time of General Availability (GA) and are updated for each maintenance release.
4.1 Severity Definitions
Service requests for supported Oracle programs may be submitted by you online through Oracle’s web-based customer support systems or by telephone. The service request severity level is selected by you and Oracle and should be based on the severity definitions specified below.
Severity 1
- Data corrupted.
- A critical documented function is not available.
- System hangs indefinitely, causing unacceptable or indefinite delays for resources or response.
- System crashes, and crashes repeatedly after restart attempts.
Reasonable efforts will be made to respond to Severity 1 service requests within one hour. For response efforts associated with Oracle Communications Network Software Premier Support and Oracle Communications Network Software Support & Sustaining Support, please see the Oracle Communications Network Premier & Sustaining Support and Oracle Communications Network Software Support & Sustaining Support sections above.
Except as otherwise specified, Oracle provides 24 hour support for Severity 1 service requests for supported programs (OSS will work 24x7 until the issue is resolved) when you remain actively engaged with OSS working toward resolution of your Severity 1 service request. You must provide OSS with a contact during this 24x7 period, either on site or by phone, to assist with data gathering, testing, and applying fixes. You are requested to propose this severity classification with great care, so that valid Severity 1 situations obtain the necessary resource allocation from Oracle.
Severity 2
You experience a severe loss of service. Important features are unavailable with no acceptable workaround; however, operations can continue in a restricted fashion.
Severity 3
You experience a minor loss of service. The impact is an inconvenience, which may require a workaround to restore functionality.
Severity 4
You request information, an enhancement, or documentation clarification regarding your software but there is no impact on the operation of the software. You experience no loss of service. The result does not impede the operation of a system.
4.2 Resolved Bug List
The following Resolved Bugs tables list the bugs that are resolved in Oracle Communications Cloud Native Core Release 3.26.1.2xx.0.
4.2.1 ATS Resolved Bugs
Release 26.1.201
Table 4-1 ATS 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39176624 | ATS UI login fails after scaling up ATS pod due to Jenkins users mismatch when PVC is enabled | ATS GUI login failed after scaling up ATS pod due to Jenkins users mismatch when PVC was enabled (users directory symlink points into jobs).
Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39004260 | ATS API endpoint is not working with IPv6 or Dualstack environment | When ATS was deployed with IPv6 or dualstack deployment mode, ATS API endpoint was unreachable.
Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
Note:
Resolved bugs from 25.2.200 have been forward ported to 26.1.201.4.2.2 BSF Resolved Bugs
Release 26.1.201
Table 4-2 BSF 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 39557457 | NF discovery failed when PCF priority was not defined | NF discovery failed with a NullPointerException when the NRF profile did not define a priority value for PCF. This disrupted discovery processing for profiles that omitted the priority field.
Doc Impact: No Doc Impact. |
3 | 25.1.200 |
| 38830387 | Alternate routing did not occur during PCF shutdown | When a PCF was in controlled shutdown and its Diameter pod was scaled down, BSF did not attempt the configured alternate route.
Doc Impact: No Doc Impact. |
2 | 25.1.200 |
| 38962335 | Log event metric was unavailable after upgrade | After an in-service BSF upgrade, the log4j2_events_total metric was unavailable from the monitoring service although it was available from the pod actuator endpoint. This prevented expected log event monitoring through Prometheus or Grafana.
Doc Impact: No Doc Impact. |
2 | 25.2.200 |
| 38909575 | BSF ingress gateway pod protection did not enable | BSF ingress gateway pod protection did not enable in release 25.1.203, and the expected pod-protection behavior was unavailable for BSF ingress gateway.
Doc Impact: No Doc Impact. |
3 | 25.1.202 |
| 38953320 | NRF Agent configuration import did not update the configuration | The NRF Agent configuration import REST API returned success for action=Create without updating the configuration, misleading users that imported configuration was applied.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 38958909 | Replication failed during new-site addition | Replication failed while a site was upgraded during new-site addition. This disrupted site-addition or upgrade workflows that depended on successful replication.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 39202393 | Egress Diameter monitoring metrics failed | Egress Diameter traffic monitoring metrics failed on some Diameter Gateway pods because meshMap entries were corrupted, reducing visibility into Diameter traffic across the affected pods.
Doc Impact: No Doc Impact. |
3 | 25.2.102 |
| 39225155 | Common Services REST specification contained an incorrect resource URI | The Common Services REST specification contained an incorrect resource URI for BSF/PCF.
Doc Impact: The Error Code section in Oracle Communications Cloud Native Core, Binding Support Function REST Specification Guide was updated with the correct resource URI. |
3 | 25.1.201 |
| 38065064 | Correlation-information header metric did not update | The ocbsf_correlation_info_header_received metric did not update when requests included the 3gpp-sbi-correlation-info header.
Doc Impact: No Doc Impact. |
3 | 25.1.200 |
| 38305515 | Warnings appeared during BSF lifecycle operations | Helm warnings appeared during BSF installation, uninstallation, or upgrade on a cluster.
Doc Impact: No Doc Impact. |
3 | 25.2.100 |
| 38986750 | Message Profile creation failed with filter conditions | The REST API could not create a Message Profile when messageProfileFilterConditions was specified.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 39003985 | Configuration export omitted screens | CM-UI export omitted some configuration screens though they were present in the UI.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 39068631 | BSF management reported database lock-wait timeouts | BSF management frequently reported database lock-wait timeout errors.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 39066970 | BSF Management Service returned an incorrect error response | BSF Management Service returned HTTP 500 for requests that should have returned a method-not-allowed response.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 39096764 | Egress Gateway did not generate an alert for DNS SRV resolution failures | Egress Gateway did not generate the expected alert when DNS SRV resolution failed.
Doc Impact: No Doc Impact. |
3 | 25.1.100 |
| 39407313 | Database pod restarted during high traffic | The ndbmysqld pod restarted during an overnight 63K TPS traffic run.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 38735372 | Data became inconsistent after rollback | Data became inconsistent after rollback was completed.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 38913231 | BSF chart contained an unused parameter | The BSF Helm chart contained an unused isIpv6Enabled parameter.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 38751933 | BSF Management and Query Service restart failed | Restarting the BSF Management and Query Service deployment failed with a duplicate port definition error.
Doc Impact: No Doc Impact. |
3 | 24.2.2 |
| 38962235 | Ephemeral-storage settings were not applied | BSF service ephemeral-storage requests and limits were not reflected in the deployed configuration, causing cluster resource-policy violations.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 38726956 | SCP alerts continued after monitoring was disabled | SCP alerts continued even after the SCP Monitoring feature was disabled.
Doc Impact: No Doc Impact. |
3 | 25.1.200 |
| 38834313 | BSF management-service logs contained date-time parsing errors | BSF management-service pod logs contained DateTimeParseException errors.
Doc Impact: No Doc Impact. |
3 | 25.1.100 |
| 39096491 | BSF custom YAML files contained obsolete references | BSF custom YAML files contained obsolete references to timerSvc and database tables.
Doc Impact: No Doc Impact. |
3 | 25.1.200 |
| 39326592 | BSF upgrade failed during the pre-upgrade hook | The BSF upgrade failed during the pre-upgrade hook phase when upgrading to 25.2.200.
Doc Impact: No Doc Impact. |
3 | 25.2.200 |
| 39472592 | BSF operational-state change failed in the CNCC GUI | Changing the BSF operational state from controlled shutdown in the CNCC GUI returned an “Unable to switch the operational state” error.
Doc Impact: No Doc Impact. |
3 | 25.2.100 |
4.2.3 cnDBTier Resolved Bugs
Release 26.1.202
Table 4-3 cnDBTier 26.1.202 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39877744 | Upgrade to from 25.2.201 to 26.1.201 has failed - Pre-upgrade hooks unable to start container process | The pre-upgrade hook could select the Istio proxy instead of the db-monitor-svc container, causing the replication-health check and upgrade to fail.
Doc Impact: There is no documentation impact. |
2 | 26.1.201 |
| 39789596 | DBTier 25.1.201-4 ndbmysqld pods PVC utilization levels between 85% and 90% | After upgrade, ndbmysqld pod PVC utilization could remain between 85% and 90%.
Doc Impact: There is no documentation impact. |
2 | 25.1.201 |
| 39795366 | Incorrect version field in OpenAPI json -26.1.201 | The 26.1.201 OpenAPI validation files incorrectly identified the release version as 26.1.200.
Doc Impact: There is no documentation impact. |
3 | 26.1.201 |
| 39825041 | SLF dbtier 25.2.102 db-replication-svc container not coming up | On a fresh 25.2.102 installation, the replication-service container could fail its readiness probe and not start until the pod was restarted.
Doc Impact: There is no documentation impact. |
3 | 25.2.102 |
| 39803277 | Missing documentation for Replication Service Hostname Assignment API | The OpenAPI specification included a replication-service hostname-assignment operation that was not documented. The obsolete API was removed from the specification.
Doc Impact: There is no documentation impact. |
3 | 26.1.201 |
| 39724791 | cnDBTier-26.1.200-New Parameters Missing for ndbRestoreOptions in Documentation and Confluence Pages | Documentation did not describe ndbRestoreOptions.restoreData.useHint and ndbRestoreOptions.restoreData.readSize.
Doc Impact: Added the new parameters in the section "Global parameters". For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide |
4 | 26.1.200 |
Release 26.1.201
Table 4-4 cnDBTier 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 38982059 | Binlog injector thread stall causes epoch not to advance |
Binlog injector thread stall caused epoch not to advance. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
2 | 23.4.6 |
| 38998915 | Replication pod restart could not resolve SSL connection failure on HTTPS-enabled setup |
Replication pod restart could not resolve SSL connection failure on HTTPS-enabled setup. Replication and recovery were updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39090731 | dbtreplmgr reports success without checking replication status |
Dbtreplmgr reported success without checking replication status. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39090743 | NDB pods fail to reach ready state when network policy is enabled on OpenShift |
NDB pods failed to reach ready state when network policy was enabled on OpenShift. Deployment handling was updated for the affected OpenShift configuration. Doc Impact: There is no documentation impact. |
2 | 25.2.201 |
| 39149707 | dbtrecover script does not run after phase 0 |
Dbtrecover script did not run after phase 0. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
2 | 25.2.102 |
| 39166090 | dbtrecovery script does not work with ASM external setup |
Dbtrecovery script did not work with ASM external setup. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39239385 | Replication breaks when password encryption key is modified |
Replication broke when password encryption key was modified. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39245979 | dbttriage fails at startup because bundled dbtcommon module is missing |
Dbttriage failed at startup because bundled dbtcommon module was missing. The affected utility was updated to validate prerequisites, handle startup conditions, and report its result accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39246174 | dbtaudit fails because a core Python module is missing |
Dbtaudit failed because a core Python module was missing. The affected utility was updated to validate prerequisites, handle startup conditions, and report its result accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39249317 | New transporter metrics missing and db-monitor-svc logs continuous errors
|
New transporter metrics were missing, and Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39257872 | Event Details API returns duplicate events and misses unique events across pages |
Event Details API returned duplicate events and missed unique events across pages. API processing was updated so it returned consistent results and validated the required state. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39260249 | Unsafe scan of ndbinfo.transporters during node restart |
An unsafe scan of ndbinfo.transporters occurred during node restart. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
2 | 24.2.6 |
| 39272197 | Improve dbtaudit, dbttriage, and dbtfastrecover startup handling for TMPDIR |
Startup handling was incomplete for dbtaudit, dbttriage, and dbtfastrecover startup handling for TMPDIR. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39303878 | dbtfastrecover reports success despite partial replication |
Dbtfastrecover reported success despite partial replication. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39307465 | Valid checkpoints are missing in Auto GRR update APIs |
Valid checkpoints were missing in Auto GRR update APIs. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39308966 | GRR stuck in RECONFIGURE state |
GRR became stuck in RECONFIGURE state. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39315201 | NDB data nodes restart during online backup |
NDB data nodes restarted during online backup. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39318886 | Pods fail to pull images from private repository |
Pods failed to pull images from private repository. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
2 | 25.2.201 |
| 39324175 | Installation fails with a pre-created service account on OpenShift |
Installation failed with a pre-created service account on OpenShift. Deployment handling was updated for the affected OpenShift configuration. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39341350 | Replication goes down during upgrade because DBTIER_SITE_INFO column conversion fails
|
Replication went down during upgrade because Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39371221 | Handle missing GRR metadata tables after failed restore |
Handled missing GRR metadata tables after a failed site restore. Updated replication and recovery handling to preserve the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39427627 | Update site replacement procedure for StatefulSet rollout restart |
Updates were required for site replacement procedure for StatefulSet rollout restart. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the rollout restart procedure for all StatefulSets to the site replacement procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
2 | 26.1.200 |
| 39445456 | SLF 26.1.200 - Observing Ndbmtd pods restarts in multiple containers with different error codes |
Configuration options were not exposed for Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39459517 | Document global.imagePullSecrets object-list format for Helm install |
Documentation was missing for global.imagePullSecrets object-list format for Helm install. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the global.imagePullSecrets parameter to the "Global Parameters" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
2 | 25.2.202 |
| 39472791 | Prevent LoadBalancer labels on db-replication-svc internal service |
The system did not prevent LoadBalancer labels on db-replication-svc internal service. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39505844 | dbtrecover fails on transient replication_info outage during restore |
Dbtrecover failed on transient replication_info outage during restore. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 25.2.202 |
| 39520233 | Fix missing StartNodeId validation before site addition |
Incorrect behavior affected missing StartNodeId validation before site addition. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39534327 | Update cnDBTier docs for dbtaudit guidance |
Updates were required for cnDBTier docs for dbtaudit. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the section 'Auditing cnDBTier Sites with dbaudit'. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
2 | 25.2.202 |
| 39536009 | DBTIER_INITIAL_BINLOG_POSITION lacks mate-site entries on fresh deployment |
DBTIER_INITIAL_BINLOG_POSITION lacked mate-site entries on a fresh deployment. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39554203 | NDB data node hits DBTC assertion during rolling-upgrade failure handling |
An NDB data node hit a DBTC assertion during rolling-upgrade failure handling. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39572938 | GRR failed on SM Performance Setup beacuse of wrong calculation of Disk sufficiency. |
Incorrect behavior affected GRR backup PVC validation using aggregate memory usage. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39577599 | Clarify georeplication credentials and encryption-key guidance |
Documentation was unclear about georeplication credentials and encryption-key guidance. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the password-encryption guidance with credential and encryption-key requirements for georeplication sites. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
2 | 26.1.200 |
| 39656682 | Document GRR recovery when replication_info is missing after NDB restore failure |
Documentation was missing for GRR recovery when replication_info was missing after NDB restore failure. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added recovery steps for a missing replication_info database to the "Restoring GR Failures Using cnDBTier GRR APIs" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
2 | 26.1.200 |
| 39659432 | Add grr_info cleanup step to replication recovery guide |
Support was missing for grr_info cleanup step to replication recovery guide. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: Added the grr_info cleanup step to the replication recovery procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
2 | 26.1.200 |
| 39675735 | GRR through dbtrecover fails when Auto GRR is disabled |
GRR through dbtrecover failed when Auto GRR was disabled. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39695536 | dbtreplmgr timeout while waiting for expected replication status |
dbtreplmgr could time out while waiting for replication to reach the expected status. Replication-status handling was updated to avoid the timeout. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39654370 | Replication break after cnDBTier upgrade due to schema-conversion conflict |
Replication could break after upgrading cnDBTier from 25.1.201-5 to 26.1.200 because of a schema-conversion conflict. Upgrade and replication handling were updated to prevent the conflict. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39713808 | NDB restart during ASM-enabled IPv6 upgrade |
During an upgrade from 25.2.201 to 26.1.200 in a three-site NSSF GR IPv6 deployment with ASM enabled, ndbmtd could restart with error 6054 and extend upgrade duration. The upgrade flow was updated to prevent the restart. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39747263 | FRR failure indication and credential exposure in execution logs |
Fast Replication Recovery (FRR) could fail without a clear recovery-failure indication and could expose MySQL credentials in execution logs. FRR error handling and log sanitization were updated. Doc Impact: There is no documentation impact. |
2 | 26.1.201 |
| 39758599 | Upgrade and rollback documentation for ASM external-enabled setup |
The upgrade and rollback documentation required updates for ASM external-enabled deployments. The documentation was updated to provide the required procedure. Doc Impact: Added the Upgrade and Rollback procedures in the "Migrating cnDBTier to Use ASM for External Communication" section. For more information, see Oracle Communications Cloud Native Core cnDBTier User Guide. |
2 | 26.1.201 |
| 39676520 | Upgrade failure with large DBTIER_REPL_EVENT_INFO table |
An upgrade from 25.2.201 to 26.1.200 could fail when replication_info.DBTIER_REPL_EVENT_INFO contained a large number of entries. Upgrade handling was updated to support this condition. Doc Impact: There is no documentation impact. |
2 | 26.1.201 |
| 39561914 | GRR backup taken from preferred instead of override site | During GRR, the remote-server backup can be taken from the preferred backup site instead of the configured override site.
Doc Impact: Updated the section "cnDBTier Deterministic and Controllable Automatic Georeplication Recovery (GRR)" section to clarify GRR backup-site selection precedence and limitations. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
2 | 26.1.200 |
| 39553160 | dbtaudit failure with password encryption
|
dbtaudit can fail when password encryption is enabled.
Doc Impact: Updated the section "Auditing cnDBTier Sites with dbtaudit" to clarify password-encryption support for |
2 | 25.2.202 |
| 38924435 | Deleting all CNDB pods across three sites causes unrecoverable replication breakage |
Deleting all CNDB pods across three sites caused unrecoverable replication breakage. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38931127 | LoadBalancerClass must be explicitly added for F5 SPK IP assignment |
LoadBalancerClass was not added automatically for F5 SPK IP assignment. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38948407 | RESTART_SQL_NODES_FOR_BINLOG_THREAD_STALL event observed |
A RESTART_SQL_NODES_FOR_BINLOG_THREAD_STALL event was observed. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38958909 | Missing Documentation for Immutable External IPs After Replication Setup |
Documentation was missing for Immutable External IPs After Replication Setup. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added a note stating that external IP addresses were immutable after replication setup to the georeplication configuration procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.2.200 |
| 38959055 | Replication pod restart occurs while re-establishing georeplication |
A replication pod restart occurred while georeplication was being re-established. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38962843 | Replication got failed while upgrading the site during new site addition |
Replication failed while the site was being upgraded during new site addition. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38981208 | All GRR events are not captured in replication_info.DBTIER_REPL_EVENT_INFO after GRR completion |
All GRR events were not captured in replication_info.DBTIER_REPL_EVENT_INFO after GRR completion. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38983663 | Replication goes down after horizontal scaling in a three-site setup |
Replication went down after horizontal scaling in a three-site setup. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39013599 | Replication SVC PVC scaling is failing on Non GR/Single site setup |
Replication SVC PVC scaling failed on non-GR or single-site setup. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39026907 | Helm test pod logs display No resources found before health-check logs |
The Helm test pod displayed "No resources found" before the health-check logs appeared. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39043466 | node_type attribute missing in DBTier TC Time Track Metrics |
The node_type attribute was missing from DBTier TC Time Track Metrics. Metrics and monitoring handling was updated so the expected data and behavior were reported correctly. Doc Impact: Added the node_type attribute to the DBTier TC Time Track Metrics section. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 25.2.200 |
| 39058094 | Kyverno policy created during non-ASM deployment is not applied correctly |
Kyverno policy created during non-ASM deployment was not applied correctly. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39061324 | LOCAL_BACKUP_INITIATE fails when backup_info database does not exist on failed site |
LOCAL_BACKUP_INITIATE failed when backup_info database did not exist on failed site. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39079483 | GRR stuck in BACKUPRESTORE state |
GRR became stuck in BACKUPRESTORE state. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39087322 | mysql-external-connectivity-service should be removed from custom YAML |
Mysql-external-connectivity-service was incorrectly included from custom YAML. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39091105 | dbtscale_ndbmtd_pods must stop on NDB query and sanity failures |
Dbtscale_ndbmtd_pods did not stop on NDB query and sanity failures. Scaling and resource-handling logic was updated to validate values and complete the operation correctly. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39093230 | db-replication-svc pods are not prompted for manual restart when automated restart fails during dbtrecover |
Db-replication-svc pods were not prompted for manual restart when automated restart failed during dbtrecover. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.102 |
| 39093333 | PvcUsageMetricsBuilder fails to read PVC size |
PvcUsageMetricsBuilder failed to read PVC size. Metrics and monitoring handling was updated so the expected data and behavior were reported correctly. Doc Impact: There is no documentation impact. |
3 | 25.2.102 |
| 39136847 | CNCC georeplication status shows down when georeplication is up |
CNC Console showed the georeplication status as down when georeplication was up. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39143347 | dbtscale_vertical_pvc updates replication pod PVC values in bytes instead of Gi |
Dbtscale_vertical_pvc updated replication pod PVC values in bytes instead of Gi. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39159515 | dbtaudit script does not work in dual-stack deployment |
Dbtaudit script did not work in dual-stack deployment. The affected utility was updated to validate prerequisites, handle startup conditions, and report its result accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 39221202 | Documentation Error: upgradeStrategy and RollingRestart Mentioned Incorrectly |
Documentation contained incorrect section references for upgradeStrategy and RollingRestart. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Corrected the affected section references in the backup and recovery procedures. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide |
3 | 26.1.200 |
| 39249443 | Discrepancy in global.ndb.restoreparallelism documentation value |
A discrepancy existed in global.ndb.restoreparallelism documentation value. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the global.ndb.restoreparallelism parameter in the "Global Parameters" section with the correct value. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39254203 | Helm chart error while installing cnDBTier 26.1.200 |
A Helm chart error occurred while cnDBTier 26.1.200 was being installed. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39256558 | Prevent empty IPv6 admin_address during ndbappmysqld upgrade startup |
The system did not prevent empty IPv6 admin_address during ndbappmysqld upgrade startup. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39270244 | cnDBTier Rollback not supported when istiosidecarinject mode:external |
The GRR process was not documented for single-site ASM migration. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the "Migrating cnDBTier to Use ASM for External Communication" section with the GRR steps required for a single-site setup. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 25.2.201 |
| 39286747 | Pre-upgrade hook completes close to timeout |
The pre-upgrade hook completed close to the timeout. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39288509 | Alert documentation does not match REPLICA_REPLICATION_DELAY_HIGH implementation
|
Alert documentation did not match Doc Impact: Updated the |
3 | 26.1.200 |
| 39303366 | Horizontal scaling script does not reject incorrect charts |
Horizontal scaling script did not reject incorrect charts. Scaling and resource-handling logic was updated to validate values and complete the operation correctly. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39303979 | Documentation issue in Event API |
Documentation was incorrect in Event API. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the Event Details API request, response, time-window, and pagination information. For more information, see Oracle Communications Cloud Native Core, cnDBTier REST API Guide. |
3 | 26.1.200 |
| 39364230 | Add total script execution time output to dbtaudit |
dbtaudit did not print total execution time. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39364277 | Add total script execution time output to dbttriage should print total execution time |
dbttriage did not print total execution time. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39365054 | Add total script execution time output to dbtfastrecover should print total execution time |
Dbtfastrecover did not print total execution time. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39365473 | Improve dbtrecover backup-site messaging |
Startup handling was incomplete for dbtrecover backup-site messaging. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39367733 | Missing sample cnDBTier Generic CSAR structure |
A sample cnDBTier Generic CSAR structure was missing. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the Generic CSAR directory and file structure to the CSAR package documentation. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 26.1.200 |
| 39367847 | Duplicate ETSI-Entry-Certificate entry in TOSCA.meta |
A duplicate ETSI-Entry-Certificate entry existed in TOSCA.meta. Package validation and deployment content were updated to use the correct files and references. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39372533 | Digital validation script does not fail when .sig file is missing |
The digital validation script did not fail when the .sig file was missing. Package validation and deployment content were updated to use the correct files and references. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39374079 | Fix cs-restricted PSP RoleBinding reference |
Incorrect behavior affected cs-restricted PSP RoleBinding reference. Package validation and deployment content were updated to use the correct files and references. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39374255 | Definitions/occndbtier.yaml contains incorrect paths in CDCS CSAR |
Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39398750 | Pre-upgrade hook fails when stop_repl_switchover contains NULL
|
Pre-upgrade hook failed when Doc Impact: There is no documentation impact. |
3 | 25.2.102 |
| 39417142 | Handle empty API_FQDNS in db-monitor datasource selection
|
Handling was missing for empty Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39418328 | Skip heartbeat metrics when replication is not configured |
The system did not skip heartbeat metrics when replication was not configured. Metrics and monitoring handling was updated so the expected data and behavior were reported correctly. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39439674 | DBTIER_SITE_CONFIG is skipped by dbtremovesite
|
Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39439891 | Add site replacement cleanup for stale DBTIER_REPL_SVC_INFO entries
|
Support was missing for site replacement cleanup for stale Doc Impact: Added the |
3 | 26.1.200 |
| 39460693 | DB monitor service throws NullPointerException during initialization |
DB monitor service threw NullPointerException during initialization. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39520999 | Sync PVC-stored GRR events when parallel recovery is disabled |
Synchronization was missing for PVC-stored GRR events when parallel recovery was disabled. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39521183 | Prevent failed or uninstalled sites from being selected as backup |
The system did not prevent failed or uninstalled sites from being selected as backup. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39522690 | Add GRR guide note for dummy remoteSiteIp when remote site is failed |
Support was missing for GRR guide note for dummy remoteSiteIp when remote site had failed. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: Added a note about using a dummy remoteSiteIp value when the remote site had failed to the GRR procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39527608 | Document DBTIER_INITIAL_BINLOG_POSTION row-count mismatch behavior |
Documentation was missing for DBTIER_INITIAL_BINLOG_POSTION row-count mismatch behavior. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the expected row-count mismatch behavior for DBTIER_INITIAL_BINLOG_POSTION to the dbtaudit troubleshooting information. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 25.2.202 |
| 39534838 | Update cnDBTier doc for internalService guidance |
Updates were required for cnDBTier documents for internalService guidance. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the internalService parameters to the DB Replication Service parameters section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.2.202 |
| 39535060 | Clarify dbttriage supported tests in documentation |
Documentation was unclear about dbttriage supported tests in documentation. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the supported diagnostic tests to the "Using dbttriage" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39537317 | Fix dbtaudit namespace re-prompting after sourcing source_me |
Incorrect behavior affected dbtaudit namespace re-prompting after sourcing source_me. The affected utility was updated to validate prerequisites, handle startup conditions, and report its result accurately. Doc Impact: There is no documentation impact. |
3 | 25.2.202 |
| 39543100 | Update GRR HTTPS curl examples |
Updates were required for GRR HTTPS curl examples. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: Updated the HTTPS curl examples in the "Georeplication Recovery APIs" section to remove --pass and include --cacert. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39552371 | Fix ndbmysqld scaling procedure when adding a site |
Incorrect behavior affected ndbmysqld scaling procedure when adding a site. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the ndbmysqld pod scaling steps in the "Adding a Georedundant Cluster" procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 26.1.200 |
| 39559531 | Document source_me prerequisite for dbtfastrecover |
Documentation was missing for source_me prerequisite for dbtfastrecover. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the source ./source_me prerequisite to the "Using dbtfastrecover" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39573289 | Correct MYSQL_NDB_CLUSTER_DISCONNECT alert clear behavior documentation
|
Incorrect behavior affected Doc Impact: Corrected the clear condition for the |
3 | 26.1.200 |
| 39581697 | Clarify dbtrecover backup-site selection policy |
Documentation was unclear about dbtrecover backup-site selection policy. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added preferred backup site and backup site selection policy behavior to the GRR recovery procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39585469 | Fix false server_id warnings for sparse multi-site deployments |
Incorrect behavior affected false server_id warnings for sparse multi-site deployments. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39587337 | Document dbtaudit OpenShift oc namespace handling |
Documentation was missing for dbtaudit OpenShift oc namespace handling. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added OpenShift oc namespace handling information to the dbtaudit section. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 26.1.200 |
| 39587775 | Document dbttriage --use-oc namespace requirements |
Documentation was missing for dbttriage --use-oc namespace requirements. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the OpenShift namespace requirements for the --use-oc option to the "Using dbttriage" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39619029 | Update GRR state name in Exception Table Restoration documentation |
Updates were required for GRR state name in Exception Table Restoration documentation. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Updated the GRR state name to |
3 | 26.1.200 |
| 39658556 | Document invalid preferredBackupSite behavior |
Documentation was missing for invalid preferredBackupSite behavior. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added invalid preferredBackupSite behavior for STRICT and PREFERRED policies to the "Deterministic and Controllable Automatic GRR" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 26.1.200 |
| 39669973 | Add localhost SANs to server certificate |
Support was missing for localhost SANs to server certificate. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39675399 | Remove obsolete DBTIER_BACKUP_COMMAND_QUEUE cleanup step
|
Obsolete behavior remained for obsolete Doc Impact: Removed the |
3 | 26.1.200 |
| 39677883 | Documentation issue in site addition procedure |
Documentation was incorrect in site addition procedure. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Corrected the site addition steps in the "Adding a Georedundant Cluster" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
3 | 26.1.200 |
| 39687925 | dbtfastrecover fails with AttributeError when db_replication_svc pod is unavailable |
Dbtfastrecover failed with AttributeError when db_replication_svc pod was unavailable. Replication and recovery handling was updated to maintain the expected state and report failures accurately. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 38915605 | Replication service restart during GRR | The db-replication-svc pod can restart with exit code 137 during the GRR procedure.
Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38585013 | dbtscale_vertical_pvc stuck in phase 4
|
On a non-GR setup, dbtscale_vertical_pvc can remain stuck for an ndbapp pod in phase 4 while waiting for localhost to restart.
Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 38468810 | MOP correction for replica start and stop through REST API | The cnDBTier 25.1.200 FR MOP requires correction for starting and stopping a replica through REST APIs.
Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 38884040 | PVC values updated in bytes instead of Gi | The dbtscale_vertical_pvc script can update new PVC values in bytes rather than Gi units.
Doc Impact: There is no documentation impact. |
3 | 25.1.201 |
| 38921972 | Replication delay during CNCC upgrade | A replication delay of up to 10 hours (36000 seconds behind remote) can occur during CNCC upgrade.
Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 38916012 | Cluster disconnect during ndbappmysqld horizontal scaling
|
A cluster disconnect can occur when ndbappmysqld pods are horizontally scaled during DB upgrade from 25.2.100 to 25.2.101.
Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38877149 | Replication break after pod scale-down with skip error enabled | Replication can break when skip error is enabled after ndbmysqld and ndbappmysqld pods are completely scaled down for 15 minutes.
Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39570772 | dbtscale_ndbmtd_pods phase 1 does not exit
|
Phase 1 of dbtscale_ndbmtd_pods does not exit when existing NDB data nodes are disconnected or still starting.
Doc Impact: There is no documentation impact. |
3 | 25.2.202 |
| 39476632 | Incorrect backup source selected by dbtrecover |
While recovering Site 3, dbtrecover can select Site 4 as the backup source instead of Site 1.
Doc Impact: There is no documentation impact. |
3 | 25.2.202 |
| 39376809 | dbtuser does not work
|
dbtuser does not work in cnDBTier 25.1.201-4.
Doc Impact: There is no documentation impact. |
3 | 25.1.201 |
| 39723714 | Incorrect GRR GET Config Values API response | The GRR GET Config Values API returns an incorrect response message.
Doc Impact: Updated the GET |
3 | 26.1.200 |
| 39735312 | replication_skiperror_count does not reset consistently
|
The replication_skiperror_count column in replication_info.DBTIER_REPL_ERROR_SKIP_INFO does not consistently reset to zero after the expected default 3600-second window.
Doc Impact: Updated the section "Using dbtfastrecover" with skip-error limits, reset-window behavior, and recovery actions after a safety limit is exceeded. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39278880 | False MYSQL_NDB_CLUSTER_DISCONNECT alert on Site 3
|
A MYSQL_NDB_CLUSTER_DISCONNECT alert can be observed for Site 3 even when the setup is stable.
Doc Impact: There is no documentation impact. |
3 | 25.1.103 |
| 38948216 | Incorrect log message: "Restarting odd pods" but even pod ordinals are listed |
The log message incorrectly stated "Restarting odd pods" when even pod ordinals were listed. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38952168 | Log displays empty timeout value when waiting for pod |
The log displayed an empty timeout value while waiting for a pod. Pod and node handling was updated to prevent the failure and restore the expected operational state. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39074819 | Add ASM-only external migration note for istio-inject annotation |
Support was missing for ASM-only external migration note for istio-inject annotation. The affected cnDBTier logic and validation were updated to restore the expected behavior. Doc Impact: Added the istio-inject: false requirement to the "Migrating cnDBTier to Use ASM for External Communication" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
4 | 25.2.201 |
| 39202574 | Validate backup encryption password and report unsupported characters |
Validation was missing for backup encryption password and report unsupported characters. Backup and recovery handling was updated to validate the required state and complete the operation reliably. Doc Impact: There is no documentation impact. |
4 | 25.2.102 |
| 39239616 | Incorrect Service Reference in LoadBalancerClass Description for sqlgeorepsvclabels |
Documentation contained incorrect section references for LoadBalancerClass Description for sqlgeorepsvclabels. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Corrected the affected section references in the backup and recovery procedures. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
4 | 26.1.200 |
| 39239771 | Incorrect documentation section references for backup encryption, remote transfer, TDE, and upgrade |
Documentation contained incorrect section references for backup encryption, remote transfer, TDE, and upgrade. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Corrected the affected section references in the backup and recovery procedures. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
4 | 26.1.200 |
| 39303483 | Update dbtfastrecover documentation for OpenShift execution |
Updates were required for dbtfastrecover documentation for OpenShift execution. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the OpenShift command and namespace requirements to the "Using dbtfastrecover" section. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
4 | 26.1.200 |
| 39326958 | Unable to configure cnDBTier alert rule files on OSO |
cnDBTier alert rule files could not be configured on OSO. Metrics and monitoring handling was updated so the expected data and behavior were reported correctly. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39332167 | Explain why port 8080 is used as remotesiteport |
Documentation did not explain why port 8080 was used as remotesiteport. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added an explanation for using port 8080 as remotesiteport to the applicable georeplication procedure. For more information, see Oracle Communications Cloud Native Core, cnDBTier Installation, Upgrade, and Fault Recovery Guide. |
4 | 26.1.200 |
| 39349551 | Mismatch Between Documented and Actual CSAR Test Folder Contents in DB Tier 26.1.200 User Guide |
A sample cnDBTier Generic CSAR structure was missing. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the Generic CSAR directory and file structure to the CSAR package documentation. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
4 | 26.1.200 |
| 39594026 | Document expected dbtaudit cross-site inconsistency findings |
Documentation was missing for expected dbtaudit cross-site inconsistency findings. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Added the expected cross-site inconsistency findings to the dbtaudit section. For more information, see Oracle Communications Cloud Native Core, cnDBTier User Guide. |
4 | 26.1.200 |
| 39599813 | Fix REST API documentation inconsistencies |
Incorrect behavior affected REST API documentation inconsistencies. The affected documentation was updated to provide the correct procedure, configuration, or reference information. Doc Impact: Corrected the GeoReplication and Config endpoint paths, parameters, and examples. For more information, see Oracle Communications Cloud Native Core, cnDBTier REST API Guide. |
4 | 26.1.200 |
| 39745375 | db_tier_client_sql_tps metric not scraped by Prometheus |
The db_tier_client_sql_tps metric was generated by ndbappmysqld but was not scraped by Prometheus. Metrics scraping was updated to expose the metric correctly. Doc Impact: There is no documentation impact. |
4 | 25.2.100 |
Note:
Resolved bugs from 25.2.202 have been forward ported to Release 26.1.201.4.2.4 CNC Console Resolved Bugs
Release 26.1.200
Table 4-5 CNC Console 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39603655 | LDAP users were not authenticated after CNCC upgrade to 25.1.202 from 24.2.4 |
LDAP Test Connection and LDAP login failed in single-stack IPv6 environments because CNCC-IAM/Keycloak was not started with the required IPv6 preference settings. CNCC custom-values support was updated to expose cncc-iam.kc.preferIpv6Stack.enabled, so the required IPv6 JVM preference could be enabled for LDAP connectivity. Upgrade and rollback documentation was also updated to preserve Unicode characters correctly during database backup and restore. Doc Impact: The “Global Configuration Options” section and the upgrade and rollback documentation are updated to include IPv6 preference configuration and Unicode-safe backup and restore guidance in Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.1.202 |
| 39396760 | Added tolerationSeconds values for NoExecute toleration in CNCC YAML file |
Helm custom-values support was added to configure NoExecute tolerationSeconds for CNCC pods during node not-ready or unreachable conditions. Doc Impact: The “Global Configuration Options” section is updated in Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.1.200 |
| 39259142 | CNCC Console showed an error while changing the operational state |
Operational State Change from the CNCC GUI failed because the request was not sent with the required Content-Type: application/json header. The backend rejected the GUI request even though the same operation worked through REST API. CNCC GUI request handling was corrected so Operational State Change requests were sent with the required Content-Type header. Doc Impact: There is no documentation impact. |
3 | 25.2.101 |
| 39387135 | Support was required for CNCC ingress configuration in NodePort mode |
CNCC did not have code-level support to configure ingress gateway services in NodePort mode. CNCC chart/custom-values handling was updated to support configurable NodePort service type and static HTTP/HTTPS node port configuration for CNCC ingress services such as cncc-iam, mcncc-core, and acncc-core. Doc Impact: The new NodePort custom-values parameters are added in Oracle Communications Cloud Native Configuration Console Installation Guide. |
3 | 25.2.200 |
| 39080860 | CNCC LDAP server binding credentials via API |
CNC Console REST API documentation was updated with additional API endpoints to update LDAP server binding credentials through REST APIs using curl or Postman. Doc Impact: Additional APIs are added in Oracle Communications Cloud Native Configuration Console REST API Guide. |
4 | 24.2.3 |
| 39214507 | API prefix clarification was required for PCF and BSF API calls through CNCC |
The CNC Console User Guide “Accessing NF Configurations Through Curl and Postman” section was updated with examples of Policy and BSF curl requests. Doc Impact: Examples of Policy and BSF curl requests are added in Oracle Communications Cloud Native Configuration Console User Guide. |
4 | 25.2.100 |
| 39415443 | CNCC 25.2.2xx default custom-values parameter had incorrect spelling |
The CNC Console parameter global.maxUnvailable contained an incorrect spelling. The parameter was updated in the custom values.yaml file. Doc Impact: The “Global Configuration Options” section is updated in Oracle Communications Cloud Native Configuration Console Installation, Upgrade, and Fault Recovery Guide. |
4 | 25.2.200 |
Note:
Resolved bugs from 25.2.200 have been forward ported to Release 26.1.200.4.2.5 CNE Resolved Bugs
Release 26.1.200
Table 4-6 CNE 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 39098746 | Installation Failure Due to network_optimize.service Start Error | Installation failed when network_optimize.service started on vCNE nodes with a high CPU count because the generated RPS CPU mask value exceeded the supported data type size. The network optimization service, which tunes CNE nodes for optimal and predictable CNLB network performance, caused the installation failure.
Doc Impact: There is no documentation impact. |
1 | 26.1.200 |
Note:
Resolved bugs from 25.2.201 have been forward ported to Release 26.1.200.4.2.6 NSSF Resolved Bugs
Release 26.1.202
Table 4-7 NSSF 26.1.202 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 39904375 | candidateAmfList format is not included |
The NsSelection Doc impact: There is no doc impact. |
2 | 26.1.201 |
| 39830194 | NSSF must have service name as per spec while registering to NRF |
NSSF application-profile service names were corrected to the specification-compliant values for NRF registration. Doc impact: There is no doc impact. |
3 | 26.1.200 |
| 39789456 | NSSF-NRF Subscription (GR state) Is Not Automatically Restored After Recovery from a Complete Critical-Service Outage |
The NSSF-to-NRF on-demand subscription was restored after recovery from a complete critical-service outage, so NSSF continued to receive NRF peer-status notifications. Doc impact: There is no doc impact. |
3 | 26.2.200 |
| 39830138 | SubscriptionToNrfFailed alert OID mismatch |
The SubscriptionToNrfFailed alert OID was corrected to match the alert YAML file. Doc impact: Updated the SubscriptionToNrfFailed alert OID in the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide. |
4 | 26.1.200 |
| 39877626 | Feature Documentation Clarification–Support to Handle Partial NF Notification |
Documentation was clarified to state that partial NF Profile Update Notification support is always enabled in NSSF and cannot be enabled, disabled, or configured through Helm, REST, or CNCC. Doc impact: Updated the configuration-status and partial-NF-notification content in the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide. |
3 | 26.1.200 |
| 39773810 | CNCC GUI Issues related to user-agent and system options configuration |
The CNCC GUI no longer required an NF instance ID for User-Agent configuration, and Doc impact: There is no doc impact. |
4 | 25.2.200 |
| 39015332 | LCI OCI header contains NfInstance ID but does not contain serviceInstanceId |
NsSelection and NsSubscription responses were updated to include the backend NSSF header so the gateway could generate NF-service-instance-specific load information and OCI and LCI headers. Doc impact: There is no doc impact. |
4 | 25.2.200 |
| 39891691 | NSSF CV file modifications related to obsolete NRF urls and InstanceId under oauthConfig not getting configured correctly |
Obsolete NRF URL parameters were removed from the default NSSF configuration, and the OAuth instance ID was added to egress-gateway configuration. Doc impact: There is no doc impact. |
4 | 26.1.200 |
Release 26.1.201
Table 4-8 NSSF 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39193463 | notifCondition with monitoredAttributes is not present in Subscription request initiated by NSSF in GR. |
NSSF did not include notifCondition with monitoredAttributes in subscription requests that it sent to NRF in GR. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39236415 | Overload feature is not working because the perf-info service cannot communicate with the Prometheus server getting 503 error response |
In 25.2.200, the overload feature did not trigger during 120% and 150% traffic because the perf-info service could not communicate with the Prometheus server and received a 503 response. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39504583 | During the L1 Overload scenario, the OSO ALM pod restarted with OOMKilled after the OSO APM pod was intentionally brought down |
During an L1 overload scenario in 26.1.200, the OSO ALM pod repeatedly restarted with an OOMKilled condition after the OSO APM pod was intentionally scaled down. Doc Impact: Updated Oracle Communication Cloud Native Core, Operations Services Overlay Installation and Upgrade Guide, section "Configuration of Alert Processing Microservice (APM)" with a limitation that APM supports a single replica deployment and that extended APM unavailability or scale-down to zero replicas can increase Alert Manager memory consumption and cause OOM conditions. |
2 | 26.1.200 |
| 39291838 | NSSF ATS scenario names contains a typo in the feature file |
Several NSSF ATS feature file scenario names contained typographical errors and spelling inconsistencies. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39148715 | One of the Availability pods was recreated during the NSSF upgrade, with no changes in the associated Deployment or ConfigMap. |
During an upgrade to 26.1.200, one Availability pod was recreated even though the associated Deployment and ConfigMap did not change. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39582033 | CPU allocation for the Leader DB Replication Service need to be increased in custom yaml of CNDB shared with NSSF package |
The CPU allocation for the leader DB Replication Service in the CNDB custom YAML shared with the NSSF package needed to be increased from 2 CPUs to 8 CPUs. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39202008 | NSSF transitions to Deregistered state instead of Suspended state in NRF when Egress service replicas are scaled to zero |
When Egress service replicas were scaled to zero, NSSF moved to the Deregistered state in NRF instead of the Suspended state. Doc Impact: Updated the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide, "NSSF behaviour when microservices are scaled down" table, to describe NSSF behavior when microservices are scaled down. |
3 | 26.1.200 |
| 39322192 | NS-Selection 99th percentile latency is higher than IGW for NS-Selection latency in the Grafana dashboard. |
During 27K TPS traffic, Grafana showed NS-Selection 99th percentile latency as higher than ingress gateway latency for NS-Selection. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39193092 | NSSF 26.1.200: destinationRules should include the hostname in given example in nssf service_mesh custom yaml. |
In 26.1.200, the service mesh custom YAML example for CNDB in a different namespace did not work because the destinationRules host did not include the .svc.<cluster_hostname> suffix. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39200060 | NSSF should not return a 2xx success response for notifications from NRF containing invalid or non-compliant 3GPP parameters Values. |
NSSF returned a 2xx success response for NRF notifications that contained invalid or non-compliant 3GPP parameter values. Doc Impact: Updated the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide, "Support to Handle Partial NF Profile Update Notifications From NRF" section with in Validation/Error Cases. |
3 | 26.1.200 |
| 39015501 | LastUpdateTime field is not getting updated when updating the geo_redundant_sites_info table. |
NsSubscription did not update the LastUpdateTime field when it updated the geo_redundant_sites_info table. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39210841 | NSSF 26.1.200: Ingress Rate Section in Grafana is not showing any traffic. |
In 26.1.200, the Grafana Ingress Rate section showed no traffic, and the related Prometheus query returned no data. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39258489 | CNDB pod(ndbappmysqld) restart observed during cndb upgrade from 25.2.200 to 26.1.200 |
During a CNDB upgrade from 25.2.200 to 26.1.200, ndbappmysqld pods restarted once on all three CNDB sites, although the upgrade succeeded and no significant traffic drop was observed. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39540527 | NSSF Helm charts PDB minAvailable parameter is unused and documentation needs correction |
In 25.2.200, the NSSF PodDisruptionBudget Helm charts exposed the unused minAvailable parameter, so the chart values and documentation needed correction to use one active disruption-budget parameter. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39381521 | NSSF 25.2.200: alertnative-route replica count mismatch between CIQ and custom values file |
In 25.2.200, the Ns-Auditor replica count in the default custom values file did not align with the CIQ, which expected one replica. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39008266 | NSSF should reject avail put and patch request if SST type is string. |
NSSF accepted an ns-availability PUT request when sst was sent as a string; sst string values in PUT and PATCH requests should have been rejected. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39031340 | With CNDB and NSSF deployed as non-ASM setup in same namespace NSSF installation fails |
In 25.2.200 non-ASM mode, NSSF installation failed when CNDB and NSSF were deployed in the same namespace with service mesh disabled because the pre-install hook was denied for a read-only root filesystem policy violation. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38552515 | GW Metrics issues for NSSF 54K Success Scenario and 26K failure [Slice is not configured in PlmnInfo] TPS traffic on single site. |
In 25.2.200, ingress gateway metrics were incorrect during single-site traffic with 54K successful TPS and 26K failed TPS: 503 responses were not pegged, some 500 responses appeared only in metrics, a 403 invalid-slice reason showed as UNKNOWN, and a backend 403 response was pegged as a 500 response. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38238999 | oc_oauth_request_failed_cert_expiry Metric not getting pegged. |
The oc_oauth_request_failed_cert_expiry metric was not pegged when a certificate-expired OAuth request returned a 408 response. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 35860137 | In Policy Mapping Configuration in Ingress Gateway, For the samplingPeriod parameter, max value of parameter validation should be necessary. |
In policy mapping configuration, NSSF accepted an excessively large samplingPeriod value and returned a 200 response because maximum value validation was missing. Doc Impact: There is no documentation impact. |
3 | 23.3.0 |
| 36552026 | KeyId, certName, kSecretName, and certAlgorithm invalid values are not validating in the oauthvalidator configuration. |
The OAuth validator configuration accepted invalid keyId, certName, kSecretName, and certAlgorithm values, and validation was also needed in CNCC UI. Doc Impact: There is no documentation impact. |
3 | 24.1.0 |
| 39207188 | Oauth error codes not consistent with configuration done in CV file under oauthErrorConfigForValidationFailure |
In 26.1.200, OAuth error responses used the correct title and detail but did not use the status codes configured in oauthErrorConfigForValidationFailure for expired-token and KID-mismatch cases. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39503711 | duplicate alerts are raised for L1 and L2 Overload Level during performance validation |
In 26.1.200, duplicate alerts were raised for L1 and L2 overload levels during performance validation, while previous releases raised one alert for the same condition. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39031454 | Removal of deprecated attribute contentEncodingEnabled since this attribute is no longer being used for gzip compression |
In 25.2.200, the deprecated contentEncodingEnabled attribute remained in custom YAML even though it was no longer used for gzip compression. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39550656 | Continuous Error printing in ns availability pod logs. |
The ns-availability pod logs continuously printed Refresh task failed due to invalid response code for k8s api query response. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39200552 | The guide shall explicitly document the 3GPP-defined parameter classification for all attributes associated with NRF partial profile update notifications |
The guide did not capture the 3GPP classification for NotificationData attributes and ChangeItem attributes associated with NRF partial profile update notifications. Doc Impact: Updated the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide, "Definition of Type NotificationData" and "Definition of ChangeItem" tables with condition information for NotificationData and ChangeItem. |
4 | 26.1.200 |
| 39490095 | NSSF 26.1.200: helm success message for NSSF is for installation instead of upgrade |
In 26.1.200, Helm upgrade output displayed Thank you for installing ocnssf instead of Thank you for upgrading ocnssf. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39490028 | Clarification Required: NSSF NRF Subscription Deletion Behavior in 3-Site GR Setup (Partial profile) |
In a 3-site GR setup, the expected behavior for NSSF NRF subscription deletion was not clearly defined, including the scenarios in which NSSF was expected to delete a subscription. Doc Impact: Updated the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide, "Support to Handle Partial NF Profile Update Notifications From NRF" section with a note that when NSSF is deregistered from an NRF in a three-site GR deployment, the NRF Client sends a subscription deletion request to the NRF. |
4 | 26.1.200 |
| 39231019 | Statistics Name Correction Required in Partial Profile Update Notification |
The partial profile update notification statistic name did not match between the design page and Prometheus: the design used ocnssf_nrf_invalid_status_notification, and Prometheus used ocnssf_nrf_invalid_status_notification_total. Doc Impact: Updated the Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide, "Support to Handle Partial NF Profile Update Notifications From NRF" and "NSSF Metrics" sections so the metric name is ocnssf_nrf_invalid_status_notification_total. |
4 | 26.1.200 |
| 39129294 | Removal of enableOutgoingHttps flag under ingress section and incorrect comment added against enableIncomingHttp flag - Duplicate |
Bug link description and comments were not accessible; only the issue summary and status were returned. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39035289 | NSSF ATS 25.2.200: ATS Documentation is not same as feature file steps |
In 25.2.200, the ATS documentation did not match feature file steps; for example, grsites.feature scenario 02 used a PUT operation with status code 400, while the documentation showed PUT with status code 200. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39031666 | Removal of enableOutgoingHttps flag under ingress section and incorrect comment added against enableIncomingHttp flag |
In 25.2.200, custom YAML still included the unused enableOutgoingHttps flag under ingress, and the enableIncomingHttp comment incorrectly referred to HTTPS/2.0 instead of HTTP/2.0. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38222239 | NSSF Incorrectly Returns "Unsupported Value" Error for Valid SupportedFeature Values (10-15) in ns-availability PUT Request When All Features Are Disabled |
When all supported features were disabled, NSSF returned an Unsupported value error for valid SupportedFeature values 10 through 15 in an ns-availability PUT request instead of returning No optional features are supported. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 36653494 | If KID is missing in access token, NSSF should not send "Kid missing" instead of "kid configured does not match with the one present in the token" |
When KID was missing from the access token, NSSF returned the cause kid configured does not match with the one present in the token instead of Kid missing. Doc Impact: There is no documentation impact. |
4 | 24.1.0 |
| 39015332 | LCI OCI header contains NfInstance ID but does not contain serviceInstanceId |
For ns-selection, LCI and OCI headers included NF-Instance but did not include NF-Service-Instance, even though service instance mappings were configured; ns-availability returned both headers. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38941167 | Dynamic Logging Feature: With commonCfgClient.enabled set to false run time log level of services is still getting updated |
In 25.2.200, runtime log levels for ns-availability and ns-selection were still updated from CNCC even when commonCfgClient.enabled was set to false. Doc Impact: Updated the Oracle Communications Cloud Native Core, Network Slice Selection Function Installation, Upgrade, and Fault Recovery Guide and Oracle Communications Cloud Native Core, Network Slice Selection Function User Guide to state that |
4 | 25.2.200 |
Note:
Resolved bugs from 25.1.2xx have been forward ported to Release 26.1.201.4.2.7 OSO Resolved Bugs
Release 26.1.200
Table 4-9 OSO 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39335185 | OSO upgrade failed for RHOCP K8s version 1.20 |
OSO upgrades on Kubernetes 1.20 clusters failed due to Alertmanager Helm chart compatibility issues. Helm templates are now validated against Kubernetes 1.20, 1.25, and 1.27 to prevent incompatible artifacts from being released. This error was observed because ALM Helm charts were not performing checks on the k8s API for Kubernetes versions 1.20, 1.25, and 1.27. This error has been resolved by adding checks for the k8s version. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
Note:
Resolved bugs from 25.2.1xx have been forward-ported to Release 26.1.200.4.2.9 Policy Resolved Bugs
Release 26.1.201
Table 4-10 Policy 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found In Release |
|---|---|---|---|---|
| 39750847 | UM policies not executed for unknown subscribers in OCCNP |
PCRF skipped the usage monitoring processing for subscribers whose profile is missing from UDR. As a result, UM policies and configured unknownsubscriber handling are not executed for those subscribers. Doc impact: There is no documentation impact. |
2 | 25.1.200 |
| 39748403 | Observing the critical alert - PolicyDsIngressErrorRateAbove10Percent |
SM Policy sessions for Data Network Named (DNNs) excluded from Policy Data Service (PDS) communication can still be processed after PDS notifications for another session of the same subscriber. Stale PDS resources can then trigger repeated requests for nonexistent associations, increasing PDS errors and raising the PolicyDsIngressErrorRateAbove10Percent alert. Doc impact: There is no documentation impact. |
2 | 25.1.203 |
| 39702052 | Rollover data is updated without Rollover-limit in UDR if UDR is brought down/Up |
Usage monitoring failed to retain the rollover definition in UDR when UDR updates failed during a rollover operation. After session termination, later requests cannot recover the rollover limit or allocate quota from an otherwise valid rollover plan. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39125564 | UE Service fails to handle non-JSON "no healthy upstream" response from Istio during Timer Service downtime |
UE Service failed to handle a non-JSON no healthy upstream response from Istio during timer service downtime. This can break N1N2 transfer retry after handling when the dependency outage returns a plain-text upstream error. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39155184 | [Generic_Policy]: SAL logs for Nas messages needs to be improvised to have properly decoded details |
Subscriber Activity Log (SAL) logs for NAS messages do not provide properly decoded details. This can make troubleshooting NAS message handling harder because the logged information is not sufficiently readable or complete. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39723617 | After Policy rollback from 26.1.200 to 25.1.203(leap frog), diam-gateway went in crashloopback |
During rollback from 26.1.200 to 25.1.203, diameter gateway pods entered CrashLoopBackOff because mixed version coherence members use incompatible PartitionedCache quorum policies. This can leave a diameter gateway pod unavailable during the rollback. Doc impact: There is no documentation impact. |
2 | 26.1.200 |
| 38741484 | Observed that Grafana import is not working on CNE 25.2.100 version |
Policy observability dashboard imports failed on CNE 25.2.100 because the dashboard cannot resolve the required data sources. This prevents the supplied Grafana dashboard from loading correctly in the supported environment. Doc impact: There is no documentation impact. |
2 | 25.1.201 |
| 38503445 | [AM_UE_Perf]- Execution of ~80K Traffic having Stale Request Cleanup for UE Enabled throwing Error "java.lang.NullPointerException" |
AM and UE performance traffic with stale-request cleanup enabled triggered a NullPointerException under high load. This can interrupt affected performance executions and produce errors during request cleanup. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38315824 | [SM-PERFORMANCE] GRR with 10M db in SM failed with VALIDATERESOURCES "total required disk space for GRR is configured less" |
SM GRR execution with a 10-million record database failed the resource validation because the configured disk space requirement is insufficient. This blocked the GRR execution for the expected database scale. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38203873 | [AM-UE Performance] - Execution of 54k TPS, UE service have intermittent Error "Error in PDS request:404 Not Found" |
UE service intermittently received PDS 404 Not Found errors during 54K TPS AM and UE performance execution. This caused failures in affected requests under sustained load. Doc impact: There is no documentation impact. |
3 | 24.2.7 |
| 38110128 | Problem Statement: STALE_DIAMETER_CONNECTOR_REQUEST_CLEANUP alert expressions are wrong in AlertRules file |
STALE_DIAMETER_CONNECTOR_REQUEST_CLEANUP alert expressions used incorrect metric-label matching. This prevents the alert calculation from retrieving the intended data for diameter connector request cleanup failures. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39526979 | PA Create accepts a QoSMon subscription attempt when evSubsc.events is missing/empty, instead of rejecting it. |
PCF PA create accepted a request whose evSubsc.events field is missing or empty even though the field is mandatory. The malformed request can create an application session and trigger SMF UpdateNotify processing instead of being rejected. Doc impact: There is no documentation impact. |
3 | 26.1.200 |
| 39171986 | : "Observing "Emergency session establishment" failure as the evaluated message priority is lower during SM congestion." |
Emergency session establishment failled during SM congestion because the evaluated message priority is lower than expected. This can prevent emergency traffic from receiving the intended priority handling under congestion conditions. Doc impact: There is no documentation impact. |
3 | 24.2.0 |
| 39206384 | Audit notify fails at SM serivce with 500 INTERNAL_SERVER_ERROR because "sessionType" is null |
SM service audit notification failed with a 500 INTERNAL_SERVER_ERROR when sessionType is null. This can prevent audit notify processing for sessions missing that field. Doc impact: There is no documentation impact. |
2 | 25.2.100 |
| 39271829 | [Generic]: Unable to delete user data for pcrf-core service from session viewer |
Session viewer failed to delete data for the pcrf-core service. You can be unable to remove PCRF Core session data through the expected UI workflow. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39580205 | Session Management PUT/GET returns only partial payload instead of complete configuration |
Session Management PUT and GET operations returned only a partial payload instead of the complete configuration. This can cause you or clients to see incomplete session-management configuration data. Doc impact: There is no documentation impact. |
3 | 24.2.0 |
| 38589051 | Observing continuous flood of NPE in SM service while running PA-CREATE/UPDATE flows with SDC (Sponsored Data Connectivity Supports) for Failed to notify AF"errorStack": io.micrometer.core.instrument.ImmutableTag |
SM service can continuously log NullPointerException errors while running PA-CREATE or PA-UPDATE flows with sponsored data connectivity enabled. The failure occurs during AF notification metric handling and can flood logs while the signaling flow is active. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38590212 | Observing OCPM_PRE Pod is consuming more than 90% memory usage |
OCPM_PRE pods consumed more than 90% memory in one of the environment. This high memory usage can affect pod stability and operational headroom during policy service execution. Doc impact: There is no documentation impact. |
2 | 24.2.7 |
| 38729096 | Observing OCPM_PRE Pod is consuming more than 90% memory usage |
OCPM_PRE pods showed excessive memory consumption above 90% in one of the environment. This can create resource pressure and reduce service stability during runtime. Doc impact: There is no documentation impact. |
2 | 24.2.7 |
| 38751374 | Upgrading PCF from 25.1.200 to 25.1.201 "duplicate port definition with spec.template.spec.containers" |
PCF upgrade from 25.1.200 to 25.1.201 failed because of a duplicate port definition in the pod container specification. This can block the upgrade flow for AM-UE performance environments. Doc impact: There is no documentation impact. |
2 | 25.1.201 |
| 38758473 | Policy table rows silently missing when tested with 20 large tables |
Policy table processing missed rows when tested with multiple large policy tables. This can cause policy data to appear incomplete without a clear error indication. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38789247 | When one of pod of pcrf-core is in congestion state and overload condition hit we are seeing WARN "Exception occurred while applying overload control for backend BACKEND_PCRF_CORE" in diam-gateway |
Diameter gateway logged warnings while applying overload control when a pcrf-core pod is congested and overload conditions are reached. This can make overload handling for the BACKEND_PCRF_CORE backend appear to fail or behave inconsistently. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38813332 | SM pod is rejecting valid npcf-policyauth delete request and sending 415 Unsupported media type when content-length:0 and content-type header is not present |
SM service rejected a valid npcf-policyauth DELETE request with 415 Unsupported Media Type when the request has content-length 0 and no content-type header. This can incorrectly fail valid delete requests. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38839988 | For the UE service the congestion L1/L2/L3 thresholds are configured without any gap, which causes very rapid level fluctuations. |
UE service congestion thresholds for L1, L2, and L3 can be configured without sufficient separation. This can cause rapid congestion-level fluctuations and unstable congestion behavior. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38860927 | 500 "INTERNAL_SERVER_ERROR" logs in SM service generated by BulwarkServiceConnector |
SM service generated a 500 INTERNAL_SERVER_ERROR logs from BulwarkServiceConnector. This can add error noise and indicate failed backend connector handling during affected flows. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38870898 | GUI hangs when saving SNSSAI message attribute after fresh installation |
CNC Console did not respond when saving an Single Network Slice Selection Assistance Information (SNSSSAI) message attribute after a fresh installation. This can prevent you from completing the expected configuration save workflow. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38870925 | PCF respond with empty problem details body to AMF while PDS pod is unreachable and also kept stale UE policy session in DB while responding 500 to AMF |
PCF returned a 500 response with an empty problem details body to AMF when the PDS pod is unreachable. The same flow can leave a stale UE policy session in the database. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38885156 | PCF using expired token |
PCF continued using an expired token in affected call flows. This can cause authentication or authorization failures when communicating with dependent services. Doc impact: There is no documentation impact. |
2 | 25.1.200-1 |
| 38899915 | PCF not sending umDecs on receiving PA subscribe with event USAGE_REPORT and usgThres while send policyCtrlReqTriggers US_RE |
PCF exculded umDecs when receiving a PA subscribe request with the USAGE_REPORT event and usage threshold while sending the US_RE policy control request trigger. This can result in incomplete policy authorization subscription handling. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38918089 | After successful Gx and Sd session termination, PCRF not sending Sy session termination causing stale session for pdssubscriber & pdsprofile in PCF and eventually on OCS as well. |
PCRF failed to send Sy session termination after successful Gx and Sd session termination. This can leave stale pdssubscriber and pdsprofile sessions in PCF and eventually stale session state on OCS. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38922466 | Missing Mandate checks in RCManager in SM resulting NPE in GR Regression Test: triggerClass":"[ocpm.pcf.service.pa](http://ocpm.pcf.service.pa).domain.component.AfAdaptor","errorName":"java.lang.NullPointerException" |
SM service can encounter a NullPointerException in PA processing because required RCManager mandate checks are missing. This can affect GR regression flows involving AfAdaptor processing. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38922472 | PCF not sending reportingLevel=RAT_GR_LEVEL towards SMF for PA-UPDATE when sponStatus made AS SPONSOR_DISABLED |
PCF exculded reportingLevel=RAT_GR_LEVEL toward SMF during PA-UPDATE when sponsored status is set to SPONSOR_DISABLED. This can result in incomplete update notification data for the SMF. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38922499 | PA update request getting rejected even if in case NEF/AF need to update other parameter than sponsored data when ACCEPT_REQUEST_WHEN_MISSING_SPONSORED_CONNECTIVITY_DATA set to true |
PA update requests rejected even when NEF or AF update parameters other than sponsored data and ACCEPT_REQUEST_WHEN_MISSING_SPONSORED_CONNECTIVITY_DATA is enabled. This can incorrectly block valid Policy Authorization updates. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 38992796 | UDR subscription delete request in Model-D communication mode getting failed in UDR-conn due to http port:null in uri |
UDR subscription delete requests in Model-D communication mode can fail in UDR-Connector because the generated URI contains http port:null. This can prevent subscription cleanup in the affected communication mode. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39035473 | [GR_Testing]: SM service log is continuously printing "Exception occurred calling Bulwark Unlock" ERROR logs after upgrading to 25.2.200 build - patch 26.1.200 |
After upgrade, SM service continuously printed ERROR logs indicating an exception while calling Bulwark Unlock. This can create persistent error noise and indicate failed unlock handling in affected flows. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39069811 | Label error_reason for metrics occnp_oc_ingressgateway_http_responses_total resulting in high Cardinality |
The error_reason label for the occnp_oc_ingressgateway_http_responses_total metric created high cardinality. This can increase observability storage and query load for ingress gateway response metrics. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39071135 | update notify sent towards SMF for PA subscribe is disabling sponstatus by PCF |
PCF disabled sponsored status in the update notification sent toward SMF for a PA subscribe flow. This can send incorrect sponsored-connectivity state to SMF. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39082018 | Egress traffic increased for SMF notify after the upgrade from 25.1.201 to 25.2.200 |
SMF notify egress traffic increased after upgrade from 25.1.201 to 25.2.200. This can result in higher-than-expected outbound signaling volume for notification flows. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39082720 | testbed-PCF&UDR: Incorrect Next Reset Time and Grant for user with Billing Day 31 |
PCF and UDR calculated an incorrect next reset time and grant for you with billing day 31. This can produce incorrect quota or billing-cycle behavior for those subscribers. Doc impact: There is no documentation impact. |
2 | 24.2.8 |
| 39095272 | PCRF core with subs-to-notify false, PDS response is getting timed out causing Gx session create failure |
PCRF core timed out waiting for a PDS response when subs-to-notify is false. This can cause Gx session creation to fail in the affected flow. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39108818 | Exception while PATCH SmPolicyData at UDR Connector with 500 INTERNAL_SERVER_ERROR and thrown NullPointerException |
UDR Connector can throw a NullPointerException while handling PATCH SmPolicyData and return 500 INTERNAL_SERVER_ERROR. This can cause policy data patch requests to fail. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39109082 | PCF 25.1.202 Binding Service fails to look up BSF Profile with IP Ranges other than /64 |
PCF Binding Service failled to look up a BSF profile when the BSF IPv6 range uses a prefix other than /64. This can prevent BSF selection for NEF use cases that register broader IPv6 ranges such as /32. Doc impact: There is no documentation impact. |
2 | 25.1.202 |
| 39112907 | Congestion control for diam-connector is getting triggered at 55K TPS (SM call model) with default thresholds |
Diameter connector congestion control can trigger at 55K TPS with default thresholds in the SM call model. This can cause congestion discards earlier than expected under load. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39205123 | To reduce cardinality, egressLatencyBuckets configuration needs to be fine tuned for ocpm_egress_response_total |
The ocpm_egress_response_total metric had excessive cardinality because egressLatencyBuckets are configured too broadly across policy services. This can increase memory usage and observability overhead. Doc impact: There is no documentation impact. |
2 | 23.4.6 |
| 39213189 | NRF Cache Auditor Not Purging Entries as per Configured Percentage |
NRF cache auditor failed to purge cached discovery entries according to the configured purge percentage after the scheduler interval elapsed. Stale or excess cache entries can continue to be served instead of triggering fresh network discovery. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39224565 | Config-server restarts during DBTIER ndbappmysqld pods scaled down |
Config server pods can enter restart or CrashLoopBackOff behavior when DBTIER ndbappmysqld pods are scaled down. This can reduce service stability during DB tier unavailability or recovery. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 39354716 | SM Service fails to route to alternate SMF after 429 response from primary SMF |
SM Service can fail to route traffic to an alternate SMF after receiving a 429 response from the primary SMF. This can prevent expected alternate routing during primary SMF throttling or overload. Doc impact: There is no documentation impact. |
2 | 25.2.200 |
| 37740602 | ES3XX feature is mentioned as Not supported under 4.2.4.3 Request for termination of the policy association section, but ES3XX feature is not included under Not supported category under 4.2.4.2 section in PCF Compliance Matrix |
The PCF Compliance Matrix lists ES3XX support inconsistently across related sections. You can see ES3XX marked unsupported in one section while it is missing from the unsupported category in another section. Doc impact: There is no documentation impact. |
3 | 25.1.100 |
| 37897111 | The tier condition block is not available under PCRF-CORE service blockly |
The tier condition block is not available under the PCRF-Core service blockly interface. You can be unable to configure tier-based PCRF-Core logic through the expected visual block. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 37983361 | Multiple issues on Table 2-372 of REST API guide. |
Table 2-372 in the REST API guide contains multiple documentation issues. You can receive unclear or inaccurate REST API reference information from that table. Doc impact: Updated the Binding Service section in Oracle Communications Cloud Native Core, Converged Policy REST Specification Guide. |
3 | 25.1.200 |
| 38316856 | policy_installation_guide_25.1.200 Note in section 5.11.d not clear |
A note in section 5.11.d of the Policy Installation Guide is unclear. You can misinterpret the documented installation guidance for that section. Doc impact: Updated the Preupgrade Tasks section in Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.1.200 |
| 38508960 | CNC policy installation & Upgrade document Discrepancy 25.1.200 |
The CNC Policy installation and upgrade documentation contains inconsistent guidance for 25.1.200. You can follow conflicting information during installation or upgrade activities. Doc impact: Updated the Preupgrade Tasks section in Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.1.200 |
| 38645027 | Importing 23.x Profiles into 25.x |
Profile import guidance or behavior for importing 23.x profiles into 25.x is incomplete or unclear. You can encounter issues when migrating older profiles into a newer release. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38689474 | Uploaded Single UE ID MOP to update Rollback section |
The Single UE ID MOP rollback section required correction. You can receive incomplete or unclear rollback guidance for the Single UE ID procedure. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38695883 | FD is missing important information related to enhance warn logging on diameter interface |
The feature document is missing important information about enhanced warning logging on the Diameter interface. You can lack required context for understanding or configuring Diameter warning logs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38721106 | SD CCR-T without session id should failed with error 5005 DIAMETER_MISSING_AVP and causing NPE error |
An SD CCR-T request without a session ID can trigger a NullPointerException instead of failing cleanly with DIAMETER_MISSING_AVP error 5005. This can produce incorrect Diameter error handling for malformed requests. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38735637 | Wrong accept=[application/json] header sent to CHF in subscription delete request by PCF will cause issue with real CHF |
PCF sent an incorrect accept=[application/json] header to CHF in subscription delete requests. This can cause interoperability issues with a real CHF implementation. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38738240 | CPU utilization of UE service has increased by ~40% after in-service upgrade to 25.2.200 from 25.2.100 |
UE service CPU utilization can increase by approximately 40% after an in-service upgrade from 25.2.100 to 25.2.200. This can reduce performance headroom for UE service after upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38761727 | In case 3gpp-Sbi-Sender-Timestamp received in incorrect format SM service not able to create PDS set request and call fail |
SM service failed to create a PDS set request when the 3gpp-Sbi-Sender-Timestamp header is received in an incorrect format. This can cause the affected call flow to fail. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38776742 | Subscription-Id-Type is END_USER_SIP_URI , enhance warn log does not show subscription id details for diam error code 5009 |
Enhanced warning logs for Diameter error code 5009 do not show subscription ID details when Subscription-Id-Type is END_USER_SIP_URI. This can make troubleshooting subscription-related Diameter errors harder. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38779098 | UDR connector not adding 3gpp-sbi-correlation-info while sending discovery request to nrf-client-nfdiscovery |
UDR connector excluded 3gpp-sbi-correlation-info when sending discovery requests to nrf-client-nfdiscovery. This can reduce correlation visibility for NRF discovery traffic. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38779120 | SPAD_PERF[AM-UE-Perf]- Executing ~54K TPS for long run leads to frequent ERROR in bulwark svc "java.lang.RuntimeException" |
Long-running AM-UE performance traffic at around 54K TPS can cause frequent RuntimeException errors in the Bulwark service. This can add persistent error logging during high-throughput performance runs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38783864 | WARN logs for Binding Audit: Revalidation successfully changed across 25.2.100 vs 25.2.200 |
Binding Audit revalidation warning logs differed unexpectedly between 25.2.100 and 25.2.200. This can make audit revalidation behavior appear inconsistent across releases. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38787767 | Diam-conn: NullPointerException (key is null) causes 5012 rejection of PcfSdEvent during Performance |
Diameter connector throwed a NullPointerException when a key is null, causing PcfSdEvent rejection with error 5012 during performance testing. This can interrupt affected Diameter event handling. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38788906 | Subscriber Activity logs for UDR GET/POST/DELETE request missing apiroot in uri field |
Subscriber Activity logs for UDR GET, POST, and DELETE requests can omit the apiRoot value in the URI field. This can make request tracing and troubleshooting incomplete. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38796704 | For PDS session audit query sent for Gx session to PCRF-core, PCRF core return 404 for Gx session while session was active in DB |
PCRF-Core returned a 404 for a PDS session audit query for a Gx session even though the session is active in the database. This can cause audit results to incorrectly indicate that an active session is missing. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38817020 | [GR_Testing]:Policyds_Overall_Processing_time_Seconds is reaching nearly 3 seconds during audit notification handling thus causing "Unexpected error occurred: Scheduler unavailable errors at PDS |
PolicyDS overall processing time approached three seconds during audit notification handling, causing scheduler-unavailable errors at PDS. This can delay or disrupt audit notification processing. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38817267 | Abnormal restarts have been observed on ocpcf-oc-diam-gateway-5 pod on site-2 with during ndbmtd pod restart scenario lead to traffic loss |
The ocpcf-oc-diam-gateway pod restarted abnormally during an ndbmtd pod restart scenario on site 2. This can lead to traffic loss during the affected DB pod restart condition. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38827482 | NPE seen in sm-service after upgrade with error message Cannot invoke "java.util.Map.get(Object)" because the return value of "[ocpm.pcf.service.sm](http://ocpm.pcf.service.sm).domain.model.SmPolicyAssociation.getQosDatas()" is null"," |
SM service can throw a NullPointerException after upgrade when SmPolicyAssociation QoS data is null. This can interrupt affected SM policy processing after upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38828870 | PCF doesn't send RAR with FRA to AF even though the RxReauth action SEND_RAR is getting applied |
PCF failed to send an RAR with FRA to AF even when the RxReauth action SEND_RAR is applied. This can prevent the expected reauthorization request from reaching AF. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38846947 | [GR_Testing]: Observing audit pod is restarting with OOM in longevity run at approximately 3 days 6 hours intervals |
The audit pod restarted with an out-of-memory condition during longevity runs at roughly three-day intervals. This can affect long-running audit service stability. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38872036 | Change in dimensions of ocpm_ingress_request_total metric causing UE service congestion validation failure |
A change in ocpm_ingress_request_total metric dimensions can cause UE service congestion validation to fail. This can make congestion validation unreliable when using the affected metric. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38883699 | Audit cleanup/delete metrics are not getting updated on binding service while session got removed due to audit |
Binding service audit cleanup and delete metrics can fail to update when a session is removed by audit processing. This can leave monitoring data inconsistent with actual session cleanup activity. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38883715 | Audit service pod is throwing "Error saving TimerPodStateEntities" Error after upgrading to 25.2.200. |
Audit service pods can log errors while saving TimerPodStateEntities after upgrade to 25.2.200. This can indicate failed timer pod state persistence after upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38885830 | OpenSpec API Compile Time Warnings |
OpenSpec API generation can produce compile-time warnings. This can indicate inconsistencies in the API specification that affect generated API artifacts. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38898205 | Few HTTP error codes eg. 415 and 406 are not reaching controllers |
Certain HTTP error codes, including 415 and 406, can fail to reach the application controllers. This can prevent controller-level handling for those error conditions. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38901026 | GUI PCRF-CORE Advanced Setting: DIAMETER.AF.SessionBindingAltKeys |
The GUI advanced setting for DIAMETER.AF.SessionBindingAltKeys under PCRF-Core is not documented or exposed clearly. You can miss or misconfigure the session binding alternate key setting. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38903093 | Update overload threshold values for AM, UE, SM, PCRF-Core, Diam-Connector |
Overload threshold values for AM, UE, SM, PCRF-Core, and Diameter Connector are not aligned with the expected configuration. This can cause overload behavior to trigger at unintended levels. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38941633 | Diam-GW assigns default message priority even when no priority profile is attached, preventing validation of "IfNotPresent" Request Priority Override |
Diameter Gateway assigned a default message priority even when no priority profile is attached. This can prevent correct validation of the IfNotPresent request-priority override behavior. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38973595 | PCF 25.2.100 : Table 7-47 ("SM Policy Association Section of Audit Group") incorrectly lists the TDF parameters |
Table 7-47 in the PCF guide incorrectly lists TDF parameters in the SM Policy Association section of the Audit Group. You can receive incorrect parameter guidance from the documentation. Doc impact: Updated the PCF Session Management section in Oracle Communications Cloud Native Core, Converged PolicyUser Guide. |
3 | 25.2.100 |
| 39063863 | [Generic_Policy]: occnp_oc_ingressgateway_incoming_connections metric details are missing in user guide |
The User Guide does not include details for the occnp_oc_ingressgateway_incoming_connections metric. You can lack the information needed to monitor incoming ingress gateway connections. Doc impact: Updated the Ingress Gateway Metrics section in Oracle Communications Cloud Native Core, Converged Policy Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.2.100 |
| 39064093 | [Generic_Policy]: Handling_DB_Cluster_Disconnect feature documentation is missing in user guide |
The User Guide does not include documentation for the Handling_DB_Cluster_Disconnect feature. You can be unaware of the feature behavior or required operational guidance. Doc impact: Updated the PCF Session Management section in Oracle Communications Cloud Native Core, Converged PolicyUser Guide. |
3 | 25.2.100 |
| 39083388 | Npcf_AMPolicyControl_TerminateNotify Resource URI details incorrect in User Guide |
The User Guide contains incorrect resource URI details for Npcf_AMPolicyControl_TerminateNotify. You can use the wrong URI when implementing or validating terminate-notify behavior. Doc impact: Updated the Policy Services section in Oracle Communications Cloud Native Core, Converged Policy User Guide. |
3 | 25.2.200 |
| 39084971 | [CNCESPOL-7335] [GR_Testing]: NPE observed in cm-service with error "Cannot invoke "Object.toString()" because the return value of "java.util.LinkedHashMap.get(Object)" is null" |
CM service can throw a NullPointerException when a LinkedHashMap lookup returns null and the service attempts to call toString on it. This can cause errors during the affected generic policy flow. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39187168 | InfoDev :: Update - Policy User Guide : SAL limitation for subscription expiry audit notification |
The Policy User Guide does not clearly describe the SAL limitation for subscription-expiry audit notifications. You can miss the documented limitation when planning or troubleshooting audit notification behavior. Doc impact: Updated the Expiry Handling for Policy Data Subscriptions section in Oracle Communications Cloud Native Core, Converged Policy User Guide. |
3 | 25.2.200 |
| 39238447 | [SM_OCE_Phase2_Assume_Positive]: CM UI/SUT Allows Import of Higher Version (n+1) configuration into Lower Version (n) without Validation |
CM UI/SUT can allow a higher-version configuration to be imported into a lower-version system without validation. This can permit unsupported configuration downgrade scenarios. Doc impact: There is no documentation impact. |
3 | 25.2.201 |
| 39280735 | Advanced key for TDF enabling is wrong TDF.TDF_ENALBLED in SM Service configuration in User Guide at multiple places |
The User Guide lists the SM Service TDF enablement advanced key incorrectly as TDF.TDF_ENALBLED in multiple places. You can configure the wrong key when enabling TDF behavior. Doc impact: There is no documentation impact. |
3 | 25.2.201 |
| 39440075 | Duplicate policyds.mySql.connection block in 25.2.201 custom values overrides dynamic DB pool sizing |
A duplicate policyds.mySql.connection block in 25.2.201 custom values can override dynamic database pool sizing. This can cause PolicyDS to use unintended DB connection settings. Doc impact: There is no documentation impact. |
3 | 25.2.201 |
| 39573249 | While Doing DB Inservice Upgrade when DB pods are initializing PDS is throwing NPE :Cannot invoke "ocpm.uds.policyds.db.entity.PdsTableWrapper.setLstPdsSubs(java.util.List)" |
PDS can throw a NullPointerException during DB in-service upgrade while DB pods are initializing. This can affect policy data service behavior during the database upgrade window. Doc impact: There is no documentation impact. |
3 | 25.2.201 |
| 35776567 | PCF should add npcf-policyauthorization service on default custom yaml section appProfiles. |
The default custom YAML appProfiles section can omit the npcf-policyauthorization service. This can require manual configuration before policy authorization service profiles are available. Doc impact: There is no documentation impact. |
3 | 23.2.0 |
| 37324111 | ERRORS & Exceptions observed in PDS Logs during UsageMon Performance Runs |
PDS logs can contain errors and exceptions during UsageMon performance runs. This can indicate unstable behavior or noisy error logging under performance traffic. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 38291688 | PCF is not rejecting the Policy association request with valid error cause for invalid/incorrect conditional attributes |
PCF can reject policy association requests with invalid or incorrect conditional attributes without returning the expected valid error cause. This can make request failures unclear to clients. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38305437 | N CNE - Helm Warnings observed when installing/uninstalling and upgrading Policy on N CNE cluster |
Helm warnings can appear during Policy installation, uninstallation, or upgrade on an N CNE cluster. This can make lifecycle operations look problematic even when they should proceed normally. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38418947 | UE service is registering with Audit service where Audit is disabled by default on Fresh installation 25.2.100 when slicing enabled |
UE service can register with Audit service on a fresh installation even though Audit is disabled by default when slicing is enabled. This can create unintended audit-service registration behavior. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38617440 | [Rx_Enhancement_AVP_Phase2]: Metric occnp_ocnf_service_cookie_total (direction="out") only pegged when AAR-U received with ocnfservicecookie header |
The occnp_ocnf_service_cookie_total metric with direction=out can be pegged only when AAR-U includes the ocnfservicecookie header. This can make service-cookie metric reporting incomplete for other affected flows. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38648280 | : bulkexport & export report are incorrect when one of the policy project is missing with dependancy |
Bulk export and export reports can be incorrect when a dependent policy project is missing. This can give you inaccurate export results for incomplete project dependencies. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38691549 | POLICY_READ Role enabled but user is also able to edit the parameters |
You can still edit parameters with the POLICY_READ role. This can allow changes from a role that should have read-only access. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 38696528 | PRE: Release variables that hold references and optimize the creation of policyTableMap, ensuring it does not retain unnecessary references |
PRE can retain unnecessary references while creating policyTableMap. This can contribute to excessive memory retention during policy table processing. Doc impact: There is no documentation impact. |
3 | 24.2.7 |
| 38714868 | From CNCESPOL-6097 High Memory Alerts for PRE |
PRE can generate high-memory alerts under affected conditions. This can indicate elevated memory usage and reduced resource headroom. Doc impact: There is no documentation impact. |
3 | 25.1.201 |
| 38747169 | Unable to edit/download Yaml Schema to modify Blockly for DNNReplacement feature |
Unable to edit or download the YAML schema needed to modify Blockly for the DNNReplacement feature. This can block configuration changes for that feature. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38823032 | PCF is rejecting SM Policy Request with 500 Internal Server Error when a mandatory IE SUPI is missing in the request |
PCF returned 500 Internal Server Error when an SM Policy request is missing the mandatory SUPI information element. This can produce an incorrect server error instead of a clear client-side validation response. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38823361 | PCF is not sending UpdateNotify to SMF to remove the pcc rule installed during AAR-I |
PCF failed to send UpdateNotify to SMF to remove a PCC rule installed during AAR-I. This can leave policy rules active when they should have been removed. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38898259 | occnp_pod_congestion_state metric is not getting generated for PCRF Service |
The occnp_pod_congestion_state metric failed to generate for PCRF Service. This can prevent expected congestion-state monitoring for PCRF. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38909860 | There are no warning or error-level logs in DGW that indicate the cause of load level changes—for example, whether they’re due to CPU usage or pending_request_count |
Diameter Gateway can change load levels without warning or error logs explaining whether the cause is CPU usage or pending request count. This can make load-level changes difficult to diagnose. Doc impact: There is no documentation impact. |
3 | 24.2.9 |
| 38935609 | [Soltest-25-C] [Diam-Cli]: Diamcli fails to send the RAA success response to PCF when sending 3gpp-User-Location-Info AVP from PCF (diam-connector) |
Diamcli failed to send the RAA success response to PCF when PCF sends the 3gpp-User-Location-Info AVP through Diameter Connector. This can disrupt Rx reauthorization response handling. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38936767 | For Cause "NOT_ACCEPTABLE" response Body doesn't contain the cause for the failure & error state code. |
Responses with cause NOT_ACCEPTABLE can omit the failure cause and error state code from the response body. This can leave clients without the expected problem details. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38943008 | 25.2.200-: In the Default CV file of 25.2.200 (CSAR) , concurrency for istio container of all the Microservices is not mentioned |
The default CV file in the 25.2.200 CSAR does not mention Istio container concurrency for all microservices. This can leave deployment configuration incomplete or unclear. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38964293 | Voice Call model- Observed multiple Policy microservice container restart during the PCF upgrade from 25.1.200 to 25.2.200 |
Multiple Policy microservice containers can restart during PCF upgrade from 25.1.200 to 25.2.200 in the BT Voice call model. This can affect service stability during upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38970033 | With READ_ONLY user CNCC prompt "Profile named DEFAULT is activated successfully" for Congestion Profile switch and Load Shedding Rules copy etc |
With the READ_ONLY role, you can receive successful action prompts for operations such as congestion profile switch or load-shedding rule copy. This can incorrectly indicate that the read-only role performed configuration actions. Doc impact: There is no documentation impact. |
3 | 25.1.202 |
| 38973947 | Config server pods are getting stuck and not processing any requests after restarting 1 out of 2 config server pods with 55K TPS traffic (SM Call Model) |
Config server pods can become stuck and stop processing requests after one of two pods is restarted under 55K TPS SM call-model traffic. This can affect configuration service availability under load. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38985407 | UE- Validation is not there for notificationURI in update request |
UE service update requests can lack validation for notificationURI. This can allow invalid notification URI values to be accepted. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 39066800 | Need an alert off of “oc.egressgateway.resolve.fqdn.from.ars.failure” metric when EGW encounter DNS SRV resolution failure |
Egress Gateway does not provide the expected alert based on oc.egressgateway.resolve.fqdn.from.ars.failure when DNS SRV resolution fails. This can leave DNS SRV failures without the intended operational notification. Doc impact: There is no documentation impact. |
3 | 24.2.4 |
| 39082749 | pcrf-core: change default value for configurations for unsolicited messages routing via diam-gw |
PCRF-Core default configuration for unsolicited message routing through Diameter Gateway can use an unintended value. This can cause unsolicited messages to follow the wrong routing behavior by default. Doc impact: There is no documentation impact. |
3 | 25.1.100 |
| 39092757 | AM service: PCF is sending wrong Content-Type: application/problem+json header for successful response |
AM service responses from PCF can use the problem-details content type for successful responses. This can give clients an incorrect Content-Type header for successful AM policy operations. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39098879 | Removing the duplicate diamGatewayEnable parameter under the custom.yaml |
custom.yaml can contain a duplicate diamGatewayEnable parameter. This can make Diameter Gateway enablement configuration ambiguous. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39125512 | Update policy upgrade guide to inculde newly introduced table i.e. occnp_pcf_sm.TdfSession in existing replication group |
The Policy Upgrade Guide does not include the newly introduced occnp_pcf_sm.TdfSession table in the existing replication group guidance. This can leave upgrade replication instructions incomplete. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39125875 | Incorrect NFType label value in oc_egressgateway_http_responses_total metric |
The oc_egressgateway_http_responses_total metric can report an incorrect NFType label value. This can make metric filtering and attribution inaccurate. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39136398 | UDR patch request failed on GR site-2 EGW with error 3gpp-sbi-target-apiroot header is missing on minimal performance run of 1K TPS on Dual Stack setup |
UDR PATCH requests can fail on GR site-2 Egress Gateway with a missing 3gpp-sbi-target-apiroot header during a 1K TPS dual-stack performance run. This can disrupt UDR update traffic in that setup. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39386429 | PolicyDs: problem while removing oldest context from context_info on exceeding column size |
PolicyDS can have trouble removing the oldest context from context_info when the column size is exceeded. This can prevent proper context cleanup when stored context data grows too large. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 39604232 | Internal server error importing a big file of Data Limit Profile json |
CNC Console returned an internal server error when importing a large Data Limit Profile JSON file. This can prevent successful import of large profile data. Doc impact: There is no documentation impact. |
3 | 25.1.202 |
| 39604527 | cnPCRF is adding an undesired custom AVP in Sy interface |
cnPCRF added an undesired custom AVP on the Sy interface. This can send unexpected Diameter AVP data to peer systems. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39615975 | PCF 25.2.100: Repeated Firing/Resolved Notifications for SYSTEM_OPERATIONAL_STATE_PARTIAL_SHUTDOWN Alert |
PCF can repeatedly fire and resolve notifications for the SYSTEM_OPERATIONAL_STATE_PARTIAL_SHUTDOWN alert. This can create alert noise and make the operational state harder to interpret. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 37721161 | AN-Trusted AVP is not getting included in AAA response from PCRF for given specific RAT-Type |
PCRF can omit the AN-Trusted AVP from AAA responses for a specific RAT-Type. This can produce incomplete Diameter response data for affected access-type scenarios. Doc impact: There is no documentation impact. |
3 | 25.1.100 |
| 37746896 | When N7 Delete is received to SM service then Get PDS/v2/user-data is triggered although queryUseronDelete=false is configured |
SM service can trigger a PDS /v2/user-data GET request when an N7 Delete is received even though queryUserOnDelete is configured as false. This can cause unnecessary user-data queries during delete handling. Doc impact: There is no documentation impact. |
3 | 24.2.4 |
| 37757536 | Able to update the exclude DNN flags in advancedSettings of PCF Session Management service configuration using common service API with leading & trailing spaces |
The common service API can allow exclude DNN flags in PCF Session Management advanced settings to be updated with leading or trailing spaces. This can result in malformed or unintended configuration values. Doc impact: There is no documentation impact. |
3 | 24.2.4 |
| 38417366 | msg_type="SNR" parameter is missing from metric occnp_diam_congestion_message_reject_total |
The occnp_diam_congestion_message_reject_total metric can omit the msg_type="SNR" parameter. This can make Diameter congestion rejection metrics incomplete for SNR messages. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38526952 | Retry Feature enabled in App-Info but it is marking cluster as failed |
App-Info can mark the cluster as failed even when the retry feature is enabled. This can report an incorrect cluster failure state during retry handling. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38526975 | Assume Positive property in app-info is enabled but it is marking cluster as failed |
App-Info can mark the cluster as failed even when the assume positive property is enabled. This can incorrectly report cluster failure despite the configured positive-assumption behavior. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38587466 | [Generic_Policy]:Retain/Ignore option is replacing the old configuration with the new configuration in PDS settings screen |
The Retain or Ignore option in the PDS settings screen replaced the existing configuration with the new configuration. This can cause retained settings to be overwritten unexpectedly. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38590615 | Even Query User on Terminate=False, SM sending GET request for smPolicyData (in case earlier POST subs-to-notify failed) |
SM service can send a GET request for smPolicyData even when Query User on Terminate is false if an earlier POST subs-to-notify request fails. This can trigger an unexpected data query during termination handling. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38608724 | [GENERIC_POLICY]:ocLogID is missing in AM Service Logs for the Response Messages received from PolicyDS and PRE Services. |
AM Service logs can miss ocLogID values for response messages received from PolicyDS and PRE services. This can make response-message tracing harder across services. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38705518 | [PA_SPONSOR_DATA_CONNECTIVITY_UPDATE_USAGE_REPORT]: sponId and aspId value changed in update_notify on PA-Subscribe request |
sponId and aspId values can change in update_notify messages for a PA-Subscribe request in the sponsored data connectivity usage-report flow. This can send inconsistent sponsor identity data. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38718734 | The "sender" field in the enhanced warning log is not showing the correct binding-pod name in the diam-gateway pod when error 5065 comes from the binding pod during the context-owner query. |
Diameter Gateway enhanced warning logs can show the wrong binding-pod name in the sender field when error 5065 came from the binding pod during a context-owner query. This can make the source of the error difficult to identify. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38741355 | java.lang.NullPointerException observed while binding triggers re-validation for binding session with GR site2 BSF |
Binding session revalidation with GR site2 BSF can trigger a NullPointerException. This can interrupt binding revalidation processing for affected sessions. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38771910 | allowedSnssais is missing from request section of AM Create Response when DNNReplacement and SliceSupport is disabled |
allowedSnssais can be missing from the request section of the AM Create response when DNNReplacement and SliceSupport are disabled. This can produce incomplete AM policy response data. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38837486 | invalidParams field is not correct when SM service is rejecting PA- Create request with invalid "notifURI" |
SM service can populate the invalidParams field incorrectly when rejecting a PA-Create request with an invalid notifURI. This can give clients inaccurate validation details. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38857919 | [GR_Testing]: Observing "Exception handling failed. Message: For input string: "INTERNAL_SERVER_ERROR"" error in PDS logs when audit notification is received and sm-service pod is in congestion |
PDS logs can show an exception-handling failure when an audit notification is received while the SM service pod is congested. The error can occur while handling an INTERNAL_SERVER_ERROR string value. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38885139 | [GR_Testing]: NPE seen in sm-service with reason: "message":"Cannot invoke "[ocpm.pcf.service.pa](http://ocpm.pcf.service.pa).domain.model.AppSession.isFeatureNegotiated(int)" because "appSession" is null" |
SM service can throw a NullPointerException when appSession is null during feature-negotiation checks. This can interrupt affected policy authorization processing. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38885174 | Alert UPDATE_NOTIFY_FAILURE_ABOVE_50_PERCENT is not getting fired |
The UPDATE_NOTIFY_FAILURE_ABOVE_50_PERCENT alert can fail to fire when the configured failure condition is met. This can leave update-notify failure spikes without the expected alert. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38899895 | The value of the sponId/aspId dimensions is not coming as "NotSpecified" when SYSTEM.INCLUDE_SPONID_ASPID_DIMENSIONS is false |
The sponId and aspId metric dimensions can fail to report NotSpecified when SYSTEM.INCLUDE_SPONID_ASPID_DIMENSIONS is false. This can produce unexpected metric dimension values. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38930756 | Prometheus cardinality control for the metric occnp_pa_sponsored_sessions_total is not enforced when the number of calls is below the configured SPONID_ASPID_PAIR_CARDINALITY_LIMIT value |
Prometheus cardinality control for occnp_pa_sponsored_sessions_total can fail to apply when call volume is below the configured SPONID_ASPID_PAIR_CARDINALITY_LIMIT. This can allow higher-than-expected metric cardinality. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38980990 | UDR-Notification is failing if "Charging Profile selection based on Notification - UDR" workflow is enabled |
UDR notifications can fail when the Charging Profile selection based on Notification - UDR workflow is enabled. This can disrupt notification-driven charging profile selection. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39059680 | SM service is not printing framedIpAddress, calledStationId, sessionId, reciever items correctly in enhanced WARN log |
SM service enhanced WARN logs can print framedIpAddress, calledStationId, sessionId, and receiver values incorrectly. This can reduce the usefulness of warning logs for troubleshooting. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39061348 | Oclog id is missing in server response(SAL is on) for PA-UPDATE when call failed as 403 REQUESTED_SERVICE_NOT_AUTHORIZED |
ocLogId was missing from the server response for PA-UPDATE failures with 403 REQUESTED_SERVICE_NOT_AUTHORIZED when SAL is enabled. This can make failed request correlation harder. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39064208 | [GR_Testing]: Session viewer displaying incorrect Creation Time in case of UE policy create request |
Session Viewer displayed an incorrect creation time for UE policy create requests. This can show misleading session timing information to you. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39064258 | occnp_dnn_replacement_total metrics is not update AM create response when UDR send "olddnn"= null for AM data for DNN_replacement feature |
The occnp_dnn_replacement_total metric failed to update for AM create responses when UDR sends olddnn as null for DNN replacement data. This can make DNN replacement metric reporting incomplete. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39070829 | ocLogId is not contained in enhanced log of diam-connector logs during SY 3002 error response from diam-gw - 26.1.200 |
Diameter Connector enhanced logs can omit ocLogId during Sy 3002 error responses from Diameter Gateway. This can make error correlation harder for Sy response handling. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39096625 | Multiple issue is observed in SM service enhanced log when 5030 error received in SLA response from OCS |
SM service enhanced logs contained multiple issues when a 5030 error is received in an SLA response from OCS. This can make OCS error handling harder to diagnose. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39096801 | The occnp_http_congestion_message_reject_total metrics has "message priority" dimenesions diff as "priority" and "message_priority" in different micro services |
The occnp_http_congestion_message_reject_total metric can use inconsistent message-priority dimension names across microservices. This can make congestion rejection metrics harder to query consistently. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39123731 | With high rate SM calls (minimal performance 1k or more TPS), wrong ocLogId mapped for same transaction in udr-conn logs |
UDR Connector logs mapped the wrong ocLogId for the same transaction under high-rate SM call traffic of 1K TPS or more. This can break log correlation for affected transactions. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39589081 | ASR not triggered by PCF on UpdateNotify failure for AAR-I without Media-Type when it mismatches the media type in Rx Reauth profile with Suppress-ASR - patch 26.1.200 |
PCF can fail to trigger ASR after an UpdateNotify failure for AAR-I without Media-Type when the request mismatched the Rx Reauth profile media type with Suppress-ASR. This can leave the expected session cleanup or notification behavior incomplete. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 37329590 | Occasionally during CHF or UDR notification ocLogID missing from SM Service for GET request towards PDS |
SM Service logs occasionally missed the ocLogID values for GET requests to PDS during CHF or UDR notification handling. This can make request tracing incomplete. Doc impact: There is no documentation impact. |
3 | 24.3.0 |
| 37375563 | PCF is not sending CHF delete for 1st message received during race condition |
PCF failed to send a CHF delete for the first message received during a race condition. This can leave charging-related cleanup incomplete for that flow. Doc impact: There is no documentation impact. |
3 | 24.2.0 |
| 37637352 | No ocLogID in UDR (other NF) response in egress gateway subscriber tracing logs |
Egress Gateway subscriber tracing logs can omit ocLogID for UDR or other NF responses. This can make cross-service response tracing incomplete. Doc impact: There is no documentation impact. |
3 | 25.1.100 |
| 38190543 | Lots of UE services logs missing ocLogID for N1N2 Subscription or N1N2 Transfer failures and RAB attempts |
UE service logs missed ocLogID values for N1N2 subscription failures, N1N2 transfer failures, and RAB attempts. This can make troubleshooting those UE flows harder. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38502162 | ocLogID missing in SM-Service logs for GET from DIAM-Conn to SM service for PA policy GET |
SM-Service logs excluded ocLogID for PA policy GET requests initiated from Diameter Connector. This can break log correlation for those Diameter-to-SM requests. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38521967 | Policy 25.2.100 - IllegalArgumentException observed on pcrf-core service after upgrade and rollback between 25.1.200 and 25.2.100 |
PCRF-Core throwed an IllegalArgumentException after upgrade and rollback between 25.1.200 and 25.2.100. This can affect service behavior after rollback scenarios. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38568991 | [Generic_Policy]: NPE seen in sm-service during audit notification flow towards SMF |
SM service throwed a NullPointerException during audit notification flow toward SMF. This can interrupt audit notification handling for affected sessions. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38618037 | [Generic_Policy]: AM service deletion is not happening and AM service logs are flooding with NPE when ASSOCIATIONID in Enabled |
AM service deletion failed and AM service logs was flooded with NullPointerException errors when ASSOCIATIONID is enabled. This can prevent cleanup and create excessive error logging. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38638225 | [Generic_Policy]: PDS settings default fields are not reflecting in GET and EXPORT requests output from Swagger |
PDS settings default fields was missing from GET and EXPORT request output in Swagger. This can make exported or retrieved PDS settings appear incomplete. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38674636 | [GR_Testing]: Observing audit service reporting different counts in different audit service pods for metric: oc_db_active_session_count metric |
Audit service pods reported different oc_db_active_session_count values for the same environment. This can make active-session monitoring inconsistent across pods. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38689892 | Enhance error details CauseCode for REQUESTED_SERVICE_NOT_AUTHORIZED sent as 0000 UNKNOWN |
Error details for REQUESTED_SERVICE_NOT_AUTHORIZED reported CauseCode as 0000 UNKNOWN. This can give clients unclear or incorrect failure cause information. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38693201 | PolicyDS: Handle Monotonic Increment of last_modified_time for Conflict Resolution During DB Updates |
PolicyDS database updates failed to maintain a monotonic last_modified_time value for conflict resolution. This can make update ordering and conflict handling unreliable. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38693414 | Binding: Prevent Time Drift by Enforcing Monotonic Increment of lastModifiedTime column value During DB Update Operations |
Binding database updates allowed lastModifiedTime values to drift instead of increasing monotonically. This can affect conflict resolution or update ordering. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38700733 | msgtype and appytype are diameter related but also include POST and URI which is for http in diam connecotor |
Diameter Connector logs or fields for msgtype and apptype can include HTTP-specific values such as POST and URI. This can mix Diameter and HTTP semantics in diagnostic data. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38706710 | [GR_Testing]: Audit dequeue rate is going beyond the configured notification rate in audit registration |
Audit dequeue rate exceeded the configured notification rate in audit registration. This can cause audit notifications to be processed faster than the configured limit. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38718607 | "sender" field in enhance warn log is adding k8 node name in diam-gateway pod for error 5012 |
Diameter Gateway enhanced warning logs populated the sender field with the Kubernetes node name for error 5012. This can make the logged sender identity incorrect. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38768694 | NPE is seen in audit service during inservice upgrade from 25.2.100GA to 25.2.200. |
Audit service throwed a NullPointerException during in-service upgrade from 25.2.100 to 25.2.200 . This can affect audit service stability during upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38787919 | [GR_Testing]: Observing Audit service pod restart after performing upgrade to 25.2.200 |
Audit service pods restarted after upgrade to 25.2.200 . This can affect audit service availability during or after upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38796358 | [GR_Testing]: NPE seen in policyds with ERROR "Cannot invoke "java.util.List.forEach(java.util.function.Consumer)" because the return value of "getPdsProfileData()" is null" |
PolicyDS throwed a NullPointerException when pdsProfileData is null and the service attempted to iterate over it. This can interrupt affected policy data processing. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38819116 | Infra Validation is not working for minViablePath feature during upgrade scenario for ocnrf |
Infrastructure validation for the minViablePath feature failed during an OCNRF upgrade scenario. This can leave upgrade validation incomplete for that feature. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38877018 | (PCF:25.2.200)AM Service Reports a Warning "Error found in Bulwark Unlock Request: null" full exception and stack trace do not get printed as Enhanced Logging is not present |
AM Service logged a Bulwark Unlock warning with a null error while omitting the full exception and stack trace. This can make the underlying failure difficult to diagnose. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38902416 | Diam-connector is printing error log "Timestamp cannot be processed because dateString is: 2025-07-04T09:50Z" during SM performance run |
Diameter connector printed a timestamp-processing errors during SM performance runs. This can add error noise and indicate that valid timestamp formats are not handled correctly. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38909233 | Remove unused helm parameter isIpv6Enabled |
The Policy Helm chart contains an unused isIpv6Enabled parameter. This can create configuration confusion because the parameter appears available but has no useful effect. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38914302 | The error response format does not match the expected Problem Details structure in binding microservice |
Binding microservice error responses failed to match the expected Problem Details structure. This can give API clients inconsistent or nonstandard error payloads. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38930363 | PCF is sending 3gpp-sbi-discovery-target-nf-set-id: with no value/null value to BSF for pcfbinding create request while same not found |
PCF sent an empty or null 3gpp-sbi-discovery-target-nf-set-id header to BSF during pcfBinding create requests. This can send invalid discovery metadata in binding traffic. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38930703 | [Systemic] Fix QueryTypeMismatchException in JPQL COUNT() queries (Hibernate 6.6 Migration) |
JPQL COUNT queries throwed QueryTypeMismatchException after Hibernate 6.6 migration. This can break database query paths that relied on COUNT results. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38948315 | PCF UE service rejecting N1N2 notification with incorrect error code while json format is invalid |
PCF UE service rejected N1N2 notifications with an incorrect error code when the JSON format is invalid. This can give clients misleading validation failures. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38948483 | Post GRR table mismatch has been found in occnp_overload2.leader_election table. |
A table mismatch appeared in the occnp_overload2.leader_election table after GRR. This can indicate inconsistent leader-election state after recovery or replication. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39027875 | [GR_Testing][intermittent]: Policy upgrade failing due to EGW failed to connect to database while upgrading from 25.1.200 to 25.2.101 |
Policy upgrade failed intermittently when Egress Gateway cannot connect to the database during upgrade from 25.1.200 to 25.2.101. This can interrupt upgrade completion. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 39053775 | Sender is printed as "null-" in SM service log while trying to generate 5002 error response for AAR-U message |
SM service logs printed the sender as null- while generating a 5002 error response for an AAR-U message. This can make the sender identity unclear in enhanced logs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39053783 | receiver field in SM log is printed as 'AF-' instead of 'Diam-C' for 5002 error response on STR message |
SM logs printed the receiver field as AF- instead of Diam-C for a 5002 error response on an STR message. This can misidentify the receiver in enhanced logs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39059748 | errorCause in diam-gw is shown as UNKNOWN whereas diam-conn is showing as DIAMETER_TOO_BUSY for 3004 diameter error code |
Diameter Gateway showed errorCause as UNKNOWN for a 3004 Diameter error while Diameter Connector shows DIAMETER_TOO_BUSY. This can make error reporting inconsistent across components. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39063766 | [Generic_Policy]: Custom values file does not contain readiness related configuration and proper description in diam-gw section |
The custom values file excluded readiness-related configuration and a proper description in the Diameter Gateway section. This can leave deployment guidance incomplete for readiness behavior. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 39083791 | EGW logs for message "HTTP response body is empty" doesn't contains ocLogId |
Egress Gateway logs for HTTP response body is empty messages can omit ocLogId. This can make those response errors harder to correlate. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39084868 | Diam-conn log contains error code as 5012 & diam-gw log has error code as 5063 |
Diameter Connector and Diameter Gateway logged different error codes for the same failure, with Diam-Conn showing 5012 and Diam-GW showing 5063. This can make troubleshooting inconsistent across components. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39090587 | Relevant error should be printed in errorCause field instead of UNKNOWN in Diam-conn and SM for HTTP related error log |
Diameter Connector and SM HTTP-related error logs printed UNKNOWN in the errorCause field instead of the relevant error. This can reduce diagnostic value for HTTP failures. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39090727 | EGW 25.2.109: Host dimension in Egress gateway response metrics still has cardinality explosion |
The Host dimension in Egress Gateway response metrics can still have excessive cardinality. This can increase monitoring storage and query load. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39100130 | [GR_Testing]:reactor.core.Exceptions$RetryExhaustedException Error log is seen while upgrading policy to 25.2.200 |
Policy upgrade to 25.2.200 can produce RetryExhaustedException error logs. This can add error noise or indicate retry handling issues during upgrade. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39110950 | Errors are printed in errorCode field rather than errorStatus field for all HTTP related enhanced error log in pcrf-core |
PCRF-Core enhanced HTTP error logs printed errors in the errorCode field instead of the errorStatus field. This can make error log fields inconsistent or misleading. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39110969 | Incorrect sender field with senderType as "OCS-ocpcf" is printed in daim_gw log for SNA message for 5005 error response |
Diameter Gateway logs can print an incorrect sender field with senderType OCS-ocpcf for SNA messages with a 5005 error response. This can misidentify the source in enhanced logs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39120227 | PCF nrf-client sending NRF subscription request with invalid URI causing subscription failure by NRF |
PCF NRF client sent NRF subscription requests with an invalid URI. This can cause NRF subscription creation to fail. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39155094 | calledStationId, framedIpAddress and other value are printed with a place holder in enhanced log for all http error codes in SM service |
SM service enhanced logs printed placeholders instead of actual values for calledStationId, framedIpAddress, and related fields across HTTP error codes. This can reduce the usefulness of error logs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39155221 | In received error response enhanced log of SM service, receiver field is printed as SM-, it doesn't contian receiverID value |
SM service enhanced logs for received error responses can print the receiver field as SM- without the receiverID value. This can make receiver identification incomplete. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39278726 | PCF sending additional AVP AN-Trusted as untrusted in Rx RAR |
PCF sent an additional AN-Trusted AVP with an untrusted value in Rx RAR messages. This can produce incorrect AVP data in Rx reauthorization traffic. Doc impact: There is no documentation impact. |
3 | 25.1.203 |
| 38291687 | PCF is not rejecting the Policy association request with invalid optional attributes. |
PCF accepted policy association requests containing invalid optional attributes. This can allow malformed policy association data instead of rejecting it with a validation error. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38477293 | [FTP-201/197]Handling: Error State and Error Cause- Code Mapping not working for cause code "optional_ie_incorrect" status code 400, |
Error state and error-cause code mapping can fail for the optional_ie_incorrect cause with HTTP status 400. This can produce incorrect or missing error details for that validation failure. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38564066 | [25.2.200.beta4]NPE is seen in UDR-conn once in SM performance run with receivedHeaders is null |
UDR connector throwed a NullPointerException during SM performance runs when receivedHeaders is null. This can interrupt affected UDR connector processing. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38590640 | NullPointerException observed in UE service during AM/UE call flow with AMFSET_UPDATE feature enabled. |
UE service throwed a NullPointerException during the AM/UE call flow when AMFSET_UPDATE is enabled. This can disrupt affected UE policy processing. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38602106 | [Micronaut]: io.micrometer.core.instrument.MeterRegistry WARN log is seen in multiple services in pod logs after upgrading to 25.2.200 |
Multiple services emitted MeterRegistry warning logs after upgrade to 25.2.200. This can create noisy pod logs and indicate metric registration issues. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38803368 | Binding Service logs WARN: "found 1 argument placeholders, but provided 3" at 1 CPS |
Binding Service logged warning messages about mismatched argument placeholders even at low traffic. This can create misleading WARN log noise during normal operation. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38810100 | UDR subscriber termination request is getting conflicted with error 409 in case sm-data and usage-mon data enabled for PCRF |
UDR subscriber termination requests can fail with 409 conflict when SM data and usage-monitoring data are enabled for PCRF. This can prevent subscriber termination cleanup. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38817096 | SM Create requests with non-matching DNN (sos) are incorrectly rejected during overload when rejection rules are configured for dnn=internet |
SM Create requests using a non-matching DNN such as sos can be incorrectly rejected during overload when rejection rules are configured for dnn=internet. This can reject traffic outside the intended DNN rule scope. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38826799 | Remove the license information and other irrelevant information from REST documentation |
REST documentation includes license information and other irrelevant content. This can clutter the API reference and confuse you reviewing REST documentation. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38856018 | Usage monitoring prompt ERROR Exception occurred in GrantManager /WARN getType()\" because "umD" is null with no clear error/warning of failure reason |
Usage monitoring logged GrantManager errors or warnings when umD is null without clearly reporting the failure reason. This can make usage-monitoring failures harder to diagnose. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38856758 | Ambiguity on namespace label on PCF /PCRF alertrule yaml file. |
The PCF and PCRF alert rule YAML file has ambiguous namespace label usage. This can make alert rule configuration unclear for you. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38867718 | [MICRONAUT] isIpvSixSetup used for SCLB to be removed if redundant post micronaut migration |
The isIpvSixSetup setting for SCLB can remain after Micronaut migration even if it is redundant. This can leave obsolete configuration in the service. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38902456 | (PCF:25.1.200): Egress Gateway (EGW) is generating a WARNING log with the message: "HTTP response body is empty." This occurs when SAL is enabled |
Egress Gateway can generate warning logs stating HTTP response body is empty when SAL is enabled. This can create misleading warning noise during subscriber activity logging. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38907997 | The Family of Alerts CPUUsagePerService.. and MemoryUsagePerServiceAbove.. are logically incorrect as the rate() function is being used on a gauge metric |
CPUUsagePerService and MemoryUsagePerServiceAbove alert rules can use rate() on gauge metrics. This can make the alert logic incorrect for CPU and memory usage monitoring. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38920493 | Audit service reported "Caught Exception while executing timer count synchronization job" due to Specified result type [java.lang.Integer] did not match Query selection type [java.lang.Long] |
Audit service can report an exception during timer count synchronization because the query result type does not match the selected type. This can disrupt timer count synchronization jobs. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38953982 | UDR_XX_IMMREP_FEATURE_NEGOTIATION_FAILED & UDR_XX_IMMREP_RESPONSE_MISSING_DATA alerts introduced in immediate reporting feature are activated during 4XX & 5XX failure condition |
Immediate reporting alerts for UDR feature negotiation failure and missing response data can activate during 4XX and 5XX failure conditions. This can generate alerts for expected failure-response scenarios. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38957418 | Observing 500 INTERNAL_SERVER_ERROR during fetch/export operation of UE Service Configuration if AMF Resubscription Condition is configured as "Please Select" |
UE Service Configuration fetch or export can fail with 500 Internal Server Error when AMF Resubscription Condition is set to Please Select. This can block configuration retrieval or export. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38973311 | When ImmRep is true, after 1st SM create success with POST ImmRep exchange and 2nd SM create revalidation with unsuccess GET-> PUT-> POST failure then SM update is not triggering POST with ImmRep enabled as per FD 4.2.11 |
SM update can fail to trigger the expected POST with Immediate Reporting enabled after a revalidation sequence involving unsuccessful GET, PUT, and POST operations. This can make immediate reporting behavior inconsistent with the documented flow. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39010720 | Bulwark logs for "Lock Response status" changed in 25.2.200 vs 25.2.100 (Similar to CNCESPOL-6535, status code missing) |
Bulwark lock response logs can omit the status code or differ unexpectedly between releases. This can reduce the usefulness of lock-response diagnostics. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39012904 | Bulk export from 23.4.6 fails import on 25.1.200 for congestion load shedding profile for diam-gw |
A bulk export from 23.4.6 can fail to import on 25.1.200 for the Diameter Gateway congestion load-shedding profile. This can block migration of that configuration. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39048337 | PCF is sending wrong Content-Type: application/problem+json header for successful response |
PCF can send Content-Type application/problem+json on successful responses. This can give clients an incorrect response content type. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39114139 | PCF CSAR package occndbtier_custom_values_model_d file having Invalid value for schedulertimer. |
The PCF CSAR package occndbtier_custom_values_model_d file can contain an invalid schedulertimer value. This can provide incorrect default deployment configuration. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39121038 | config server and audit service pods unexpected restarts have been observed in scaling down pod for 15 Min scenario on site-1 |
Config server and audit service pods can restart unexpectedly during a 15-minute pod scale-down scenario on site 1. This can affect service stability during scaling operations. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39139447 | High cardinality metrics in oc-policy-ds |
oc-policy-ds can emit metrics with high cardinality. This can increase monitoring storage and query load. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 39181026 | UDR Connector Have WARN Logs ""Error while reading client-metadata header" getting Printed during Execution of 54K Traffic Over AM-UE call Model |
UDR Connector can print warning logs about reading the client-metadata header during 54K AM-UE traffic execution. This can create warning noise under high traffic. Doc impact: There is no documentation impact. |
3 | 25.2.201 |
| 37042968 | Mismatch in IGW occnp_oc_ingressgateway_http_requests_total & occnp_oc_ingressgateway_http_responses_total when request sent with Content-Length:0 and Body- PRESENT |
Ingress Gateway request and response metrics can mismatch when a request has Content-Length: 0 while a body is present. This can make ingress HTTP request and response counts inconsistent. Doc impact: There is no documentation impact. |
3 | 23.4.6 |
| 37055606 | ocpm_ingress_response_total{servicename_3gpp="npcf-ue-policy-control"} for response_code=4xx not updating while request received with Content-Length:0 and Body-Absent |
The ocpm_ingress_response_total metric for npcf-ue-policy-control 4xx responses can fail to update when a request has Content-Length: 0 and no body. This can underreport ingress error responses. Doc impact:There is no documentation impact. |
3 | 23.4.6 |
| 37618869 | pre pods restart observed due to OOM on Policy 24.2.4 |
PRE pods restarted because of out-of-memory conditions on Policy 24.2.4 . This can affect PRE service stability. Doc impact: There is no documentation impact. |
3 | 24.2.4 |
| 37685088 | Two ASRs are being triggered from PCF, resulting in a Diameter "Unknown Session ID" (5002) error. |
PCF can trigger two ASRs for a session, resulting in a Diameter Unknown Session ID 5002 error. This can create duplicate session termination signaling. Doc impact: There is no documentation impact. |
3 | 23.4.5 |
| 38428760 | FTP-197[TC-047]Handling: Error State and Error Cause- Code Mapping is not correct for cause code "MANDATORY_IE_INCORRECT" status code 400, |
Error state and error-cause code mapping can be incorrect for MANDATORY_IE_INCORRECT with HTTP status 400. This can give clients wrong error details for mandatory IE validation failures. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38676847 | Diam GW once stuck in Overload state continued to be in same state even No traffic was there |
Diameter Gateway remained stuck in overload state even after traffic stops. This keeps the gateway in an incorrect overload condition. Doc impact: There is no documentation impact. |
3 | 24.2.7 |
| 38709061 | TDF value gets change in policy project when policy bulk import is performed |
TDF values in a policy project changed during policy bulk import. This can alter imported policy configuration unexpectedly. Doc impact: There is no documentation impact. |
3 | 24.2.0 |
| 38709401 | Rollback fails due to Missing "empty-dir" volumeMount in 24.2.8 ARS deployment.yaml |
Rollback can fail because the ARS deployment YAML missed an empty-dir volumeMount. This can block rollback for the affected deployment package. Doc impact: There is no documentation impact. |
3 | 25.1.201 |
| 38750370 | SM is not storing the rule failure report when the rule status is "active" |
SM service failed to store rule failure reports when the rule status is active. This can leave failure-report information missing for active rules. Doc impact: There is no documentation impact. |
3 | 23.4.6 |
| 38770251 | PA Create without MediaSubComponents causes null pointer exception on SMF Update Notify |
PA Create requests without MediaSubComponents can cause a NullPointerException during SMF Update Notify processing. This can interrupt notification handling for that request shape. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38770894 | Alternate route retry does not work for nBSF initial message in model B |
Alternate route retry can fail for the nBSF initial message in Model B. This can prevent expected rerouting when the initial path fails. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 38797394 | PCF choosing SUSPENDED BSF instead of the REGISTERED BSF in case of Alternate route for deleteBinding request |
PCF can choose a suspended BSF instead of a registered BSF when using alternate routing for deleteBinding requests. This can route binding deletion traffic to the wrong BSF state. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 38824470 | Inconsistent grant by UM when max grant limits granted units |
Usage Monitoring can grant inconsistent units when maximum grant limits are applied. This can produce incorrect quota grants. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38835801 | chf_tracking_request_total and chf_tracking_response_total metrics are getting pegged for incorrect nfName in case of rerouted-retried attempts by ARS |
CHF tracking request and response metrics can be pegged with the wrong nfName during ARS reroute and retry attempts. This can misattribute CHF tracking metrics. Doc impact: There is no documentation impact. |
3 | 25.2.100 |
| 38842438 | Dynamic rule with Ethernet Flow Description VLAN tag is not working |
Dynamic rules using an Ethernet Flow Description VLAN tag failed to work. This can prevent correct policy behavior for VLAN-tagged Ethernet flow rules. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38846215 | UE svc exposing too much of the data in the log. Which will potentially results in over flood of the log and will increase the cpu |
UE service logs exposed excessive data, causing log flooding and increased CPU usage. This can reduce observability quality and add runtime overhead. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38864849 | Exception in non-ASM setup for content-length and content-type are absent |
Non-ASM setups can throw an exception when both content-length and content-type headers are absent. This can fail request handling for headerless payload scenarios. Doc impact: There is no documentation impact. |
3 | 23.4.6 |
| 38883549 | Stale data is present when PCF send POST request with ImmRep attribute as true to UDR but 5xx response is received since validate user is true SM create is declined but stale PDS data is not deleted |
Stale PDS data can remain when PCF sends a POST request with ImmRep true to UDR and receives a 5xx response while validation is enabled. This can leave stale data after an SM create request is declined. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38883651 | Binding Sevice : ar_request_total and ar_response_total metrics are not being pegged for nBSF initial messages retry attempts when Binding service performs rerouting on alternate route. |
Binding Service failed to peg ar_request_total and ar_response_total metrics for nBSF initial-message retry attempts during alternate-route rerouting. This can underreport alternate routing activity. Doc impact: There is no documentation impact. |
3 | 25.2.200 |
| 38905299 | BAUTTMELAB: PCF EGW not giving precedence to IPV6 and resolving to IPV4 address |
PCF Egress Gateway resolved to an IPv4 address instead of giving precedence to IPv6. This can route traffic over the wrong IP family in IPv6-preferred environments. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38956556 | "occnp_oc_ingressgateway_http_responses_total" metric not getting incremented |
The occnp_oc_ingressgateway_http_responses_total metric failled to increment. This can underreport ingress gateway HTTP responses. Doc impact: There is no documentation impact. |
3 | 24.2.7 |
| 38966619 | N5 PA update PATCH request is reject with wrong error cause when Mandatory parameter is missing in request |
N5 PA update PATCH requests with missing mandatory parameters was rejected with the wrong error cause. This gives clients misleading validation information. Doc impact: There is no documentation impact. |
3 | 25.1.202 |
| 38972667 | EGW is not able to send access token request towards NRF in TLS enabled setup |
Egress Gateway failed to send access-token requests toward NRF in TLS-enabled setups. This can prevent expected NRF authorization flow. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 38974428 | SPAD_POLICY[AM-UE-Performance]- UE services has Intermittent Error "Error creating params for PDS DELETE request with exceptionl" |
UE service intermittently log errors while creating parameters for PDS DELETE requests during AM-UE performance runs. This can affect PDS delete request handling. Doc impact: There is no documentation impact. |
3 | 25.1.202 |
| 38982314 | PCF not sending Event Triggers in notification message towards SMF in continuous call testing |
PCF excluded event triggers in notification messages sent to SMF during continuous call testing. This sent an incomplete notification data. Doc impact: There is no documentation impact. |
3 | 24.2.9 |
| 38984315 | Network Element capability must be restricted to a few values |
Network Element capability values were accepted without the expected restriction to allowed values. This can permit invalid or unsupported capability values. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39007416 | 25.1.200 PCF Congestion Control migration: Activities |
PCF congestion-control migration activities had incomplete or incorrect behavior for the 25.1.200 migration path. This affected migration of congestion control configuration. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39028996 | Pcrf-core: Need a retry mechanism for context and dependentContext binding creation failure |
PCRF-Core lacked retry handling when context or dependentContext binding creation fails. This can leave binding creation failures unrecovered. Doc impact: There is no documentation impact. |
3 | 24.2.9 |
| 39066625 | Seeing extra PA Service Received Event: msg type: DELETE in SM-service logs when executing SM-Rx call |
SM-service logs can show an extra PA Service received event with DELETE message type during SM-Rx calls. This can create misleading log entries for the call flow. Doc impact: There is no documentation impact. |
3 | 23.4.4 |
| 39128166 | OCCNP25.1.201-Incorrect destination-host avp in Sd TSR message |
Sd TSR messages included an incorrect Destination-Host AVP. This can send Diameter traffic with wrong routing information. Doc impact: There is no documentation impact. |
3 | 25.1.201 |
| 39162602 | cnPCRF CCA-I (3004) does not include Mandatory AVP CC-Request-Type |
cnPCRF CCA-I responses with result code 3004 omitted the mandatory CC-Request-Type AVP. This can produce noncompliant Diameter response messages. Doc impact: There is no documentation impact. |
3 | 24.2.0 |
| 39189141 | Deletion of config item causes export failure |
Deleting a configuration item caused an export operations to fail. This can prevent the user from exporting configuration after item deletion. Doc impact: There is no documentation impact. |
3 | 25.1.203 |
| 39216654 | Policy synchronization issue: Post-upgrade/failover state mismatch |
Policy state mismatched after upgrade or failover. This can leave synchronized policy data inconsistent across system components. Doc impact: There is no documentation impact. |
3 | 24.2.8 |
| 39285181 | No policy evaluated for service pds as there is no policy project in 'Prod' state |
PDS policy evaluation failled when no policy project is in Prod state. This can prevent expected policy evaluation for the PDS service. Doc impact: There is no documentation impact. |
3 | 25.1.200 |
| 39320933 | Snssai showing blank |
SNSSAI values were displayed as blank. This can hide slice information from the user. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 39377723 | Import containing Subscriber Activity Logging configuration is responded with 500 ISE |
Imports containing Subscriber Activity Logging configuration failed with a 500 Internal Server Error. This can block import of SAL-related configuration. Doc impact: There is no documentation impact. |
3 | 25.2.201 |
| 39378360 | DnsConfig addition in CV yaml file |
The CV YAML file lacked required DnsConfig content for the scenario. This can leave DNS configuration incomplete in custom values. Doc impact: There is no documentation impact. |
3 | 24.2.1 |
| 39396476 | config-server: When found a duplicate entry in the config-server DB for a config_item, delete it based on a configuration |
Config-server encountered a duplicate config_item entries in its database without configuration-based cleanup behavior. This can leave duplicate configuration records unresolved. Doc impact: There is no documentation impact. |
3 | 23.4.6 |
| 39480148 | Changing: PCF -> Controlled Shutdown -> Operational State in the CNCC GUI gives "Unable to switch the operational state" error |
Changing PCF controlled-shutdown operational state from the CNCC GUI failed with an Unable to switch the operational state error. This can prevent you from changing PCF operational state through the GUI. Doc impact: There is no documentation impact. |
3 | 25.1.202 |
| 39488706 | NPE seen in sm-service when it directly communicates with BSF when binding is disabled |
SM service throwed a NullPointerException when directly communicating with BSF while binding is disabled. This can interrupt affected SM-to-BSF communication. Doc impact: There is no documentation impact. |
3 | 24.2.3 |
| 39669081 | OCS_KEY_PRECEDENCE=GPSI does not suppress IMSI in Sy SLR when request contains both SUPI and GPSI |
OCS_KEY_PRECEDENCE=GPSI failed to suppress IMSI in Sy SLR messages when the request contains both SUPI and GPSI. This sent an unintended subscriber identifiers on the Sy interface. Doc impact: There is no documentation impact. |
3 | 25.1.203 |
| 39681602 | Unavailability of the db-monitor-svc, shall not be considered db cluster failure |
App-info incorrectly interpreted the db-monitor service unavailability or probe failure as a database cluster failure. Transient db-monitor errors, timeouts, or unavailable responses can cause the database tier to be reported as Not_Running even when the DB cluster is not down. Doc impact: There is no documentation impact. |
3 | 23.4.6 |
4.2.10 NRF Resolved Bugs
Release 26.1.201
Table 4-11 NRF 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39437130 | NRF Auditor pod entered CrashLoopBackOff after a complete connectivity break. |
During a complete connectivity break experiment, the NRF Auditor pod restarted repeatedly and entered the CrashLoopBackOff because startup depended on Kubernetes secret access for leader datasource initialization. When secret retrieval failed or timed out, Micronaut treated the bean creation failure as fatal, and the container did not start. This resulted in delayed recovery of the Auditor pod after connectivity was restored. During a fault insertion with a complete connectivity break experiment against the NRF Auditor pod, the auditor pod restarted repeatedly and entered CrashLoopBackOff. The failure was seen during recovery after connectivity interruption, where the pod startup path depended on Kubernetes secret access for leader datasource initialization. The observed customer-facing behavior was that the auditor pod did not recover promptly after connectivity was restored, and recovery could be delayed by Kubernetes restart backoff while startup continued to fail. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39713222 | NRF rejected UDR registration requests without Content-Length with a misleading Content-Encoding error. |
After NRF was upgraded from 25.1.202 to the 25.2.20x line, previously completed UDR registration requests were rejected when the request body was valid, but the Content-Length header was not specified. NRF returned HTTP 415 with an unsupported Content-Encoding or gzip error even though the failure was related to request transfer framing, not compressed content. This resulted in valid UDR registration requests being rejected with an incorrect error response. Doc Impact: There is no documentation impact. |
2 | 25.2.201 |
| 36108386 | Forwarding Loop Detection does not consider all the sets of the other NRF segment. |
NRF forwarding loop detection did not consider all configured NRF sets in the other segment. When a request contained a Via header from an NRF in a non-primary or lower-priority set, NRF compared the header only with the primary forwarding set and did not detect that the request had already passed through the other segment. This resulted in additional forwarding hops, forwarding loops, and request timeouts in multi-set segment deployments. Doc Impact: Updated the configuration details in the Enhanced NRF Set Based Deployment (NRF Growth) section and updated the recommended actions for the OcnrfSyncFailureFromAllNrfsOfAllRemoteSets alert in Oracle Communications Cloud Native Core Network Repository Function User Guide. |
3 | 23.4.0 |
| 37262850 | Server header is not returned in client response by NRF for some error response codes when Support for Server Header feature is enabled. |
When the Server header feature was enabled, NRF did not return the configured Server header in some client-facing roaming error responses for the Discovery, Subscription, and Access Token services. NRF propagated the internal Oc-Skip-Server-Header marker for responses generated by the Egress Gateway microservice, and the Ingress Gateway microservice interpreted this marker as an instruction to skip Server header injection. This resulted in client-facing error responses being returned without the configured Server header even though the feature was enabled. Doc Impact: There is no documentation impact. |
3 | 24.3.0 |
| 38460687 | NRF uses only local site data when georedundancy feature is enabled. |
NRF used only local site state data when georedundancy was enabled with overrideReplicationCheck set to true. During a fresh install or georedundancy reconfiguration, updated site mappings from geoRedundancyOptions.siteNameToNrfInstanceIdMappingList were not reloaded dynamically, preventing remote site replication status from being updated correctly. This resulted in NRF operating as a standalone site and not considering the configured georedundant site data during service operations until the affected pods were restarted. Doc Impact: Updated the description of global.overrideReplicationCheck in Oracle Communications Cloud Native Core Network Repository Function Installation, Upgrade, and Fault Recovery Guide. |
3 | 25.1.200 |
| 39029736 | NRF accepted serverHeaderValueBasedSLFSelection as an array instead of a string. |
NRF did not reject an invalid array value for serverHeaderValueBasedSLFSelection, even though the configuration field accepted only a string value. This resulted in invalid configuration payloads being accepted instead of being rejected with an appropriate validation error. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39205839 | NRF sent nfServices in the notification request instead of nfServiceList during NF Update PUT. |
NRF processed a complete NF profile update successfully, but the NF_PROFILE_CHANGED notification could contain nfServices instead of the expected nfServiceList when requesterFeatures=1 requested service-map behavior. The issue also applied to the heartbeat update path when service load changes triggered the same notification flow. This resulted in subscribers receiving a notification payload with the wrong service attribute representation. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39280716 | Remote NRF delete subscription request did not persist the unsubscribed state. |
In a georedundant NRF deployment, a subscription delete request sent to the remote site returned HTTP 204 even when the remote site did not persist the expected local unsubscribe state. When the record was missing, NRF did not create or update the subscription entry with subscriptionStatus=UNSUBSCRIBED and the remote NRF instance ID as recordOwner. This resulted in the remote site returning success without recording the unsubscribe state required for georedundancy tracking. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39290977 | NRF intermittently fell back to DB during performance runs. |
During high-throughput NRF performance runs, ocnrf_db_fallback_total increased intermittently because service operations did not consistently use the full cached NRF set data. Under the 53k TPS call model with growth, SLF, forwarding, 1000 NFs, 2000 subscriptions, and ASM enabled, NRF fell back to DB or same-set data paths. This resulted in random DB fallback behavior across service operations under load. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39305975 | Subscription based on nfGroupId was treated as duplicate when an nfType subscription already existed and allowDuplicateSubscriptions was false. |
When allowDuplicateSubscriptions was set to false, NRF treated a new subscription that included both nfType and nfGroupId as a duplicate of an existing nfType-only subscription. The request returned 201 but reused the first subscription ID instead of creating a distinct group-specific subscription. This resulted in logically different subscriptions being collapsed into the same subscription record. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39374541 | NRF hook jobs and AppInfo did not consistently use the configured service account. |
NRF hook jobs did not consistently render,serviceAccountName, and AppInfo chart behavior did not reliably use the configured global.serviceAccountName. When image pull secrets were attached only to the configured service account, the affected resources could run with a different identity or fail image pulls in private registry environments. This resulted in inconsistent service account usage for hook jobs and AppInfo-related resources. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39459529 | DNS NAPTR records were not cleaned up after AMF NFProfile Update removed amfInfo.n2InterfaceAmfInfo. |
After a complete NFProfile Update was removed amfInfo.n2InterfaceAmfInfo, NRF did not remove the previously created DNS NAPTR, A, and AAAA records when DNS NAPTR was enabled. The update succeeded, but stale DNS entries remained in OCDNS. This resulted in DNS records remaining after the AMF N2 information was removed from the NF profile. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39529196 | Prometheus showed multiple load levels for performance pods. |
Prometheus showed more than one load_level entry for performance services because the queries included stale or non-current leader pod metrics. Filtering only by isLeaderPod="True" did not fully exclude old leader data after leader changes. This resulted in multiple load levels being displayed for the same performance service. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39580529 | NRF preferredTaiMatchInd was incorrect for preferred TAI discovery with network and operator DNN portions. |
NRF discovery returned preferredTaiMatchInd=false for SMF preferred-TAI discovery when the request used a full DNN with network and operator portions and the registered SMF profile contained only the network identifier DNN. The profiles were still returned, but the preferred-TAI joint match logic did not recognize the equivalent DNN forms. This resulted in an incorrect preferred-TAI match indication during SMF selection. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39659430 | Alternate-route service did not define ephemeralStorageLimit, so the ephemeral-storage limit was omitted. |
The alternate-route service did not consistently define a non-zero ephemeralStorageLimit in custom values.yaml. Because the Helm template rendered limits.ephemeral-storage only when ephemeralStorageLimit was non-zero, the deployment skipped the ephemeral-storage limit for alternate-route. This resulted in alternate-route pods being deployed without an explicit ephemeral-storage limit. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39688773 | Incorrect ocLogId value and hop path in CDS logs under mixed traffic, breaking end-to-end traceability. |
Under mixed duplicate-check and notification traffic, CDS logs showed an ocLogId and hop path that did not match the incoming request context. The asynchronous execution path did not consistently propagate the current request context, so duplicate-check traffic could appear as though it passed through Registration. This resulted in incorrect log correlation and reduced end-to-end traceability for CDS processing. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 38850197 | Access Token configuration validation response returned an incorrect parameter path for authConfig[1].serviceNames. |
NRF returned validation errors for the Access Token authentication feature with internal field names instead of public API parameter paths. Consequently, the validation response reported an incorrect parameter path forauthConfig[1].serviceNames, making it difficult to identify the invalid configuration in the submitted request. This affected only the validation error response and did not change the handling of valid Access Token configuration requests. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38974136 | Old Ingress Gateway microservice pods underwent rolling restarts during same-release upgrades. |
Old Ingress Gateway microservice pods were restarted unnecessarily during same-release Helm upgrades when globalIngressRateLimiting was enabled. Even when there were no changes to the deployment configuration or custom values.yaml, the deployment appeared modified because an internally generated hash value changed during each upgrade. This resulted in unnecessary rolling restarts of existing Ingress Gateway microservice pods during same-release upgrades even though no functional deployment changes had occurred. Doc Impact: There is no documentation impact. |
4 | 24.1.3 |
| 38996646 | NRF returned an incorrect maximumHopCount range message in the generalOptions REST API response. |
NRF returned an incorrect validation message for maximumHopCount and maxSLFAttempts when invalid values were submitted through the REST API. Although the product accepted the documented boundary values, the error message described the supported range using exclusive boundaries. This resulted in a validation response that incorrectly implied valid boundary values were not supported and could mislead administrators during configuration. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39032189 | NRF accepted an invalid slfConfigMode value in slfOptions. |
NRF accepted and stored unsupported values for slfConfigMode in slfOptions, although the REST API supported only STATIC_SLF_CONFIG_MODE and DISCOVERED_SLF_CONFIG_MODE. This resulted in invalid configuration values being persisted instead of being rejected during configuration validation. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39442562 | Grafana dashboard showed incorrect Egress Gateway microservice request rate. |
The NRF Grafana dashboard showed incorrect Egress Gateway microservice request and response rate values because the PromQL queries did not consistently filter the metric by the expected egress direction. This resulted in the dashboard displaying incorrect or inconsistent Egress Gateway microservice rate values. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39442597 | NRF Grafana dashboard showed an incorrect SLF Query Success Ratio (2xx) percentage. |
The NRF Grafana dashboard had an incorrect PromQL expression for the SLF Query Success Ratio (2xx) percentage panel. The denominator was filtered the same way as the 2xx numerator, so the panel calculated an incorrect success ratio. This resulted in the dashboard showing the wrong SLF success percentage. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39499880 | False OcnrfHeapUsageCrossedMajorThreshold alarms were triggered for nrfauditor pods in production NRF. |
Customer environments saw recurring OcnrfHeapUsageCrossedMajorThreshold alarms for nrfauditor pods even though the pods were stable, had no OOMKilled events, and showed no Java OutOfMemoryError. The alert thresholds were too aggressive for the expected nrfauditor heap usage pattern. This resulted in repeated false major heap alarms without any functional service impact. Doc Impact: There is no documentation impact. |
4 | 25.1.203 |
| 39636137 | NRF returned screening rules from all georedundant sites in the GET response. |
The unfiltered screening-rules GET API returned screening-rule records from all sites in a three-site georedundant deployment instead of returning only the records owned by the local NRF instance. Replicated records from the other sites were included in the response. This resulted in the GET response returning screening-rule data outside the local site scope. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
Note:
Resolved bugs from 25.2.2xx have been forward ported to Release 26.1.201.4.2.11 SEPP Resolved Bugs
Release 26.1.201
Table 4-12 SEPP 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39638124 | Inconsistent oc_ingressgateway_rss_ratelimit_total dimension labels |
Standardized the documented metric dimension labels and clarified when each metric is emitted. Doc Impact: Updated the |
4 | 25.1.203 |
| 39636918 | Missing binding_value dimension in SEPP metrics documentation |
Verified the actual labels used by the DNS SRV and alternate-route metrics, and updated the binding_value documentation. Doc Impact: Updated the "DNS SRV and alternate-route metrics" section in the Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide. |
4 | 25.1.203 |
| 39635771 | User Guide missing type dimension for alternate-route metric |
Updated the dimensions in the oc_fqdn_alternate_route_total. Doc Impact: Updated the |
4 | 25.1.203 |
Release 26.1.200
Table 4-13 SEPP 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39176253 | Missing https config in default sor peerset config |
The default SOR peerset was created without HTTPS configuration while route metadata enforced httpsTargetOnly=true. This caused intermittent routing failures with “No https instances configured” and resulted in SOR regression failures. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39373350 | SOR request from SEPP to SOR carries producer NF FQDN in header authority instead of configured SOR FQDN - v26.1.200 |
The SOR request used the producer NF FQDN in :authority instead of the configured SOR FQDN. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39476210 | Hosted SEPP multi-FQDN feature not working in 26.1.200-rc.1 |
Hosted SEPP multi-FQDN functionality does not work. The handshake between the hosted SEPP and hosted partner is established successfully; however, the handshake between the roaming partner and hosted SEPP fails with a 401 Unauthorized error on hosted SEPP pn32c. Although the hosted SEPP multi-FQDN configuration is defined in custom_values.yaml, it is not reflected in the n32-ingress ConfigMap. As a result, the hosted SEPP multi-FQDN feature does not function as expected. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39656465 | SEPP documentation updates required for EGW POP | In the SEPP Egress Gateway Pod Protection by Rate Limiting documentation, the User Guide, REST Guide, and Installation Guide contain inconsistent gateway names, REST URIs, Helm parameter names, and default values.
Doc Impact: Updated the "Pod Protection By Rate Limiting" section in the Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide, Oracle Communications Cloud Native Core Security Edge Protection Proxy REST Specification Guide and updated the "Customizing SEPP" section in Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide. |
3 | 26.1.200 |
| 39707764 | SEPP default YAML does not clearly expose seppPeerHealthCheckCodes for Proactive Health API. | SEPP Proactive Health API documentation suggesting seppPeerHealthCheckCodes may be configurable in custom-values.yaml, while only seppPeerHealthCheck is actually exposed.
Doc Impact: Updated the healthyseppPeerHealthCheckCodes in the "Proactive Health API" section in the Oracle Communications Cloud Native Core Security Edge Protection Proxy REST Specification Guide. |
3 | 26.1.200 |
| 39559658 | Default error code profile mentioned in "Pod Protection by Rate Limiting" does not exist | The default error code profile referenced by Pod Protection Rate Limiting did not match the actual configured default error code profile available in the system.
Doc Impact: Updated the "Error Code Profiles" section in the Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide. |
3 | 26.1.200 |
| 39600267 | SEPP-PERF:Duplicate includeClientCertIdentityAsTag parameter under n32-ingress-gateway causes intended metrics tagging configuration to be overridden in SEPP_26.1.200-rc.2 |
The includeClientCertIdentityAsTag parameter is configured twice in the same n32-ingress-gateway section with conflicting values. YAML parsing retains the last value, which sets the effective value to false. As a result, the ClientCertIdentity tag is not included in request and response metrics, although the earlier configuration enables it. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39694882 | SEPP: oauthRequestValidation parameter missing from custom-values.yaml for OAuth get token request validation |
The SEPP User Guide states that OAuth get-token request validation can be enabled by setting oauthRequestValidation: true under the Pn32f section in values.yaml. However, customers cannot modify the Helm chart values.yaml directly. Because the parameter is not exposed in custom-values.yaml, customers do not have a supported way to enable OAuth get-token request validation during deployment. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 38257593 | pn32f memory usage keep on increasing at 550 TPS with cat3 time check enabled |
PN32F memory usage kept increasing during 550 TPS CAT3 time-check traffic because local NRF response caches were not released. Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 38278479 | Getting "No https instances configured" intermittently in PLMN EGW logs |
With NIF enabled, PLMN egress gateway intermittently logged internal routing errors during traffic, which indicated inconsistent HTTPS peer selection behavior and potential impact to stable NIF traffic routing. Doc Impact: There is no documentation impact. |
3 | 25.1.201 |
| 38489579 | SEPP sending esxtra TLS signature algorithms when it should limit what's being sent IAW SA-TLS-016 |
SEPP sent extra TLS signature algorithms beyond the SA-TLS-016 expected list. Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 38943638 | OCSEPP 25.1.202 Roaming Hub SEPP sending plmnIdList with null value in the n32c-handshake |
During the handshake in 25.1.202, SEPP sent plmnIdList as null instead of sending it as an array, or omitting it when empty, as expected by 3GPP TS 29.573. Doc Impact: There is no documentation impact. |
3 | 25.1.201 |
| 38989742 | several standard and non-standard http headers are repeated when the request is being proxied by psepp to hSCP |
Proxied requests repeated headers such as via, content-type, and user-agent. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39066880 | SEPP: Wrong value of 'content-type' in response for Remote SEPP creation failure |
Multiple Remote SEPP creation validation failures returned content-type: application/json instead of application/problem+json. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39074219 | SEPP: Wrong value of 'content-type' in response for Remote SEPP set creation failure |
Remote SEPP set creation failure responses returned application/json instead of application/problem+json. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39074274 | Hosted SEPP: wrong error code is generated when Remote SEPP set is created with missing "hostedRemotePartnerSet" parameter |
Creating a Remote SEPP set without hostedRemotePartnerSet returned a 500 Internal Server Error because of a null dereference, instead of the expected 4xx validation error. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39114099 | errors being reported in sepp pn32f microservices |
PN32F microservices reported Coherence/JMX and service-discovery errors in pod logs. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39126163 | SEPP does not refuse a CONNECT method |
SEPP did not immediately reject HTTP CONNECT method requests during screening tests and returned a 408 timeout instead. Doc Impact: There is no documentation impact. |
3 | 25.1.201 |
| 39200159 | Errors being reported in plmn egw and ARS microservice for NRF |
PLMN egress gateway and Alternate Route Service reported NRF-related lookup errors when virtual NRF was deployed with the HTTP scheme. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39249940 | SEPP: Hosted sepp removing via header of csepp during a Model-C service request |
Hosted SEPP removed or missed the cSEPP via header during the Model-C service request flow. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39412205 | ServiceDiscoveryException being reported in multiple SEPP services |
Multiple SEPP services reported ServiceDiscoveryException from Kubernetes endpoint discovery failures. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39427362 | SEPPConnectionFailureN32IGWAlert label not exposing error_reason label in the metric |
The SEPPConnectionFailureN32IGWAlert metric did not expose the expected error_reason label. Doc Impact: There is no documentation impact. |
3 | 25.1.201 |
| 39522482 | PN32F Return 504 GATEWAY_TIMEOUT error with incorrect format |
When PLMN egress gateway pods were down, PN32F returned an HTTP 504 Gateway Timeout response that did not use the required JSON Problem Details format. Doc Impact: There is no documentation impact. |
3 | 25.1.203 |
| 39707787 | Wrong formatting for seppPeerHealthCheckCodes in SEPP Proactive Health API documentation -26.1.200v | The User Guide incorrectly formats seppPeerHealthCheckCodes as healthyseppPeerHealthCheckCodes.
Doc Impact: Updated "Proactive Health API" section in the Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide. |
4 | 26.1.200 |
| 39728190 | SEPP Installation Guide incorrectly lists n32 ingress gateway-only healthCheckMonitoring.enabled parameter under N32 Egress gateway - 26.1.200v | The Installation Guide incorrectly lists the ingress-only parameter n32-ingress-gateway.healthCheckMonitoring.enabled in the N32 Egress Gateway parameter table. This parameter is consumed only by the N32 Ingress Gateway chart and should be removed from the N32 Egress Gateway section.
Doc Impact: Updated the "Customizing SEPP" section in the Oracle Communications Cloud Native Core Security Edge Protection Proxy Installation, Upgrade, and Fault Recovery Guide. |
4 | 26.1.200 |
| 38484413 | 500 Internal Server Error logs in plmn egw logs during 1K traffic of NIF error copy |
During 1K TPS NIF error-copy traffic, PLMN egress gateway generated 500 Internal Server Error logs, which potentially affected reliable error-copy processing at higher load. Doc Impact: There is no documentation impact. |
4 | 25.2.100 |
| 38818844 | SEPP-PERF: Refresh task failed due to invalid response code for k8s api query response at ocsepp-sepp-nrf-client-nfdiscovery & ocsepp-sepp-nrf-client-nfmanagement microservice during long performance run |
During a long performance run, NRF client nfdiscovery and nfmanagement microservices logged refresh task failures because Kubernetes service discovery queries returned HTTP 403 responses. Doc Impact: There is no documentation impact. |
4 | 25.2.100 |
| 39113794 | SEPP: Missing dimensions in prometheus metric oc_egressgateway_connection_failure_total |
The Prometheus metric oc_egressgateway_connection_failure_total missed the expected dimensions host, port, and errorReason that were documented in the user guide. Doc Impact: Updated oc_egressgateway_connection_failure_total metric dimensions in the Oracle Communications Cloud Native Core Security Edge Protection Proxy User Guide. |
4 | 25.2.200 |
| 39211875 | content-type is application/json when capability exchange fails |
During N32-C capability exchange failure caused by PLMN list mismatch, SEPP returned a 400 Problem Details body with Content-Type: application/json instead of application/problem+json. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39410950 | SEPP: custom yaml updates |
The default custom YAML needed updates for atsSpecificDeployment and CNLB annotation examples. Doc Impact: The |
4 | 26.1.200 |
Note:
Resolved bugs from 25.2.201 have been forward-ported to Release 26.1.2004.2.12 SCP Resolved Bugs
Release 26.1.202
Table 4-14 SCP 26.1.202 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39760796 | SCP Fails to Fall Back to NF-Instance–Scoped LCI Load When Service-Instance Load Is Absent |
SCP treated a missing service-level load as 0, prevented fallback to the NF-profile load. Doc Impact: There is no document impact. |
3 | 25.2.104 |
Release 26.1.201
Table 4-15 SCP 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39660217 | 508 loop detected with HSS services |
A 508 loop was detected with HSS services. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39567885 | UpdateNotify not routed over TLS |
SCP failed to route UpdateNotify to an SMF over TLS and returned a 504 error. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39385808 | Notification routing issue |
A notification routing issue occurred on SCP. Doc Impact: There is no documentation impact. |
2 | 25.1.204 |
| 37886252 | High-cardinality metrics and high memory consumption |
High-cardinality metrics and high memory consumption were observed on SCP while traffic ran at full capacity. Doc Impact: There is no documentation impact. |
2 | 25.1.100 |
| 39748785 | UDV variables missing after an SCP upgrade from 25.2.203 to 26.1.201 |
UDV variables were missing after an SCP upgrade from 25.2.203 to 26.1.201. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39701340 | Roaming notification traffic not routed through configured SEPP ports |
Roaming notification traffic was not routed through the configured SEPP ports. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39569870 | Connection failure before response timeout expiry |
A connection failure occurred before the response timeout expired. Doc Impact: There is no documentation impact. |
3 | 24.3.0 |
| 39616215 | NF_PROFILES_UPDATE_HISTORY recorded NULL data for DEREGISTERED profiles after upgrade |
NF_PROFILES_UPDATE_HISTORY recorded NULL data for DEREGISTERED profiles after an upgrade from 25.2.1xx. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39616210 | ocscp_pod_overload_discard_by="PENDING_TRANSACTION" missing from a metric |
The user guide did not document ocscp_pod_overload_discard_by="PENDING_TRANSACTION" for ocscp_worker_pod_overload_discard_req_total. Doc Impact: Updated the example of the "ocscp_worker_pod_overload_discard_req_total" metric in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
3 | 26.1.200 |
| 39601835 | SCPUnhealthyPeerSCPDetected alert not cleared |
The SCPUnhealthyPeerSCPDetected alert did not clear as expected. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39597102 | Incorrect ocscp_nexthop_ocscp_fqdn dimension value |
The SCP metrics documentation incorrectly identified the ocscp_nexthop_ocscp_fqdn dimension as ocscp_nexthop_scp_fqdn. Doc Impact: Updated the dimension of the "ocscp_metric_interscp_http_tx_req_total" and "ocscp_metric_interscp_http_rx_res_total" metrics in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
3 | 26.1.200 |
| 39596149 | Audit metric pegged for an empty successful NRF response |
The audit metric was pegged when an empty successful response was received from NRF. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39581580 | ocscp_metric_peer_scp_unhealthy_total not documented |
The ocscp_metric_peer_scp_unhealthy_total metric was not documented in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. Doc Impact: Added the "ocscp_metric_peer_scp_unhealthy_total" metric in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
3 | 26.1.200 |
| 39572859 | authority header changed after an SCP upgrade |
The authority header changed after an SCP upgrade to 25.1.202. Doc Impact: There is no documentation impact. |
3 | 25.1.202 |
| 39571812 | Ingress and egress metrics missing from the user guide |
The SCP User Guide did not document ocscp_worker_ingress_req_total and ocscp_worker_egress_res_total. Doc Impact: Added the "ocscp_worker_ingress_req_total" and "ocscp_worker_egress_res_total" metrics in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
3 | 26.1.200 |
| 39520804 | OCI for inter-SCP not working |
OCI for inter-SCP did not work in SCP 25.2.203 Doc Impact: There is no documentation impact. |
3 | 25.2.203 |
| 39503574 | PUT method accepted empty nextHopRoamingProxyRoutingConfigData |
The PUT method accepted empty nextHopRoamingProxyRoutingConfigData for the NextHopRoamingProxyRoutingConfig API. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39439839 | Worker restarted during overload scenarios |
SCP-Worker restarted during overload scenarios because of the liveness probe configuration. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39434020 | Stale thread entries appeared in Thread Watch Dog information |
Stale thread entries appeared in Thread Watch Dog information with COMPLETED+isStuck=true. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39394411 | Invalid traffic-rejection parameter values did not return an error |
SCP did not return an error for invalid retryAfter and redirect URL values in defaultScpTrafficRejectionErrorProfile in the CNC Console. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39367198 | LCI Tx metrics dropped to zero after an upgrade |
SCP LCI Tx metrics intermittently dropped to zero after an upgrade from 25.1.100 to 25.2.103. Doc Impact: There is no documentation impact. |
3 | 25.2.103 |
| 39366469 | Empty default values in defaultScpTrafficRejectionErrorProfile |
The retryAfter and redirectURL default values were empty in defaultScpTrafficRejectionErrorProfile in the CNC Console. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39352037 | Notification service did not process NF_PROFILE_CHANGED |
An issue was observed in the SCP-Notification pod while processing NF profile change notifications received from NRF after a PATCH request on an NF instance. Doc Impact: There is no documentation impact. |
3 | 25.1.203 |
| 39329422 | TLS handshake did not send the full certificate chain |
SCP 25.1.202 could not be configured to send the full certificate chain in a TLS handshake. Doc Impact: There is no documentation impact. |
3 | 25.1.202 |
| 39318652 | Incorrect allowed values for reRouteConditionList |
The CNC Console displayed incorrect allowed values for reRouteConditionList in Next Hop Proxy Routing Config. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39316730 | Default port not added to a URI |
The default port was not added to a URI when callBackUri did not specify an explicit port. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39308577 | Incorrect reRouteConditionList values in the REST API Guide |
The SCP REST API Guide listed incorrect defaultValue and allowedRange values for reRouteConditionList in nextHopProxyRoutingConfig. Doc Impact: Corrected the defaultValue and allowedRange for "reRouteConditionList" in Oracle Communications Cloud Native Core, Service Communication Proxy REST Specification Guide. |
3 | 25.2.202 |
| 39251727 | 504 error for a UDR profile with an empty IPv4 address |
SCP returned a 504 "Gateway Timeout" error when a UDR profile used an empty IPv4 address and the UDR profile instance ID and service instance ID were the same. Doc Impact: There is no documentation impact. |
3 | 25.1.204 |
| 39244745 | SCP profiles not updated with correct ports |
SCP profiles were not updated with the correct ports. Doc Impact: There is no documentation impact. |
3 | 25.2.102 |
| 39158867 | SCPC subscription and notification Grafana panels not working |
The SCPC-Subscription and SCPC-Notification Grafana panels did not work. Doc Impact: There is no documentation impact. |
3 | 25.2.201 |
| 39130117 | ocscp_nf_type incorrectly pegged as SEPP |
The ocscp_nf_type metric dimension was incorrectly pegged as SEPP for custom roaming proxy requests in ocscp_metric_http_ar_tx_req_total. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39123519 | Incorrect discovery request type in a metric |
The ocscp_worker_local_discovery_processing_time_total metric reported ocscp_nfdiscovery_req_type as MODELD_DELEG_DISC_REQ for Model-C discovery requests. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39107534 | Upstream service time panel did not display values |
The "SCP Upstream Service Time" Grafana panel did not display maximum, average, or current values. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 39007898 | Incorrect inter-SCP routing for default notifications |
Inter-SCP routing was incorrect for default notifications for Model-C and Model-D. Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 38973405 | ocscp_worker_transaction_time_exhausted_total did not peg reliably |
The ocscp_worker_transaction_time_exhausted_total metric failed to peg randomly. Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 38964285 | Complete budget allocated to the target API root header attempt |
For a delayed discovery request with Timestamp Header enabled, the complete budget was allocated to the target-api-root header attempt. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38924939 | ocscp_requester_nf_type reported as NA |
The enhanced priority capacity metric reported ocscp_requester_nf_type as NA. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38920538 | Different PATCH request behavior for roaming proxy NFs |
After the NF_DEREGISTRED event, the producer NF profile remained in OCSCP_NW_TOPOLOGY_NF_PROFILES and could still be updated by patch requests during the grace period, whereas the custom roaming proxy profile was deleted and could not be updated. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38872318 | PUT API response returned null timestamps |
The PUT API response returned null timestamps. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38810553 | Incorrect static NF discovery metric values |
Static NF Discovery reported incorrect ocscp_nf_setid and ocscp_alternate_route_type values when the primary NF was unavailable. Doc Impact: There is no documentation impact. |
3 | 25.2.200 |
| 38743406 | SCPCacheQueuesUtilizationAboveCriticalThreshold alert raised |
The SCPCacheQueuesUtilizationAboveCriticalThreshold alert was raised with 730K MPS and 1200 NF profiles. Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 38743377 | SCPCoherenceCacheHitsRateAboveThreshold alert raised |
The SCPCoherenceCacheHitsRateAboveThreshold alert was raised with 730K MPS and 1200 NF profiles. Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 38719001 | Certificate-expiry metric and alert file required a rename |
The ocscp_metric_ssl_certificate_expire_total metric and its alert file required a rename. Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 38444819 | Mediation service updated a discovery target header only once |
The SCP Mediation service updated the 3gpp-sbi-discovery-target-nf-type header only once when a mediation rule configured two updates. Doc Impact: There is no documentation impact. |
3 | 25.2.100 |
| 38317992 | Worker pod throttled egress traffic without a maximum concurrent stream |
An SCP-Worker pod throttled egress traffic when the remote server did not send a maximum concurrent stream. Doc Impact: There is no documentation impact. |
3 | 25.1.100 |
| 38209469 | Exceptions occurred after an upgrade |
Multiple exceptions occurred on worker and configuration pods after an upgrade. Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 38071919 | Port not derived for ModelD Notification |
The port was not derived from NFProfileLevelAttrConfig for ModelD Notification, and SCP used hardcoded port 80 for alternate routing. Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 37969345 | Case-insensitive nfType handling in the topology source information REST API |
The topologysourceinfo REST API did not handle nfType as case-sensitive. Doc Impact: Added information about nfType case sensitivity to the "Topology Source Info REST API" in Oracle Communications Cloud Native Core, Service Communication Proxy REST Specification Guide. |
3 | 23.4.0 |
| 37554502 | Worker pod restarted with overload errors |
A newly spawned SCP worker pod restarted with overload errors after 25% or 50% of SCP worker pods entered a restart state. Doc Impact: There is no documentation impact. |
3 | 25.1.100 |
| 39708559 | RX_TX_MSG_INFO log level missing in the console GUI |
The CNC console did not display the RX_TX_MSG_INFO log level. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39684540 | retry-after header sometimes not honored |
The retry-after header was sometimes not honored, and traffic was sent to the same NF. Doc Impact: There is no documentation impact. |
4 | 25.2.203 |
| 39597248 | Incorrect allowed value for the redirectURL parameter |
The SCP REST API Guide incorrectly listed “NA” as an allowed value for the redirectURL parameter. Doc Impact: Updated the allowed value of the "redirectURL" parameter in Oracle Communications Cloud Native Core, Service Communication Proxy REST Specification Guide. |
4 | 26.1.200 |
| 39597052 | ocscp_authority dimension appeared after disablement |
The ocscp_authority dimension continued to appear in metrics after disablement. Doc Impact: Updated the description of the "ocscp_metric_http_rx_req_total" metric in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
4 | 26.1.200 |
| 39590718 | ocscp_cause values missing for rate-limiting-not-applied metrics |
The ocscp_cause values were not documented for rate-limiting-not-applied metrics in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. Doc Impact: Added the "ocscp_cause" dimension in the "ocscp_metric_egress_rate_limiting_not_applied_req_total" and "ocscp_metric_ingress_rate_limiting_not_applied_req_total" metrics in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
4 | 26.1.200 |
| 39581566 | Incorrect metric parameter example | The user guide included an incorrect metric parameter example.
Doc Impact: Updated the example of the "ocscp_metric_egress_rate_limiting_not_applied_req_total" metric in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
4 | 26.1.200 |
| 39476699 | Egress congestion control did not throttle traffic |
SCP did not throttle traffic for egress congestion control. Doc Impact: There is no documentation impact. |
4 | 25.2.102 |
| 39436160 | ocscp_metric_scp_generated_response_total pegged twice |
The ocscp_metric_scp_generated_response_total metric was pegged twice because of a race condition between the normal termination path and total transaction timeout. Doc Impact: There is no documentation impact. |
4 | 26.1.200 |
| 39417794 | ocscp_fqdn missing from a deregistration metric |
The user guide did not document ocscp_fqdn for ocscp_subscription_nrf_deregistration_success_total. Doc Impact: Added "ocscp_fqdn" to the "ocscp_subscription_nrf_deregistration_success_total" metric dimension and example in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
4 | 26.1.200 |
| 39392109 | Alarm OID query issue |
An alarm OID query issue occurred. Doc Impact: There is no documentation impact. |
4 | 25.2.102 |
| 39107451 | Requester NF type list option returned an error |
The "*" option in the CNCC GUI returned an error for Requester NF Type List in NF Discovery Mode Config. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38962325 | Incomplete validation message for discovery mode fallback criteria |
The validation message for Discovery Mode Fallback Criteria did not list the supported connectionError and timeout options. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38947469 | Incorrect error cause for a missing mandatory API parameter |
SCP returned an incorrect error cause when a mandatory parameter was missing in a Proxy Selection Routing Mode API request. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 38930373 | Incorrect error cause for an invalid congestion-control configuration value |
SCP returned an incorrect error cause when nextHopProxyNfServiceData.nfServiceLoadBasedCongestionControlCfg had an invalid value. Doc Impact: There is no documentation impact. |
4 | 25.2.200 |
| 39504439 | ocscp_locality is missing in ocscp_metric_scp_generated_response_total of user guide. |
The SCP user guide does not document the ocscp_locality for ocscp_metric_scp_generated_response_total metric. Doc Impact: Added the missing "ocscp_locality" dimension for the "ocscp_metric_scp_generated_response_total" metric in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
4 | 26.1.200 |
| 38815291 | Enhanced Consumer NF Selection Info Auto-Selected Causes 400 Error During NF Selection Mode Update. |
Auto-selecting Enhanced Consumer NF Selection Info causes a 400 error during an NF Selection Mode update. Doc Impact: Updated NF Selection Mode documentation for Enhanced Consumer NF Selection configuration in the "CNC Console" section in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide. |
4 | 25.2.200 |
| 38395424 | Missing and Incorrect Parameters in Official SCP Documentation | Some of the Helm parameters were missing from the Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.
Doc Impact: Added the missing Helm parameters in the "Global Parameters" section in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide. |
4 | 25.2.100 |
Note:
Resolved bugs from 25.2.100, 25.2.204, and 26.1.200 have been forward ported to Release 26.1.201.Release 26.1.201
Table 4-16 SCP ATS 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39680503 | SCP0015 WS1.5 full regression failed |
The metric validation failed for ocscp_metric_ingress_rate_limiting_not_applied_req_total. Doc Impact: There is no documentation impact. |
3 | 25.2.203 |
| 39108180 | NF Profile Configuration PUT API did not return a response |
The NF Profile Configuration PUT REST API did not return a response when the profile was successfully registered or updated. Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
Note:
Resolved bugs from 25.2.2xx and 26.1.200 have been forward ported to Release 26.1.201.4.2.13 Common Services Resolved Bugs
4.2.13.1 Egress Gateway Resolved Bugs
Release 26.1.201
Table 4-17 Egress Gateway 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 37696738 | IRC exceptions are not updating in Grafana or Prometheous only in the PODs logs its updated | IRC exceptions were logged in pods but were not reflected in Grafana or Prometheus for http_server_requests_seconds_count and oc_ingressgateway_http_responses_total.
Doc Impact There is no documentation impact. |
3 | 25.1.100 |
| 38953545 | "jetty parameter MaxResponseHeadersSize" boundary check is missing | The boundary validation for jettyMaxResponseHeadersSize was missing, allowing an installation to complete while Ingress Gateway entered CrashLoopBackOff.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
| 39162947 | Changing serviceMeshEnabled using setter method is not changing the serviceDiscoveryMechanism | Changing serviceMeshEnabled through its setter did not update serviceDiscoveryMechanism.
Doc Impact There is no documentation impact. |
2 | 26.1.200 |
| 39181670 | None of the Grfana Panels are updating in the Latest OCCNE Cluster(25.2.200) | Grafana panels did not update with the latest Ingress Gateway traffic, latency, memory, and CPU results on 25.2.200.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
| 39083890 | EGW logs for message "HTTP response body is empty" doesn't contains ocLogId | Egress Gateway logs for the "HTTP response body is empty" message did not contain ocLogId, preventing ocLogId-based log filtering.
Doc Impact There is no documentation impact. |
3 | 25.2.108 |
| 39154470 | SBI Service Operations CNCC screen is not allowing to save modified entry | The SBI Service Operations screen did not save a configuration with a blank initiatedRequestPriorityRule or responsePriorityRule and returned HTTP 400 CFG-E107.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.201.Release 26.1.200
Table 4-18 Egress Gateway 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
|
38522842 |
First lookup call to ARS is failing for configured vFQDN | The initial Alternate Route Service lookup for a configured vFQDN failed, although subsequent lookups succeeded.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
38405814 |
Post_rollback_SM_Validation fails at alternate-route logging level validation | After the rollback, system-manager validation failed while validating the Alternate Route Service logging level.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38997505 |
Unformatted WARN log "WARN found 2 argument placeholders, but provided 3 for pattern " is seen inpre-upgrade hook logs of alternate route, ingress-gw and egress-gw | The preupgrade hooks logged an unformatted WARN message because the placeholder count did not match the supplied arguments.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38513360 |
IGW/EGW/ARS Deployment YAML having both "replicas" and "minReplicas/maxReplicas" | The deployment YAML file included both replicas and minReplicas/maxReplicas settings.
Doc Impact: There is no documentation impact. |
3 |
25.1.205 |
|
39060179 |
Upgrade to 26.1.2xx fails at nrf-client-nfdiscovery-pre-upgrade hook | The upgrade to Gateway Services 26.1.2xx failed in the nrf-client-nfdiscovery pre-upgrade hook.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38461465 |
Sender Attribute should only consist SEPP-<sepp-fqdn> when addtional error logging in enabled in gw logging config | When additional error logging was enabled, the Gateway Services sender attribute was incorrectly populated.
Doc Impact: There is no documentation impact. |
4 |
25.2.100 |
|
39043146 |
Common-config-hook 26.1.200-rc.3 giving APPLICATION FAILED TO START error in app-info microservice hooks | The common-config hook caused the app-info microservice hooks to fail with an application-start error.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39061499 |
Common-Config: Alter Command not allowed | Common Config did not allow the required ALTER command.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38246506 |
When EGW request for the "defaultNRFInstance" then "oc_oauth_nrf_request_total" metric is not updated | Egress Gateway did not update the oc_oauth_nrf_request_total metric when it requested defaultNRFInstance.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38179718 |
In oc_egressgateway_http_responses_total metric NFTYPE should be corrected and No traffic drop observed | The oc_egressgateway_http_responses_total metric reported an incorrect NF type.
Doc Impact: There is no documentation impact. |
4 |
24.2.15 |
|
38235950 |
NPE seen in egress gateway after pod restart | Egress Gateway logged a NullPointerException after its pods restarted.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38551540 |
Call rejected with Status 0 in EGW 25.2.200-rc.1 build. | Egress Gateway rejected calls with status 0.
Doc Impact: There is no documentation impact. |
3 |
25.2.200-rc.1 |
|
38585721 |
High CPU and Memory usage in EGW 25.2.200-rc.1 build as compared with previous build 25.2.100. | Egress Gateway used significantly more CPU and memory than the previous build.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38596250 |
404 NOT_FOUND ERROR and traffic failure observed at EGW | Egress Gateway returned 404 NOT_FOUND responses and caused traffic failures.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
38433760 |
EGW is sending data packets followed by header with some delay resulting which calls are failing. | Egress Gateway sent data packets before their headers, with a delay that caused calls to fail.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38644699 |
TTL value in lookup is showing greater than the value defined in DNS SRV records in ARS 25.2.200-rc.1 | Alternate Route Service reported a DNS lookup TTL greater than the TTL configured in DNS SRV records.
Doc Impact: There is no documentation impact. |
2 |
25.2.200-rc.1 |
|
38575922 |
Inclusion of Configurable flags to enable/disable addition of X-Fowarded headers by SCG in EGW values.yaml | Egress Gateway's values.yaml file did not provide attributes to control SCG addition of X-Forwarded headers.
Doc Impact: There is no documentation impact. |
3 |
25.2.200-rc.1 |
|
38702789 |
Peer health ping request getting timed out when EGW is freshly installed/upgradedin dual stack with IPv6 address | Peer-health ping requests timed out after a fresh installation or upgrade in dual-stack IPv6 deployments.
Doc Impact: There is no documentation impact. |
2 |
25.1.207 |
|
38661262 |
HealthStatus/peerSet GET, giving 500 , NULL POINTER EXCEPTION in response | The HealthStatus/peerSet GET request returned HTTP 500 with a NullPointerException.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38434182 |
Policy upgrade failing due to EGW failed to connect to database while upgrading from 25.1.200 to 25.2.101-rc.1 | A Policy upgrade failed because Egress Gateway could not connect to the database.
Doc Impact: There is no documentation impact. |
3 |
25.2.101 |
|
38828633 |
Scheme change for the same host:port was not handled correctly during concurrent updates | Concurrent updates did not correctly handle a scheme change for the same host and port.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38515750 |
EGW not validating the LCI configure parameter loadThreshold present or not | Egress Gateway did not validate whether the LCI loadThreshold parameter was present.
Doc Impact: There is no documentation impact. |
4 |
25.2.102 |
|
38522816 |
EGW fails to build peer health table after initial ARS call fails | Egress Gateway did not build the peer-health table when the initial Alternate Route Service call failed.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
38719525 |
peer health status is showing incorrect peer scheme for https peer in EGW 25.2.105 build | Egress Gateway reported an incorrect peer scheme for HTTPS peers.
Doc Impact: There is no documentation impact. |
2 |
25.2.105 |
|
38795596 |
During EGW Upgrade from 25.1.203 to 25.2.106 Observed "java.io.InvalidClassException" on new 25.2.106 egw pods and No traffic drop observed. | Egress Gateway pods logged java.io.InvalidClassException during the upgrade.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38901642 |
PCF using expired token (26.1.200) | PCF used an expired token.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
38902573 |
Newly Updated DNS entries are not updating to EGW peer health table | Newly updated DNS entries were not reflected in the Egress Gateway peer-health table.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38704688 |
EGW peer health status is inconsistent in case of multiple EGW pods in IPv6 with a synchronization delay of ~>=1min | Multiple Egress Gateway pods reported inconsistent peer-health status in IPv6 deployments after a synchronization delay.
Doc Impact: There is no documentation impact. |
2 |
25.1.207 |
|
38537310 |
Getting Intermittent error logs on PLMN EGW while running traffic | PLMN Egress Gateway generated intermittent error logs while traffic was running.
Doc Impact: There is no documentation impact. |
3 |
25.1.201 |
|
38856622 |
EGW - Error Response enhancement validation failing when All peers are Unhealthy | Egress Gateway error-response enhancement validation failed when every peer was unhealthy.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38661597 |
Metric oc_egressgateway_peer_health_status showing incorrect peer status in EGW 25.1.207-beta.1/25.2.106 build. | The oc_egressgateway_peer_health_status metric reported incorrect peer status.
Doc Impact: There is no documentation impact. |
3 |
25.1.206 |
|
38894990 |
PCF EGW not giving precedence to IPV6 and resolving to IPV4 address | PCF Egress Gateway resolved IPv4 addresses instead of preferring IPv6 addresses.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
38957729 |
EGW is not able to send access token request towards NRF in TLS enabled setup. | Egress Gateway could not send access-token requests to NRF in a TLS-enabled deployment.
Doc Impact: There is no documentation impact. |
2 |
25.1.208 |
|
38902994 |
Peer Monitoring feature not working | The peer-monitoring feature did not work.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39049489 |
EGW 26.1.200-rc.3: EGW not giving precedence to IPv6 while initiating the connection towards NRF(Oauth) and Producer perfgo with IPv6_IPv4 based deployment in dual stack supported cluster. | Egress Gateway did not prefer IPv6 when connecting to NRF or to the producer in a dual-stack deployment.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38066375 |
Gateway is returning incorrect error when the cause is final request timeout is <=0 | Gateway Services returned an incorrect error when the final request timeout was less than or equal to zero.
Doc Impact: There is no documentation impact. |
4 |
25.1.201 |
|
38998368 |
EGW pods are restarting while running traffic | Egress Gateway pods restarted while processing traffic.
Doc Impact: There is no documentation impact. |
2 |
25.2.108 |
|
38239527 |
For status code "404 " oc_egressgateway_http_responses_total metrics are not updated | The oc_egressgateway_http_responses_total metric was not updated for HTTP 404 responses.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
39074445 |
Traffic failure on EGW when x-http2-scheme is added in GlobalRequestRemoveHeader | Egress Gateway traffic failed when x-http2-scheme was configured for request-header removal.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38902440 |
EGW is not removing headers present in globalRemoveRequestHeader and removeRequestHeader at Global and route level when forwarding the request towards Server | Egress Gateway did not remove configured global and route-level request headers before forwarding requests.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
36891476 |
Default "expiry_in" timer should be configured in EGW for access token | Egress Gateway did not configure a default expiry_in timer for access tokens.
Doc Impact: There is no documentation impact. |
3 |
24.2.5 |
|
38257511 |
For "Expire_in" zero value EGW always taking token from Cache. after this scenario EGW will not send any request to NRF | When expiry_in was zero, Egress Gateway always used the cached token and stopped sending token requests to NRF.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38920277 |
EGW default custom yaml has duplicate keys. | The default Egress Gateway custom-values.yaml file contained duplicate keys.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39148753 |
Metric 'oc_cnc_jetty_connections_active' pegged in EGW for both intraNF and interNF connections in 26.1.200-rc.4. | The oc_cnc_jetty_connections_active metric remained pegged for intra-NF and inter-NF connections.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39062313 |
3Gpp-Sbi-Lci header is not being sent out from EGW | Egress Gateway did not send the 3Gpp-Sbi-Lci header.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38592367 |
CNC - jetty : Boundary values are not Validated in the newly introduced and old parameters. | CNC Jetty did not validate boundary values for new and existing parameters.
Doc Impact: There is no documentation impact. |
3 |
25.2.200-rc.1 |
|
38552272 |
EGW rejects requests when enableOutgoingHTTP1 is enabled and the oc-http-version: http1 header is present. | Egress Gateway rejected requests when outgoing HTTP/1 was enabled and the HTTP/1 version header was present.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38504941 |
EGW/IGW should include LCI header when the current load is less than or equals to the difference between previously reported load and configured LoadThreshold value | Egress Gateway and Ingress Gateway did not include the LCI header when the load-threshold condition was met.
Doc Impact: There is no documentation impact. |
3 |
25.2.102 |
|
38789763 |
IGW/EGW Pods are not coming up when localLciHeaderValidity is assigned with value 14400000, under lciheaderconfig | Ingress Gateway and Egress Gateway pods did not start when localLciHeaderValidity was set to 14400000.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38818360 |
ASM : helm install is failing with execution error at "custom-header.tpl:3:3): defaultVal is null" and same working fine in the 25.1.207 build | ASM Helm installation failed because custom-header.tpl received a null default value.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
38460669 |
Requesting APIGW to provide a metric which give NFs the end to end latency | APIGW did not provide a metric for end-to-end NF latency.
Doc Impact: There is no documentation impact. |
Requesting APIGW to provide a metric which give NFs the end to end latency |
25.2.101 |
|
38828770 |
/nf-common-component/v1/igw/applicationparams API is returning multiple entries during Policy NF upgrade causing pod resrarts on audit service of PCF | The applicationparams API returned multiple entries during a Policy NF upgrade, causing audit-service pods to restart.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38861854 |
Increase of failure rate % after in service upgrade to 24.2.4 and to 25.1.202 |
The traffic failure rate increased after in-service upgrades.
Doc Impact: There is no documentation impact. |
2 |
24.2.13 |
|
38992190 |
prioritymappingrules accepts invalid received range format without validation | prioritymappingrules accepted an invalid received-range format without validation.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38992126 |
prioritymappingrules allows leading-zero values for received/used, causing ambiguous/duplicate priority mappings | prioritymappingrules accepted leading-zero priority values, producing ambiguous or duplicate mappings.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38991946 |
prioritymappingrules validation rejects used as non-integer but rule-level detail is missing | prioritymappingrules rejected a non-integer used value without identifying the affected rule.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38992098 |
prioritymappingrules accepts duplicate received key within a rule object; last value silently overrides earlier value (last-key-wins) | prioritymappingrules accepted duplicate received keys within one rule and silently used the last value.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38992014 |
prioritymappingrules request with duplicate rules key is accepted; earlier rules array is silently overwritten (last-key-wins) | prioritymappingrules accepted duplicate rules keys and silently overwrote the earlier rules array.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38991138 |
PUT global-configuration/sbiserviceoperations behaves inconsistently with duplicate sbiServiceOperation keys (order-dependent) | The sbiserviceoperations PUT request handled duplicate sbiServiceOperation keys inconsistently based on their order.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38645273 |
Signature schemes in certificate request message TLS contains "not supported" values | TLS certificate-request messages included unsupported signature schemes.
Doc Impact: There is no documentation impact. |
3 |
25.1.200 |
|
38953545 |
jetty parameter MaxResponseHeadersSize" boundary check is missing | The non-ASM Jetty MaxResponseHeadersSize parameter did not have boundary validation.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39108214 |
IGW/EGW is not applying default rule while processing SMP Header request even when requestsmpheaders table in CCG is null. | Ingress Gateway and Egress Gateway did not apply the default rule to SMP-header requests when the requestsmpheaders table was null.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39009617 |
common_configuration_global table is getting updated even though applyHelmConfigOnUpgrade is set to false with HELM upgrade. | A Helm upgrade updated common_configuration_global even when applyHelmConfigOnUpgrade was false.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38943732 |
During upgrade and Rollback from 25.2.107 to 26.1.200-rc1 32% and 47%traffic loss observed. | Upgrade and rollback caused substantial traffic loss.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39028063 |
ASM:wrong error detail when helm upgraded with Pseudo range values in priority mapping rule configuration | An ASM Helm upgrade returned incorrect error details for pseudo-range priority-mapping values.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39005829 |
requestsmpheaders duplicate validation is case-sensitive | requestsmpheaders duplicate validation was case-sensitive.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
39020622 |
No Input Validation on requestsmpheaders PUT Endpoint | The requestsmpheaders PUT endpoint did not validate input.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39033197 |
ASM:Error description for HELM upgrade failure and REST base upgrade failure should be in sync | Helm and REST-based upgrades returned inconsistent error descriptions for the same failure.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39031628 |
Not allowing sbiserviceoperations to be configured without initiatedRequestPriorityRule and responsePriorityRule key parameters using HELM install/upgrade | Helm installation and upgrade did not allow sbiserviceoperations to be configured without its priority-rule keys.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39046579 |
Outgoing message missing defaultSmpHeaderName name when incoming 3gpp-sbi-message-priority header value is out of range | Outgoing messages omitted defaultSmpHeaderName when the incoming message-priority value was out of range.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39155503 |
Wrong error message is sent in response when initiatedRequestPriorityRule or responsePriorityRule are empty or null | The response returned an incorrect error message when either priority rule was empty or null.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39154470 |
SBI Service Operations CNCC screen is not allowing to save modified entry | The SBI Service Operations CNC Console screen did not allow a modified entry to be saved.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38974389 |
To provide updated Grafana json wrt Spring Boot to 3.2.x upgrade changes for both IGW and EGW. | Grafana JSON was not updated for the Spring Boot 3.2.x changes.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39128713 |
no match route exception from egress gateway. | Egress Gateway returned a no-match-route exception.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38992215 |
prioritymappingrules inconsistent validation/error messaging for defaultSmpHeaderName when empty string vs null | prioritymappingrules handled an empty defaultSmpHeaderName inconsistently with a null value.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38162347 |
for Custom Header request using REST-API, the complete array is not getting validated | REST API validation for custom-header requests did not validate the entire array.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
36820640 |
Error Detail response for common config is not having Servicename and AppErrorCode in Error detail | Common Config error-detail responses omitted the service name and application error code.
Doc Impact: There is no documentation impact. |
3 |
24.2.4 |
|
35505051 |
Custom Package logging support for IGW & EGW | Ingress Gateway and Egress Gateway did not support custom-package logging.
Doc Impact: There is no documentation impact. |
3 |
23.2.0 |
|
38271114 |
Gateway configuration rollback does not work using FluxCD when it upgrades to a version it was deployed earlier | FluxCD could not roll back Gateway Services configuration to a version that had previously been deployed.
Doc Impact: There is no documentation impact. |
3 |
NA |
|
37914904 |
Required Grafana dashboard JSON containing all the metrics for PI-B-25 PoP25 feature (IGW+EGW) along with Traffic success | The required Grafana dashboard JSON did not include all relevant metrics and traffic-success information.
Doc Impact: There is no documentation impact. |
4 |
25.1.200 |
|
34920448 |
NRF-Incorrect API gives 200 OK and creating config entry in DB for altRoute/logging | An invalid NRF API request returned HTTP 200 and created a configuration entry in the database.
Doc Impact: There is no documentation impact. |
4 |
22.2.0 |
|
38324716 |
Mounting of secrets is not backward compatible approach | Secret mounting was not backward compatible.
Doc Impact: There is no documentation impact. |
3 |
25.1.200 |
|
38611657 |
CNCC Ingress Gateway 500 – reqHeaders null at CnccAuthorizationUtil.setRequestAttributes |
The Spring Boot uplift caused Ingress Gateway to throw a null Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
38827897 |
cnc_jetty_service_discovery metrics incorrectly pegged with value zero in ASM deployment | In ASM deployments, the cnc_jetty_service_discovery metrics incorrectly remained at 0.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.200.4.2.13.2 Ingress Gateway Resolved Bugs
Release 26.1.201
Table 4-19 Ingress Gateway 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 37696738 | IRC exceptions are not updating in Grafana or Prometheous only in the PODs logs its updated | IRC exceptions were logged in pods but were not reflected in Grafana or Prometheus for http_server_requests_seconds_count and oc_ingressgateway_http_responses_total.
Doc Impact There is no documentation impact. |
3 | 25.1.100 |
| 38953545 | "jetty parameter MaxResponseHeadersSize" boundary check is missing | The boundary validation for jettyMaxResponseHeadersSize was missing, allowing an installation to complete while Ingress Gateway entered CrashLoopBackOff.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
| 39162947 | Changing serviceMeshEnabled using setter method is not changing the serviceDiscoveryMechanism | Changing serviceMeshEnabled through its setter did not update serviceDiscoveryMechanism.
Doc Impact There is no documentation impact. |
2 | 26.1.200 |
| 39181670 | None of the Grfana Panels are updating in the Latest OCCNE Cluster(25.2.200) | Grafana panels did not update with the latest Ingress Gateway traffic, latency, memory, and CPU results on 25.2.200.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
| 39083890 | EGW logs for message "HTTP response body is empty" doesn't contains ocLogId | Egress Gateway logs for the "HTTP response body is empty" message did not contain ocLogId, preventing ocLogId-based log filtering.
Doc Impact There is no documentation impact. |
3 | 25.2.108 |
| 39178062 | IGW rejecting accesstoken requests with 503 backend not able to handle traffic | Ingress Gateway rejected access-token requests with HTTP 503 under discovery traffic because requests were not sent to the access-token back end.
Doc Impact There is no documentation impact. |
2 | 26.1.200 |
| 39158501 | In IGW:26.1.200 the functionality of Content-Length and Content-Type headers are not working properly | Ingress Gateway incorrectly appended Content-Type: application/octet-stream and handled Content-Length inconsistently for empty POST requests.
Doc Impact There is no documentation impact. |
2 | 26.1.200 |
| 39171586 | Cause "OAuth access Token is not present at IGW"" error "oc_ingressgateway_http_requests_total" metrics are not updated & "oc_ingressgateway_http_responses_total" updated | For the HTTP 401 "OAuth access Token is not present at IGW" error, oc_ingressgateway_http_requests_total was not updated while oc_ingressgateway_http_responses_total was updated.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
| 39170610 | Incorrect Request Count Metric oc_ingressgateway_http_requests_total – Underreporting Total Requests at Pod Level |
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
| 39154470 | SBI Service Operations CNCC screen is not allowing to save modified entry | The SBI Service Operations screen did not save a configuration with a blank initiatedRequestPriorityRule or responsePriorityRule and returned HTTP 400 CFG-E107.
Doc Impact There is no documentation impact. |
3 | 26.1.200 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.201.Release 26.1.200
Table 4-20 Ingress Gateway 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
|
38522842 |
First lookup call to ARS is failing for configured vFQDN | The initial Alternate Route Service lookup for a configured vFQDN failed, although subsequent lookups succeeded.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
38405814 |
Post_rollback_SM_Validation fails at alternate-route logging level validation | After the rollback, system-manager validation failed while validating the Alternate Route Service logging level.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38997505 |
Unformatted WARN log "WARN found 2 argument placeholders, but provided 3 for pattern " is seen inpre-upgrade hook logs of alternate route, ingress-gw and egress-gw | The preupgrade hooks logged an unformatted WARN message because the placeholder count did not match the supplied arguments.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38513360 |
IGW/EGW/ARS Deployment YAML having both "replicas" and "minReplicas/maxReplicas" | The deployment YAML file included both replicas and minReplicas/maxReplicas settings.
Doc Impact: There is no documentation impact. |
3 |
25.1.205 |
|
39060179 |
Upgrade to 26.1.2xx fails at nrf-client-nfdiscovery-pre-upgrade hook | The upgrade to Gateway Services 26.1.2xx failed in the nrf-client-nfdiscovery pre-upgrade hook.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38461465 |
Sender Attribute should only consist SEPP-<sepp-fqdn> when addtional error logging in enabled in gw logging config | When additional error logging was enabled, the Gateway Services sender attribute was incorrectly populated.
Doc Impact: There is no documentation impact. |
4 |
25.2.100 |
|
39043146 |
Common-config-hook 26.1.200-rc.3 giving APPLICATION FAILED TO START error in app-info microservice hooks | The common-config hook caused the app-info microservice hooks to fail with an application-start error.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39061499 |
Common-Config: Alter Command not allowed | Common Config did not allow the required ALTER command.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38592367 |
CNC - jetty : Boundary values are not Validated in the newly introduced and old parameters. | CNC Jetty did not validate boundary values for new and existing parameters.
Doc Impact: There is no documentation impact. |
3 |
25.2.200-rc.1 |
|
38552272 |
EGW rejects requests when enableOutgoingHTTP1 is enabled and the oc-http-version: http1 header is present. | Egress Gateway rejected requests when outgoing HTTP/1 was enabled and the HTTP/1 version header was present.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38504941 |
EGW/IGW should include LCI header when the current load is less than or equals to the difference between previously reported load and configured LoadThreshold value | Egress Gateway and Ingress Gateway did not include the LCI header when the load-threshold condition was met.
Doc Impact: There is no documentation impact. |
3 |
25.2.102 |
|
38789763 |
IGW/EGW Pods are not coming up when localLciHeaderValidity is assigned with value 14400000, under lciheaderconfig | Ingress Gateway and Egress Gateway pods did not start when localLciHeaderValidity was set to 14400000.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38818360 |
ASM : helm install is failing with execution error at "custom-header.tpl:3:3): defaultVal is null" and same working fine in the 25.1.207 build | ASM Helm installation failed because custom-header.tpl received a null default value.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
38460669 |
Requesting APIGW to provide a metric which give NFs the end to end latency | APIGW did not provide a metric for end-to-end NF latency.
Doc Impact: There is no documentation impact. |
Requesting APIGW to provide a metric which give NFs the end to end latency |
25.2.101 |
|
38828770 |
/nf-common-component/v1/igw/applicationparams API is returning multiple entries during Policy NF upgrade causing pod resrarts on audit service of PCF | The applicationparams API returned multiple entries during a Policy NF upgrade, causing audit-service pods to restart.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38861854 |
Increase of failure rate % after in service upgrade to 24.2.4 and to 25.1.202 |
The traffic failure rate increased after in-service upgrades.
Doc Impact: There is no documentation impact. |
2 |
24.2.13 |
|
38992190 |
prioritymappingrules accepts invalid received range format without validation | prioritymappingrules accepted an invalid received-range format without validation.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38992126 |
prioritymappingrules allows leading-zero values for received/used, causing ambiguous/duplicate priority mappings | prioritymappingrules accepted leading-zero priority values, producing ambiguous or duplicate mappings.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38991946 |
prioritymappingrules validation rejects used as non-integer but rule-level detail is missing | prioritymappingrules rejected a non-integer used value without identifying the affected rule.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38992098 |
prioritymappingrules accepts duplicate received key within a rule object; last value silently overrides earlier value (last-key-wins) | prioritymappingrules accepted duplicate received keys within one rule and silently used the last value.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38992014 |
prioritymappingrules request with duplicate rules key is accepted; earlier rules array is silently overwritten (last-key-wins) | prioritymappingrules accepted duplicate rules keys and silently overwrote the earlier rules array.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38991138 |
PUT global-configuration/sbiserviceoperations behaves inconsistently with duplicate sbiServiceOperation keys (order-dependent) | The sbiserviceoperations PUT request handled duplicate sbiServiceOperation keys inconsistently based on their order.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38645273 |
Signature schemes in certificate request message TLS contains "not supported" values | TLS certificate-request messages included unsupported signature schemes.
Doc Impact: There is no documentation impact. |
3 |
25.1.200 |
|
38953545 |
jetty parameter MaxResponseHeadersSize" boundary check is missing | The non-ASM Jetty MaxResponseHeadersSize parameter did not have boundary validation.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39108214 |
IGW/EGW is not applying default rule while processing SMP Header request even when requestsmpheaders table in CCG is null. | Ingress Gateway and Egress Gateway did not apply the default rule to SMP-header requests when the requestsmpheaders table was null.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39009617 |
common_configuration_global table is getting updated even though applyHelmConfigOnUpgrade is set to false with HELM upgrade. | A Helm upgrade updated common_configuration_global even when applyHelmConfigOnUpgrade was false.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38943732 |
During upgrade and Rollback from 25.2.107 to 26.1.200-rc1 32% and 47%traffic loss observed. | Upgrade and rollback caused substantial traffic loss.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39028063 |
ASM:wrong error detail when helm upgraded with Pseudo range values in priority mapping rule configuration | An ASM Helm upgrade returned incorrect error details for pseudo-range priority-mapping values.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39005829 |
requestsmpheaders duplicate validation is case-sensitive | requestsmpheaders duplicate validation was case-sensitive.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
39020622 |
No Input Validation on requestsmpheaders PUT Endpoint | The requestsmpheaders PUT endpoint did not validate input.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
39033197 |
ASM:Error description for HELM upgrade failure and REST base upgrade failure should be in sync | Helm and REST-based upgrades returned inconsistent error descriptions for the same failure.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39031628 |
Not allowing sbiserviceoperations to be configured without initiatedRequestPriorityRule and responsePriorityRule key parameters using HELM install/upgrade | Helm installation and upgrade did not allow sbiserviceoperations to be configured without its priority-rule keys.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39046579 |
Outgoing message missing defaultSmpHeaderName name when incoming 3gpp-sbi-message-priority header value is out of range | Outgoing messages omitted defaultSmpHeaderName when the incoming message-priority value was out of range.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39155503 |
Wrong error message is sent in response when initiatedRequestPriorityRule or responsePriorityRule are empty or null | The response returned an incorrect error message when either priority rule was empty or null.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39154470 |
SBI Service Operations CNCC screen is not allowing to save modified entry | The SBI Service Operations CNC Console screen did not allow a modified entry to be saved.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38974389 |
To provide updated Grafana json wrt Spring Boot to 3.2.x upgrade changes for both IGW and EGW. | Grafana JSON was not updated for the Spring Boot 3.2.x changes.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39128713 |
no match route exception from egress gateway. | Egress Gateway returned a no-match-route exception.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38992215 |
prioritymappingrules inconsistent validation/error messaging for defaultSmpHeaderName when empty string vs null | prioritymappingrules handled an empty defaultSmpHeaderName inconsistently with a null value.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38162347 |
for Custom Header request using REST-API, the complete array is not getting validated | REST API validation for custom-header requests did not validate the entire array.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
36820640 |
Error Detail response for common config is not having Servicename and AppErrorCode in Error detail | Common Config error-detail responses omitted the service name and application error code.
Doc Impact: There is no documentation impact. |
3 |
24.2.4 |
|
35505051 |
Custom Package logging support for IGW & EGW | Ingress Gateway and Egress Gateway did not support custom-package logging.
Doc Impact: There is no documentation impact. |
3 |
23.2.0 |
|
38271114 |
Gateway configuration rollback does not work using FluxCD when it upgrades to a version it was deployed earlier | FluxCD could not roll back Gateway Services configuration to a version that had previously been deployed.
Doc Impact: There is no documentation impact. |
3 |
NA |
|
37914904 |
Required Grafana dashboard JSON containing all the metrics for PI-B-25 PoP25 feature (IGW+EGW) along with Traffic success | The required Grafana dashboard JSON did not include all relevant metrics and traffic-success information.
Doc Impact: There is no documentation impact. |
4 |
25.1.200 |
|
34920448 |
NRF-Incorrect API gives 200 OK and creating config entry in DB for altRoute/logging | An invalid NRF API request returned HTTP 200 and created a configuration entry in the database.
Doc Impact: There is no documentation impact. |
4 |
22.2.0 |
|
38324716 |
Mounting of secrets is not backward compatible approach | Secret mounting was not backward compatible.
Doc Impact: There is no documentation impact. |
3 |
25.1.200 |
|
34609880 |
NFType dimension of oc_ingressgateway_http_requests_total is being set to incorrect value | The NFType dimension of the oc_ingressgateway_http_requests_total metric was set to incorrect value.
Doc Impact: There is no documentation impact. |
3 |
22.3.4 |
|
36089938 |
errorcodeserieslist api allows configuration of errorCodeSeries having errorSet with no errorCodes | The errorcodeserieslist REST API allowed configuration of errorCodeSeries having errorSet with no errorCodes.
Doc Impact: There is no documentation impact. |
3 |
23.4.0 |
|
38411251 |
The Ingress gateway is sending 5xx responses while running Restfuzz on the NSSF microservices | The Ingress Gateway was sending 5xx responses while running Restfuzz on the NSSF microservices.
Doc Impact: There is no documentation impact. |
3 |
25.2.101 |
|
38284044 |
oc_oauth_request_failed_cert_expiry Metric not getting pegged | The oc_oauth_request_failed_cert_expiry metric was not recorded.
Doc Impact: There is no documentation impact. |
3 |
25.1.103 |
|
38148295 |
Some of the pod protection parameters validation happening with and without flag enabled. all parameters are not in sync. | Some of the pod protection parameters validation occurred with and without attribute enabled. All the parameters were not in synchronization.
Doc Impact: There is no documentation impact. |
4 |
25.1.200 |
|
38272205 |
fillrate accepting zero value and igw pod is restarting continously when the pop feature is disabled | fillrate was accepting zero value and Ingress Gateway pod was restarting continuously when the Pod Protection using Rate Limiting feature was disabled.
Doc Impact: There is no documentation impact. |
3 |
25.1.200 |
|
35849764 |
Server header populated when nfInstanceId not configured | The Server header populated when nfInstanceId was not configured.
Doc Impact: There is no documentation impact. |
3 |
23.3.4 |
|
38055583 |
all calls are failing when we configured routes via REST with pattern "pattern": "/npcf-smpolicycontrol/**/sm-policies" | All calls failed when routes were configured through REST APIs with pattern "pattern": "/npcf-smpolicycontrol/**/sm-policies".
Doc Impact: There is no documentation impact. |
3 |
25.1.201 |
|
35913266 |
In Policy Mapping Configuration in IGW, for the samplingPeriod parameter, validation of max value of parameter should be necessary | In Policy Mapping Configuration in Ingress Gateway, for the samplingPeriod parameter, validation of maximum value of the parameter was not mandatory.
Doc Impact: There is no documentation impact. |
4 |
23.3.0 |
|
34610831 |
IGW is accepting incorrect API names with out throwing any error | Ingress Gateway accepted incorrect API names without any error.
Doc Impact: There is no documentation impact. |
3 |
22.2.4 |
|
35913238 |
In IGW's Error Code Series Configuration, the names of the exceptionList and errorCodeSeries parameters are not verified. | In Ingress Gateway Error Code Series Configuration, the names of the exceptionList and errorCodeSeries parameters were not verified.
Doc Impact: There is no documentation impact. |
4 |
23.3.0 |
|
35932663 |
Key Validation is missing for IGW pod protection parameter name configuration | The Key validation was missing for the Ingress Gateway pod protection parameter name configuration.
Doc Impact: There is no documentation impact. |
3 |
23.3.3 |
|
38159304 |
IGW is returning two different status codes in error response body when Configurable error code is true and non mandatory parameters are empty in errorCodeProfile. | Ingress Gateway returned two different status codes in error response body when Configurable error code was true and non mandatory parameters were empty in errorCodeProfile.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38470214 |
occnp_oc_ingressgateway_http_responses_total" metric not getting incremented | The occnp_oc_ingressgateway_http_responses_total metric did not get incremented.
Doc Impact: There is no documentation impact. |
3 |
24.2.7 |
|
38293029 |
High CPU utilisation was observed when OAuth feature is enabled with ASM | High CPU utilization was observed when OAuth feature was enabled with ASM.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38329632 |
Rename of the metric name - oc_ingressgateway_http_request_ratelimit_denied_count_total | The oc_ingressgateway_http_request_ratelimit_denied_count_total metric name was not renamed.
Doc Impact: Renamed the oc_ingressgateway_http_request_ratelimit_denied_count_total metric to oc_ingressgateway_http_request_ratelimit_exceed_count_total in Oracle Communications Cloud Native Core, Ingress Gateway User Guide. |
3 |
25.2.100 |
|
36604364 |
KeyId, certName, kSecretName, and certAlgorithm invalid values are not validating in the oauthvalidator configuration | KeyId, certName, kSecretName, and certAlgorithm invalid values were not validate in the oauthvalidator configuration.
Doc Impact: There is no documentation impact. |
3 |
24.1.0 |
|
35946896 |
Inconsistent behavior when Invalid Key vs Key not exist for mTLS | Inconsistent behavior when Invalid Key vs Key did not exist for mTLS.
Doc Impact: There is no documentation impact. |
4 |
23.3.4 |
|
36664352 |
KID is missing in access token, NSSF should send "Kid missing" instead of "kid configured does not match with the one present in the token" | If KID was missing in access token, NSSF should not have sent "Kid missing" instead of "kid configured does not match with the one present in the token".
Doc Impact: There is no documentation impact. |
3 |
24.1.6 |
|
38468707 |
IGW continues discarding discovery requests after overload trigger during ISSU, despite receiving normal load level signals | Ingress Gateway continued discarding discovery requests after overload was triggered during ISSU, despite receiving normal load level signals.
Doc Impact: There is no documentation impact. |
3 |
25.1.205 |
|
38369251 |
observed "Service MapDistCache has been terminated" in the old IGW pod after that new pods are not coming up when some of the IGW pods are deleted |
Observed “Service MapDistCache has been terminated” in the old Ingress Gateway pod. After this, new pods failed to start when some Ingress Gateway pods were deleted. Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38339561 |
Metrics oc_ingressgateway_dd_unreachable and oc_egressgateway_dd_unreachable are not resetting to value zero after connection with DD is restored | The oc_ingressgateway_dd_unreachable and oc_egressgateway_dd_unreachable metrics were not resetting to value 0 after connection with Data Director was restored.
Doc Impact: There is no documentation impact. |
3 |
24.1.5 |
|
38593162 |
Request sent to IGW not getting forwarded to backend service | The request sent to Ingress Gateway was not forwarded to the back-end service.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
37091738 |
HTTP/2 request dropped due to HTTP/1.1 validation | The HTTP/2 request dropped due to HTTP/1.1 validation.
Doc Impact: There is no documentation impact. |
3 |
23.1.0 |
|
38639858 |
Cnc-jetty : TLS-SETUP : IGW connections are increasing trend with kube-api-server when IGW installed freshly and Memory is increasing trend due to this connections. |
Ingress Gateway connections to kube-api-server increased after a fresh Ingress Gateway installation, resulted in an increased memory. Doc Impact: There is no documentation impact. |
2 |
25.2.200-rc.1 |
|
38867575 |
Metric oc_oauth_validation_failure_total with invalid-scope dimension not pegged | The oc_oauth_validation_failure_total metric with the invalid-scope dimension did not peg.
Doc Impact: There is no documentation impact. |
3 |
25.2.107 |
|
38787849 |
New "tokenCacheSize" boundary value validation is not happening eventhough fresh install/upgrade is success. |
New Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38703469 |
allowedClockSkewSeconds IE value is wrongly configured in values.yaml file for IGW | allowedClockSkewSeconds IE value was incorrectly configured in the values.yaml file for Ingress Gateway.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38872538 |
IllegalArgumentException generated while recreating the new URI in Policy ipv6 setup causing all calls to fail with 500 | IllegalArgumentException generated while recreating the new URI in Policy ipv6 setup causing all calls to fail with 500.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38767321 |
NPE and 500 internal ERROR observed in the POP25 error code rejections with configurable ERROR code. | NPE and 500 internal ERROR were observed in the Pod Protection using Rate Limiting error code rejections with configurable ERROR code.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
38702154 |
After 1.5hrs run Continuous IRC are flooding in IGW when IGW freshly installed & Traffic loss is observed from 3K to 1.7K. | Continuous IRC was observed in Ingress Gateway when Ingress Gateway was freshly installed and traffic loss was observed from 3K to 1.7K.
Doc Impact: There is no documentation impact. |
1 |
25.1.207 |
|
38808596 |
IGW failing the oauth token validation due to received token is not a digitally signed token instead NRF ID missing when validation mode is set to KID_PREFERRED | Ingress Gateway failed the OAuth token validation because the received token was not a digitally signed token instead NRF ID.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
38569278 |
Ingress Gateway reports a NullPointerException after the installation of PCF | Ingress Gateway 25.2.200 reported NullPointerException after the installation of PCF.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
38921131 |
When OC discards OverloadControlFilter attempts to update internal metrics using a null key or value, resulting in a NullPointerException in ConcurrentHashMap.put() | When Overload Control is discarded, OverloadControlFilter attempted to update internal metrics using a null key or value, resulted in a NullPointerException in ConcurrentHashMap.put().
Doc Impact: There is no documentation impact. |
2 |
25.2.107 |
|
38462947 |
when 3gpp-Sbi-Correlation-Info is sent with empty value then it is also coming in response as empty when an error occurred at IGW | In Ingress Gateway 25.2.101, when 3gpp-Sbi-Correlation-Info was sent with empty value, it came in the response as empty when an error occurred at Ingress Gateway.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38908067 |
In IGW late arrival & Remove Header feature, call flow fail with the error as no matched http response found which was earlier running fine in 25.2.106 build | In Ingress Gateway late arrival and remove header feature, call flow failed with the error as no matched http response was found.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38831358 |
Non-ASM: Memory leak observed in IGW Non-ASM set-up with 12k traffic, resulting IGW pod restarts after 7days of continuous run | A non-ASM memory leak was observed in an Ingress Gateway non-ASM setup with 12K traffic, resulting in an Ingress Gateway pod restart.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
39064453 |
Label error_reason for metrics occnp_oc_ingressgateway_http_responses_total resulting in high Cardinality | Label error_reason for the occnp_oc_ingressgateway_http_responses_total metric resulted in high cardinality.
Doc Impact: There is no documentation impact. |
2 |
25.2.108 |
|
37079438 |
Routes Configuration under IGW is not raising an error when configured with an error code series id which is not already configured (when serverHeaderDetails param is enabled). | Routes Configuration under Ingress Gateway was not raising an error when configured with an error code series ID, which was not already configured when the serverHeaderDetails parameter was enabled.
Doc Impact: There is no documentation impact. |
4 |
24.3.1 |
|
38537413 |
convertHelmToRest is not merging routesconfiguration after upgrade for serverHeaderDetails | convertHelmToRest was not merging routesconfiguration after upgraded for serverHeaderDetails.
Doc Impact: There is no documentation impact. |
3 |
25.1.201 |
|
37046943 |
Mismatch in IGW occnp_oc_ingressgateway_http_requests_total & occnp_oc_ingressgateway_http_responses_total when request sent with Content-Length:0 and Body- PRESENT | Mismatch in Ingress Gateway occnp_oc_ingressgateway_http_requests_total and occnp_oc_ingressgateway_http_responses_total metrics was observed when the request was sent with Content-Length:0 and Body- PRESENT.
Doc Impact: There is no documentation impact. |
3 |
23.4.6 |
|
37986338 |
for XFCC header failure case "oc_ingressgateway_http_responses_total" stats are not updated | For the XFCC header failure, the oc_ingressgateway_http_responses_total metric was not updated.
Doc Impact: There is no documentation impact. |
4 |
25.1.200 |
|
38787543 |
With ratelimit feature , traffic rejections stats(oc_ingressgateway_http_responses_total) are not updated | With the rate limit feature, traffic rejections stats (oc_ingressgateway_http_responses_total) were not updated.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
37663139 |
For 404 not found "oc_ingressgateway_http_requests_total" metrics are not updated only "oc_ingressgateway_http_responses_tota" updated | For 404 not found, the oc_ingressgateway_http_requests_total metric was not updated only oc_ingressgateway_http_responses_tota was updated.
Doc Impact: There is no documentation impact. |
4 |
24.2.12 |
|
38908204 |
In IGW Remove Header feature , IGW is not removing headers mentioned in removeRequestHeader and globalRemoveRequestHeader while forwarding the request to backend servcie. | In the Ingress Gateway Remove Header feature, Ingress Gateway was not removing headers mentioned in removeRequestHeader and globalRemoveRequestHeader while forwarding the request to the back-end service.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38879902 |
Misconfiguration + Pod Restart (multi fault scenario) leads to 100% traffic failure | Repeated Ingres Gateway pods restarted under load caused some pods to fail to load REST-mode route configurations, resulted in persistent 404 errors and an ingress traffic success rate drop by approximately 9%.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
38691258 |
oc_oauth_keyid_count_total metric is not incrementing when validation mode is KID_PREFERRED/KID_ONLY | The oc_oauth_keyid_count_total metric did not increment when validation mode was KID_PREFERRED/KID_ONLY.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
39151303 |
separate CIS/F5 labels for *-ingress-gateway-intra-nf service | In Gateway Services CNC Console 25.2.x, the *-ingress-gateway-intra-nf service inherited the main *-ingress-gateway service’s F5 CIS labels, caused F5/CIS mapping conflicts and external FQDN routing issues in Webscale 1.3.
Doc Impact: There is no documentation impact. |
3 |
25.2.104 |
|
39112904 |
IGW is not adding SMP header to 2xx response when value of oc-backend-generated header is not exactly matched to the value adds-priority | Ingress Gateway was not adding SMP header to 2xx response when the value of oc-backend-generated header was not exactly matched to the value adds-priority.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
|
38602425 |
Incorrect error response from IGW in case of an incorrect URI | Incorrect error response from Ingress Gateway was observed in case of an incorrect URI.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38611657 |
CNCC Ingress Gateway 500 – reqHeaders null at CnccAuthorizationUtil.setRequestAttributes |
The Spring Boot uplift caused Ingress Gateway to throw a null Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
38827897 |
cnc_jetty_service_discovery metrics incorrectly pegged with value zero in ASM deployment | In ASM deployments, the cnc_jetty_service_discovery metrics incorrectly remained at 0.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.200.4.2.13.3 Alternate Route Service Resolved Bugs
Release 26.1.201
Table 4-21 Alternate Route Service 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 38709256 | Rollback fails due to Missing "empty-dir" volumeMount in 24.2.8-rc.3 ARS deployment.yaml (25.1.207) | Rollback failed because the earlier Alternate Route Service deployment.yaml file did not define the empty-dir volumeMount and volume required by the later deployment.
Doc Impact There is no documentation impact. |
3 | 25.1.207 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.200.Release 26.1.200
Table 4-22 Alternate Route Service 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
|
38279138 |
NPE is seen Alternate route service during in-service upgrade from policy 25.1.200 to 25.2.100-rc1 |
NPE was observed alternate route service during in-service upgrade from Policy 25.1.200 to 25.2.100.
Doc Impact: There is no documentation impact. |
4 |
25.2.100 |
|
38240183 |
NullPointerException in new ARS PODS when rollback to 25.1.203 from 25.2.100-rc2. |
NullPointerException was observed in new Alternate Route Sservice pods during rollback to 25.1.203 from 25.2.100.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38594342 |
Alternate Route service reports a NullPointerException after the installation of PCF |
25.2.200 Alternate Route Service reported a NullPointerException after the installation of PCF.
Doc Impact: There is no documentation impact. |
3 |
25.2.200 |
|
38831695 |
Different value getting configured for parameter "refresh-scheduler" in EGW and ARS mircoservice in comparison to what is present in values.yaml |
Different values were getting configured for the parameter "refresh-scheduler" in Egress Gateway and Alternate Route Service mircoservice sin comparison to what was present in values.yaml file.
Doc Impact: There is no documentation impact. |
3 |
25.2.106 |
|
38179432 |
During ARS Upgrade/Rollback from 24.2.13 to 24.2.15 Observed "IllegalStateException" on the 24.2.13 pods and No traffic drop observed | During Alternate Route Service upgrade and rollback from 24.2.13 to 24.2.15, "IllegalStateException" was observed on the 24.2.13 pods with no traffic drop.
Doc Impact: There is no documentation impact. |
3 |
24.2.15 |
|
38522842 |
First lookup call to ARS is failing for configured vFQDN | The initial Alternate Route Service lookup for a configured vFQDN failed, although subsequent lookups succeeded.
Doc Impact: There is no documentation impact. |
3 |
25.1.203 |
|
38405814 |
Post_rollback_SM_Validation fails at alternate-route logging level validation | After the rollback, system-manager validation failed while validating the Alternate Route Service logging level.
Doc Impact: There is no documentation impact. |
3 |
25.2.100 |
|
38997505 |
Unformatted WARN log "WARN found 2 argument placeholders, but provided 3 for pattern " is seen inpre-upgrade hook logs of alternate route, ingress-gw and egress-gw | The preupgrade hooks logged an unformatted WARN message because the placeholder count did not match the supplied arguments.
Doc Impact: There is no documentation impact. |
4 |
26.1.200 |
|
38513360 |
IGW/EGW/ARS Deployment YAML having both "replicas" and "minReplicas/maxReplicas" | The deployment YAML file included both replicas and minReplicas/maxReplicas settings.
Doc Impact: There is no documentation impact. |
3 |
25.1.205 |
|
39060179 |
Upgrade to 26.1.2xx fails at nrf-client-nfdiscovery-pre-upgrade hook | The upgrade to Gateway Services 26.1.2xx failed in the nrf-client-nfdiscovery pre-upgrade hook.
Doc Impact: There is no documentation impact. |
2 |
25.2.200 |
|
38461465 |
Sender Attribute should only consist SEPP-<sepp-fqdn> when addtional error logging in enabled in gw logging config | When additional error logging was enabled, the Gateway Services sender attribute was incorrectly populated.
Doc Impact: There is no documentation impact. |
4 |
25.2.100 |
|
39043146 |
Common-config-hook 26.1.200-rc.3 giving APPLICATION FAILED TO START error in app-info microservice hooks | The common-config hook caused the app-info microservice hooks to fail with an application-start error.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
39061499 |
Common-Config: Alter Command not allowed | Common Config did not allow the required ALTER command.
Doc Impact: There is no documentation impact. |
2 |
26.1.200 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.200.4.2.13.4 Common Configuration Service Resolved Bugs
Release 26.1.201
There are no resolved bugs in this release.
Release 26.1.200
Table 4-23 Common Configuration Service 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
|
38817454 |
IGW is unable to read the CCA secret when deployed with TLS v1.3 | Ingress Gateway was unable to read the CCA secret when deployed with TLS v1.3.
Doc Impact: There is no documentation impact. |
2 |
25.2.106 |
|
38913633 |
Common-Config: GCC parameters should not be mandatory | The Global Common Config parameters were set as mandatory.
Doc Impact: There is no documentation impact. |
3 |
26.1.200 |
|
38099982 |
Common config rejection error deatil should be proper - not like this Unexpected character ('\"' (code 34)): was expecting comma to separate Object entries, Location :[Source: REDACTED (`StreamRead |
Common Config rejection error details were incorrect because object entries were not separated by commas. Doc Impact: There is no documentation impact. |
4 |
25.1.200 |
Note:
Resolved bugs from 25.1.200 have been forward ported to Release 26.1.200.4.2.13.5 NRF-Client Resolved Bugs
Release 26.1.204
There are no resolved bugs in this release.
Release 26.1.203
Table 4-24 NRF-Client 26.1.203 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39663505 | NRF Client emitted a stale ocLogId before updating the logging context |
During NRF Discovery request processing, NRF Client emitted early request logs with an incorrect structured Doc Impact: There is no documentation impact. |
3 | 26.1.201 |
| 39316933 | NRF Client NF Management failed while parsing text/plain responses from Config Server during scale down |
During Config Server downtime, NRF Client NF Management received a text or plain response generated by the Envoy proxy instead of a JSON ProblemDetails response. NRF Client attempted to parse the response as ProblemDetails, resulting in a Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39253442 | NRF Client NF Management INFO logs did not include ocLogId |
NRF Client NF Management did not include the Doc Impact: There is no documentation impact. |
4 | 25.2.204 |
Release 26.1.202
There are no resolved bugs in this release.
Release 26.1.201
Table 4-25 NRF-Client 26.1.201 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39350697 | NRF Cache Auditor did not purge entries according to the configured percentage |
The NRF Cache Auditor did not purge local cache entries according to the configured cleanup percentage because local cache cleanup was limited to the Discovery service. This resulted in stale cache entries remaining on the Management pod and prevented cache cleanup from operating according to the configured purge percentage. Doc Impact: There is no documentation impact. |
2 | 25.2.200 |
| 39324695 | NF Profile List API did not work as expected in CNC Console | The NF Profile List API did not function correctly in CNC Console. Saving populated configuration data failed with HTTP 400 Bad Request and the validation error CCS-E107, although the same configuration could be updated successfully by using the REST API. This prevented configuration updates through CNC Console while the REST API continued to function correctly.
Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39529740 | NRF Client route-list notification to the Egress Gateway microservice was rejected as HTTP/1.x, preventing OAuth token retrieval |
NRF Client sent route-list notifications to the Egress Gateway microservice by using HTTP/1.x, which the Egress Gateway microservice rejected. As a result, the dynamic NRF route list was not updated. This prevented successful OAuth token retrieval because the Egress Gateway microservice did not maintain the required dynamic NRF route information. Doc Impact: There is no documentation impact. |
2 | 26.1.200 |
| 39251921 | NRF Client NF Management did not handle non-JSON responses from Istio during AppInfo Service scale down |
During AppInfo Service scale down, NRF Client NF Management received a plain-text Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39120111 | NullPointerException occurred during heartbeat update processing when ipEndPoints was null |
NRF Client generated a Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39232970 | NRF NF Management generated repeated WARN logs for missing subscription renewal cache data |
NRF NF Management generated the WARN log message Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39324939 | NRF Route List API did not work as expected in CNC Console |
The NRF Route List API did not function correctly in CNC Console. Saving populated configuration data failed with Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
| 39443980 | Heartbeats were delayed to NRF, causing SEPP to enter the suspended state | In a non-ASM deployment, NRF Client Management did not support HTTP/2 communication with the Egress Gateway microservice after OAuth was disabled. The Egress Gateway microservice continued performing periodic health checks, but NRF Client Management communicated by using HTTP/1.1 instead of HTTP/2. This delayed heartbeat processing and caused SEPP to enter the suspended state.
Doc Impact: There is no documentation impact. |
3 | 25.1.200 |
| 39309686 | ServiceDiscoveryException was observed in NRF pods after upgrade to 26.1.200 |
After an in-service upgrade from release 25.2.201 to 26.1.200, NRF pods continuously reported Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
Release 26.1.200
Table 4-26 NRF-Client 26.1.200 Resolved Bugs
| Bug Number | Title | Description | Severity | Found in Release |
|---|---|---|---|---|
| 39196633 | PCF NRF-Client sent an invalid subscription request URI, causing subscription failure in NRF |
NRF-Client sent an invalid URI in subscription requests initiated by PCF, causing NRF to reject the subscription request. NRF-Client also returned an incorrect error response structure when NRF notification delivery failed. This resulted in subscription failures and inconsistent error responses being returned for NRF notification failures. Doc Impact: There is no documentation impact. |
3 | 25.2.202 |
| 39175786 | NRF-Client Management Auditor Job emitted continuous WARN logs during normal cache audit |
During normal NRF Client Management service operation, the scheduled auditor job generated Doc Impact: There is no documentation impact. |
3 | 26.1.200 |
Note:
Resolved bugs from 25.2.100 have been forward ported to Release 26.1.200.4.3 Known Bug List
The following tables list the known bugs and associated Customer Impact statements.
4.3.2 BSF Known Bugs
Release 26.1.201
Table 4-27 BSF 26.1.201 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 39207585 | Mate site is not listed in the migration completion query | The Custom Query list used to check migration completion status for the v2 table may not list the mate site. | During PCF binding table migration in a BSF GR deployment, the PCF Binding migration completion query displays only the local site ID. The migration completion percentage for the mate site cannot be viewed from either site. Binding processing, migration, service traffic, and data integrity are not affected. The impact is limited to operational visibility.
Workaround: There is no workaround. |
3 | 25.2.200 |
4.3.4 cnDBTier Known Bugs
Release 26.1.202
Table 4-28 cnDBTier 26.1.202 Known Bugs
| Bug number | Title | Description | Customer impact | Severity | Found in release |
|---|---|---|---|---|---|
| 38166191 | PCF after enabling Exception Table Cleanup-up Feature Failed the traffic | cnDBTier data pods can restart during a PCF maintenance procedure after enabling the Exception Table Cleanup-up feature.
Workaround: Recover PCF and perform GRR to restore service with nologging-table data. |
PCF loses nologging tables when cnDBTier data pods restart and interrupt maintenance. | 2 | 23.4.4 |
| 38267894 | PCF Ingress and Egress Traffic. Failed post Rollback operation | cnDBTier data pods can restart during a PCF maintenance procedure after a rollback.
Workaround: Recover PCF and perform GRR to restore service with nologging-table data. |
PCF loses nologging tables when cnDBTier data pods restart and interrupt maintenance. | 2 | 23.4.4 |
| 38426377 | Prod Mgm pods getting crashed | One of the two mgmd pods can disconnect from the other cnDBTier pods.
Workaround: During the next maintenance window, restart both |
No impact to application database queries or georeplication because the second mgmd pod remains functional.
|
2 | 23.4.6 |
| 38414831 | ndbmtd-1 in CrashLoopBackOff (AM-PCF rcklca63cpcf-y-or-am-w1-003) | A data pod can continuously restart.
Workaround: During the next maintenance window, scale down all data pods and then scale them up. |
No impact to application database queries or georeplication because the mate data pod remains functional. | 2 | 23.4.6 |
| 39212897 | Replication stopped with Last_Error: Error 'Can't find record in 'NDB$BLOB_923_11'' on query. Default database: ''. Query: 'COMMIT' | Replication can stop with an NDB$BLOB record-not-found error.
Workaround: Take a backup from the healthy site and perform GRR on the failed site. |
Replication breaks. | 2 | 25.2.102 |
| 39671872 | CNDB - We are observing GRR stucked in MONITOR_PARALLEL_BACKUP_RESTORE for long time | GRR can remain in the MONITOR_PARALLEL_BACKUP_RESTORE state for an extended time.
Workaround: Restart the |
GRR remains stuck. | 2 | 26.1.200 |
| 38979458 | SEPP-PERF-CNDB: ndbmysqld-3 stuck after rollback from 25.2.200-rc.7 to 25.2.101-GA | Following rollback, ndbmysqld pods can enter CrashLoopBackOff while creating the local Data Dictionary from the NDB Data Dictionary.
Workaround: Perform a full GRR. |
The affected ndbmysqld pod can remain unavailable.
|
2 | 25.2.200 |
| 39789596 | Graceful binlog purge may not occur while the secondary replication channel is active, which can result in higher-than-expected binlog PVC usage. This is not service-impacting, as the Layer 2 purge maintains PVC usage within safe limits. The issue does not affect operation when the primary replication channel is active. | Layer 1 binlog purge may not occur while the secondary replication channel is active.
Workaround: Do nothing; PVC usage remains below 90%. Alternatively, switch over to the primary channel, or set global.api.binlogForcePurgeSizeCheckPercentage to 70 and perform a Helm upgrade. |
PVC usage can be higher than expected, but Layer 2 purging activates at 85% and maintains usage below 90%; there is no service impact. | 2 | 25.1.201 |
| 39062625 | If the db-replication-svc PVC is deleted, or its contents are wiped while GRR is in progress, GRR can get stuck and does not transition to GRR_FAILED. | Deleting or wiping the db-replication-svc PVC during GRR can prevent the process from transitioning to GRR_FAILED.
Workaround: Mark the site as failed using the REST API, then retry GRR. |
GRR remains stuck. | 3 | 25.2.201 |
| 39646621 | hooks.sh --schema-upgrade prompt error "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ', 'PREFERRED_BACKUP_SITE', NULL, NULL) ON DUPLICATE KEY UPDATE " | The schema-upgrade script can report success even when SQL queries fail to run.
Workaround: Run the schema upgrade again. |
Schema upgrade can be marked successful despite failed SQL queries. | 3 | 26.1.200 |
| 39645167 | dbtrecover stuck in INITIATE_PARALLEL_BACKUP_TRANSFER. | dbtrecover can remain in INITIATE_PARALLEL_BACKUP_TRANSFER.
Workaround: Increase |
GRR remains stuck. | 3 | 26.1.200 |
| 39357497 | [Soltest-PI26-AB][GR_Testing]: Observing very high number of exception entries (pcf_binding) in site2 post cnDBTier rollback of site1 from 26.1.200-rc.1 to 25.2.201 also there is a mismatch in table records due to this | During rollback, replication epochs can be lost if the replication service starts late while ndbmysqld pods restart and old PVCs are deleted.
Workaround: Use |
Database inconsistency and a high number of exception entries can occur when an odd-indexed pod serves the active replication channel. | 3 | 26.1.200 |
| 39616688 | Replication break observed on deleting active mysqld pod after password encryption key is set as blank | Invalid or blank password-encryption keys can be accepted, which can lead to replication issues if the active MySQL pod is deleted.
Workaround: Provide a valid key and use |
Replication can break. | 3 | 26.1.200 |
| 39546278 | Data pods restart observed while running upgrade from 25.2.202 to 26.1.200-rc3 3site 1 channel | Data-pod restarts can occur during upgrade in a three-site, one-channel deployment.
Workaround: No workaround is required. |
No service impact. | 3 | 26.1.200 |
| 39765309 | A rare replication failure may occur during cnDBTier install, upgrade, or rollback activities performed within a maintenance window. The issue can arise when the db-replication-svc pod restarts at the same time as the ndbmysqld pods are undergoing a rolling restart, causing the replication service to start without loading the active and standby replication channel details into memory.If this condition occurs, subsequent replication switchover requests may fail. | During installation, upgrade, or rollback, simultaneous restart of db-replication-svc and rolling restart of ndbmysqld pods can leave replication-channel details absent from memory.
Workaround: Restart |
Replication switchover can fail. Confirm the issue by checking for the documented ReplicationSqlIp.getHostIp() null-value error in the pod logs.
|
3 | 26.1.201 |
| 39823749 | Cross-site replication may go down during DB Tier rollback when ndbmysqld-1 is serving the ACTIVE replication channel. Both SQL pods and their PVCs may be replaced before replication moves to the surviving SQL pod, causing the required replication epoch history to be lost.
|
During rollback, both SQL pods and PVCs can be replaced before replication moves to the surviving SQL pod, losing replication epoch history.
Workaround: Before rollback, ensure |
Cross-site replication and disaster recovery can be temporarily degraded; the local database and application traffic remain available. | 3 | 26.2.200 |
| 39782184 | During long traffic runs, db-infra-monitor-svc in NDB data-node pods may accumulate blocked Prometheus scrape threads when PVC or filesystem metric operations are slow. Memory usage increases until the container reaches its limit and restarts with exit code 137 (OOMKilled).
|
Slow PVC or filesystem metric operations can block Prometheus scrape threads and cause db-infra-monitor-svc to restart with exit code 137.
Workaround: Restart |
The infrastructure-monitor container restarts and metrics may be temporarily unavailable. NDB processing and application traffic continue. | 3 | 26.1.200 |
Release 26.1.201
Table 4-29 cnDBTier 26.1.201 Known Bugs
| Bug number | Title | Description | Customer impact | Severity | Found in release |
|---|---|---|---|---|---|
| 38166191 | Traffic failed after enabling Exception Table Cleanup-up feature | After enabling the feature, traffic failed during a PCF maintenance procedure because cnDBTier data pods restarted. |
PCF loses nologging tables when cnDBTier data pods restart and interrupt maintenance. Workaround: Recover PCF and perform GRR to restore service with nologging-table data. |
2 | 23.4.4 |
| 38267894 | Ingress and egress traffic failed after rollback operation | Traffic failed after rollback when cnDBTier data pods restarted during PCF maintenance. |
PCF loses nologging tables when cnDBTier data pods restart and interrupt maintenance. Workaround: Recover PCF and perform GRR to restore service with nologging-table data. |
2 | 23.4.4 |
| 38426377 | Management pods getting crashed | One of two mgmd pods disconnected; the other remained functional. |
No impact to application database queries or georeplication. Workaround: During the next maintenance window, restart both mgmd pods simultaneously. |
2 | 23.4.6 |
| 38414831 | ndbmtd-1 in CrashLoopBackOff | The ndbmtd-1 data pod repeatedly restarted; its mate pod remained available. |
No impact to application database queries or georeplication. Workaround: During the next maintenance window, scale down all data pods, then scale them up. |
2 | 23.4.6 |
| 39212897 | Replication stopped with missing NDB$BLOB record error | Replication stopped with a missing NDB$BLOB_923_11 record error.
|
Replication breaks when this error occurs. Workaround: Back up the good site and perform GRR on the failed site. |
2 | 25.2.102 |
| 39671872 | GRR stuck in MONITOR_PARALLEL_BACKUP_RESTORE | Geo Replication Recovery (GRR) remained in MONITOR_PARALLEL_BACKUP_RESTORE for an extended period.
|
GRR does not progress beyond this state. Workaround: Restart the |
2 | 26.1.200 |
| 39062625 | GRR stuck when db-replication-svc PVC is deleted or wiped | Deleting or wiping the PVC during GRR can leave GRR stuck instead of transitioning to GRR_FAILED.
|
GRR remains stuck rather than entering the expected failed state. Workaround: Mark the site as failed with the REST API, then retry GRR. |
3 | 25.2.201 |
| 39646621 | hooks.sh --schema-upgrade SQL syntax error | Schema upgrade displays a SQL syntax error. |
The upgrade may be reported as successful even when SQL queries fail. Workaround: Run the schema upgrade again. |
3 | 26.1.200 |
| 39645167 | dbtrecover stuck in INITIATE_PARALLEL_BACKUP_TRANSFER | dbtrecover gets stuck in INITIATE_PARALLEL_BACKUP_TRANSFER.
|
GRR does not progress beyond this state.
Workaround: Increase |
3 | 26.1.200 |
| 39357497 | Exception entries and table mismatch after cnDBTier rollback | cnDBTier rollback can result in high exception-entry counts and mismatched table records. |
Lost or skipped epoch transactions can cause database inconsistency when odd-indexed Workaround: Use |
3 | 26.1.200 |
| 39616688 | Replication break after deleting active mysqld pod with blank password encryption key | Deleting the active mysqld pod after setting a blank encryption key can break replication.
|
Invalid or blank password encryption keys can be accepted and cause issues. Workaround: Provide a valid key and use |
3 | 26.1.200 |
| 39765309 | Replication switchover can fail during maintenance activities | Restarting db-replication-svc during installation, upgrade, or rollback can prevent replication-channel details from loading.
|
Replication may fail and switchover may be unavailable. Check logs for Workaround: Restart |
3 | 26.1.201 |
4.3.5 CNE Known Bugs
Release 26.1.200
Table 4-30 CNE Release 26.1.200 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 36740199 | BareMetal CNE installation on X9-2 servers fail | When installing OL9-based Bare Metal CNE on X9-2 servers, PXE booting may occur unexpectedly. Booting with the OL9.x ISO that uses the UEK kernel can hang with: Device does not have valid ME interface.
|
This issue prevents successful installation of Bare Metal CNE on X9-2 servers. Workaround: Use the hardware-agnostic CNE installation procedure for X9-2-based Bare Metal CNE deployments. |
2 | 23.4.0 |
| 38106756 | CNE self-upgrade failed due to Multus race condition | Intermittently, a CNE upgrade with CNLB enabled fails because Multus cannot remove required resources from a node. |
This issue may occur during OCCNE upgrades with CNLB enabled. Workaround: Run the following command on all nodes: |
3 | 25.1.200 |
| 39722102 | BareMetal deployment logs are incomplete on bastion | Expected complete pipeline and deployment logs should be saved on the bastion. However, pipeline_bastion_*.log stops midway at initial_setup.
|
Installation logs are not fully visible on the bastion host. Workaround: Run the pipeline command with |
4 | 26.1.200 |
4.3.6 NSSF Known Bugs
Release 26.1.202
Table 4-31 NSSF 26.1.202 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 38284044 | oc_oauth_request_failed_cert_expiry Metric not getting pegged . | When OAuth authentication rejects an expired certificate, the request is rejected correctly but the related oc_oauth_request_failed_cert_expiry metric is not recorded.
|
Service behavior remains correct; observability for this rejection is incomplete. Workaround: There is no workaround. |
3 | 25.2.200 |
| 39805938 | NSSf ATS 26.1.201: Flag is missing to check OSO connection | The NSSF ATS framework has no flag to bypass OSO connection checks when OSO is not deployed. |
ATS execution takes longer in a non-OSO deployment. NSSF functionality is unaffected. Workaround: There is no workaround. |
3 | 26.1.201 |
| 39880200 | NSSF 25.2.201: Correct IGW Overload Control documentation for samplingPeriod and mandatory action | Documentation for Ingress Gateway Overload Control and Discard Policy Mapping describes some mandatory parameters as optional. |
Configuration can be based on incorrect parameter requirements. Workaround: There is no workaround. |
3 | 25.2.201 |
| 39893101 | NSSF 25.2.200 has alternate service disabled however its PDB is still there | The alternate-route Pod Disruption Budget remains although its corresponding pod is disabled. |
Service operation is unaffected because alternate route is recommended to remain enabled. Workaround: There is no workaround. |
3 | 25.2.200 |
| 39913694 | NSSF registration to NRF failing, when watchMySql is true and DBTier is up and running. | NRF registration fails when watchMySql is true and the previous database status URL is used.
|
NSSF cannot register with NRF in this configuration. Workaround: Use the database status URL in the NSSF 26.1.202 default configuration file. |
3 | 26.1.201 |
| 39702525 | NSSF ns-selection request through ingress gateway is failing with `Internal Server Error` due to `java.util.concurrent.CancellationException` | An NsSelection request through Ingress Gateway can intermittently return HTTP 500 with java.util.concurrent.CancellationException.
|
The reported traffic loss was below 0.01% and normal service operation remains unaffected. Workaround: Increase the client HTTP timeout as needed so it remains greater than the Ingress Gateway timeout. |
4 | 26.1.200 |
Release 26.1.201
Table 4-32 NSSF 26.1.201 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 37623199 | Invalid Accept header can trigger an AMF notification and incorrect response for nssai-auth PUT and DELETE
|
NSSF does not consistently reject nssai-auth PUT and DELETE requests with an invalid Accept header. A PUT request can return HTTP 500 after storing data, and a DELETE request can return HTTP 204 without deleting data, which can trigger an AMF notification.
|
There is no impact on traffic or service behavior. Traffic processing and success rate remain unaffected. Workaround: There is no workaround. |
3 | 25.1.100 |
| 37784755 | Log-level change option is unavailable for ocnssf-ocpm-config and ocnssf-performance pods through CNCC and REST
|
The perf-info microservice does not provide an option to change the log level dynamically. Its log level is fixed at ERROR.
|
There is no impact on traffic or call processing because the Workaround: There is no workaround. |
3 | 25.1.100 |
| 38819395 | NSSF nsselection pod restarts with exit code 143 during 80K TPS NS-Selection traffic when DB connectivity is cyclically interrupted | When DB connectivity to all pods is disrupted for 10 minutes and restored for 50 minutes, cyclically for more than 12 hours, one NS-Selection pod can restart with exit code 143. |
Impact is low because the scenario is rare and environment-specific. Traffic resumes normally after the restart. During the restart window, only in-flight messages are affected, and only one of eight NS-Selection pods is impacted. Workaround: There is no workaround. |
3 | 25.2.200 |
| 38621015 | NSSF accepts overload threshold configuration when abatementValue is greater than onsetValue |
NSSF accepts an overloadLevelThreshold configuration when abatementValue is greater than onsetValue. The configuration is saved, but the overload threshold is not applied, so overload behavior acts as if overload is disabled.
|
Misconfigured overload parameters can cause sustained overload control without proper recovery and lead to service degradation. Workaround: Configure overload-control parameters as documented in the Network Slice Selection Function REST Specification Guide. Set the abatement value lower than the onset value. |
3 | 25.2.200 |
| 39660915 | NSSF regression in 25.2.200: candidateAmfList format changed
|
The candidateAmfList format changes from an array of NfInstanceId strings to an array of objects containing nfInstanceId.
|
AMF can report a decode error because it expects a string value in Workaround: There is no workaround. |
3 | 25.2.200 |
| 39604971 | AutoConfig-Off: Duplicate element in ns-availability PATCH add request returns an error
|
In AutoConfig-Off mode, an ns-availability PATCH add request returns HTTP 400 INVALID_INPUT_DATA when it adds a duplicate TAI. The expected behavior is to accept the duplicate add request and retain one logical record.
|
Impact is low. There is no data loss or availability loss because the rejection indicates the original TAI already exists in NSSF. Workaround: Avoid sending duplicate TAI entries in PATCH add requests. If a duplicate request is rejected, send a PUT request with the complete intended |
3 | 26.1.200 |
| 39568412 | Network Slice Selection Function User Guide counter mismatches | The User Guide contains metric and KPI documentation mismatches, including incorrectly formatted dimensions, inconsistent metric names or case, undocumented KPI metrics, and missing dimension information. |
Using the guide for metric or KPI development, Prometheus dashboard creation, or query validation can result in incorrect metric names or labels, invalid queries, or confusion while validating NSSF counters. Workaround: Validate against Prometheus-visible metric names and labels until using a corrected version of the User Guide. |
3 | 25.1.200 |
| 38973933 | HTTP 500 and 404 responses in NS-Availability call flow after site restore | In a three-site GR deployment handling about 27K TPS per site, sequential failover and recovery of Sites 3 and 2 can result in isolated NS-Availability errors after traffic is redistributed. |
Impact is minimal. Approximately 0.003% message loss is observed while two sites are down and traffic is handled by one active site. No prolonged outage occurs, and full replication and traffic distribution are restored after recovery. Workaround: There is no workaround. |
4 | 25.2.200 |
| 39490419 | NRF Client does not send unsubscribe messages for existing subscriptions when NSSF is uninstalled | When NSSF is uninstalled or deregistered from NRF in a GR deployment, NRF Client can fail to send unsubscribe requests for existing NRF subscriptions. Stale subscription records can remain in NfSubscriptions after the NSSF profile is removed.
|
Obsolete NSSF subscription state can remain in NRF, causing confusing database state, stale notification targets, repeated cleanup attempts, or extra triage during failover or uninstall validation. There is no loss of service. Workaround: Before uninstalling or scaling down, confirm that the NSSF |
4 | 26.1.200 |
| 38628736 | NSSF pods enter Error state before termination when all deployments are scaled down to zero | During scale-down of all NSSF deployments to zero replicas, several pods briefly enter the Error state before terminating. |
There is no impact on live traffic because this occurs during intentional scale-down to zero. The issue is limited to pod lifecycle behavior during shutdown. Workaround: There is no workaround. |
4 | 25.2.200 |
4.3.8 OSO Known Bugs
Release 26.1.200
Table 4-33 OSO Known Bugs 26.1.200
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 38661250 | IPv6 connections are not established between prom-svr and NF pods when OSO is deployed in IPv6-preferred mode. | Prometheus targets, pods, endpoints, and services use IPv4 addresses even when the cluster is dual-stack. |
Targets use IPv4 even in a dual-stack cluster. There is no functional impact because OSO supports PreferredDualStack mode, which permits IPv4 fallback. Workaround: There is no workaround. |
3 | 25.2.200 |
| 39143113 | Communication between OSO-PROM, OSO-ALM, and OSO-APM uses IPv4 addresses instead of IPv6. | In a dual-stack cluster, communication from ALM to the APM service uses IPv4 addresses. |
OSO component communication uses IPv4 even in a dual-stack cluster. There is no functional impact because OSO supports PreferredDualStack mode, which permits IPv4 fallback. Workaround: There is no workaround. |
3 | 25.2.200 |
4.3.9 Policy Known Bugs
Release 26.1.201
Table 4-34 Policy 26.1.201 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 38618989 | Exported General Settings show incorrect values | Exported General Settings can show parameters that do not match the CM UI. Enhanced Logging and Truncate Stack Trace fields can be duplicated or appear in the wrong configuration section. |
Settings can show parameters in sections that do not match the CM UI. Enhanced Logging and Truncate Stack Trace fields can be duplicated or appear in the wrong configuration section. Running services, configuration processing, and CM UI behavior are not affected. Exported Swagger data can differ from the UI and confuse API or export consumers. Workaround: Use |
3 |
25.2.200 |
| 39148659 | UE UDR PATCH retries select an incorrect NF instance | After a UE Policy Association Update, the UDR connector can blocklist or select the wrong UDR NF instance when retrying UE UDR PATCH requests. Retries can target an inappropriate instance before another available instance is selected. |
UE Policy PATCH updates can fail intermittently during UDR failover and failover latency can increase when alternate routing is used Workaround: A configuration-only workaround does not fully resolve this issue. Remove failed or unhealthy UDR instances from NRF or profile availability quickly. Ensure |
3 |
25.2.200 |
| 39433380 | AppInfo probes database replication status when the check is disabled | AppInfo can probe the database replication status URI and log replication probe failures even when replicationStatusCheck is set to false, if the configured replication URI cannot be resolved.
|
AppInfo can report an incorrect replication status to the NF. Workaround: Configure replicationUri correctly. |
3 |
26.1.200 |
| 39523948 | PCF does not correctly reject invalid AppSessionContextReqData values | PCF can accept Policy Authorization requests with invalid AppSessionContextReqData values or reject them with an incorrect status, cause, title, or missing invalidParams. Malformed fields can return 201 Created, 500, or ERROR_REQUEST_PARAMETERS instead of the expected 400 response.
|
Valid Policy Authorization requests are not affected. Malformed N5 Policy Authorization requests can be accepted or receive an incorrect 3GPP error response. Workaround: No workaround is required for valid traffic. Correct malformed requests at the AF before sending them to PCF. |
3 |
26.1.200 |
| 39533145 | PCF does not correctly reject invalid TypeMediaComponent values | PCF can accept or incorrectly reject Policy Authorization requests with invalid optional TypeMediaComponent values. Malformed media-component fields can return 201 Created or a 400 response with an incorrect cause or title.
|
Valid Policy Authorization requests are not affected. Malformed N5 Policy Authorization requests can be accepted or receive an incorrect 3GPP error response. Workaround: There is no workaround required for valid traffic. Correct malformed requests at the AF before sending them to PCF. |
3 |
26.1.200 |
| 39540953 | PCF does not correctly reject invalid TypeMediaSubComponent values | PCF can accept or incorrectly reject Policy Authorization requests with invalid optional TypeMediaSubComponent values. Malformed media-subcomponent fields can return 201 Created or a 400 response with an incorrect cause or title.
|
PCF does not return the expected Workaround: There is no workaround required for valid traffic. Correct malformed requests at the AF before sending them to PCF. |
3 |
26.1.200 |
| 39629291 | PCRF does not remove Event-Trigger AVPs from CCA-I responses | PCRF can continue to send Event-Trigger AVPs in CCA-I responses when the configuration is intended to remove all event triggers, if the incoming request indicates ADC support. |
The system does not support Workaround: There is no workaround. |
3 |
25.2.200 |
| 39729474 | SM does not propagate message-priority headers to dependent Binding requests | SM can omit the 3gpp-sbi-message-priority and oc-message-priority headers on RX-dependent Binding requests during PA Create and PA Delete flows.
|
SM does not propagate the received priority as an internal Workaround: If you need different priority handling for dependent-context registration or deregistration traffic, configure the Binding Service advanced settings for those operation priorities. |
3 |
26.1.200 |
| 39756967 | Usage Monitoring enhanced logs show an unreadable error cause and escaped URI | When Usage Monitoring receives a 400 response from PDS, enhanced logs can show an unreadable byte-array value for the error cause and a percent-encoded URI.
|
Logs provide less diagnostic value and make troubleshooting more difficult. No call failures or stale data are reported. Workaround: There is no workaround. |
3 |
26.1.200 |
| 39759124 | Data Limit Sorting Profile REST API accepts rules without an index | The Data Limit Sorting Profile REST API can accept and store a sorting rule without an index. When the required profile name is missing, the API returns HTTP 400 with an empty response.
|
The API can store incomplete sorting-rule configurations and does not provide sufficient validation information. Workaround: There is no workaround. |
3 |
26.1.200 |
| 39763764 | Export Policy dialog is delayed | The Export Policy dialog can take approximately 15–16 seconds to appear after you select the action in CNC Console or the local GUI. The UI provides no immediate processing indication. |
The delay provides no immediate visual confirmation that the action is received or processing. Workaround: There is no workaround. |
3 |
26.1.200 |
| 39776023 | UPSI create REST API rejects an existing URSP rule name | The UPSI create REST API can return HTTP 400 when you provide an existing URSP rule by name. Exported configurations reference URSP rules by name instead of by internal UUID.
|
UPSI REST configuration creation fails. Workaround: Use the URSP UUID when you create UPSI through the REST API. |
3 |
26.1.200 |
| 39779771 | Policy Library export returns HTTP 404 when no data exists | The Policy Library export endpoint returns HTTP 404 when no Policy Library data exists, although the documented operation specifies HTTP 200.
|
Policy Library REST export returns HTTP Workaround: Policy Library is deprecated and no longer in use. It will be removed in a future release. |
3 |
26.1.200 |
| 39795244 | SM service assigns an incorrect priority to cleanup requests | When a cleanup request has no oc-message-priority header, SM service sets priority 18 instead of the configured default priority 20 and propagates it to downstream services.
|
If downstream congestion control is enabled, downstream services accept or reject cleanup requests based on priority Workaround: Set the required value by using the key: value: 20 |
3 |
26.1.200 |
| 39797452 | SM Update Notify message priority is inconsistent | Internally generated SMF Update Notify requests do not retain the original 3gpp-sbi-message-priority header because they are created as new internal reauthorization requests.
|
Message Profile attribute filters that rely on the priority header do not match these requests, so the configured priority is not evaluated from the intended Message Profile rule. Workaround: Create a message-profile rule for: {}Interface: Npcf_SMPolicyControl Message type: Update Notify Configure the rule with Request Priority Override = IfNotPresent. This lets the profile apply its configured priority when the internally triggered SMF Update Notify does not carry the original 3gpp-sbi-message-priority header. For normal requests that do contain the header, the incoming 3GPP priority remains available and is not overridden by this fallback rule. |
3 |
26.1.200 |
4.3.10 NRF Known Bugs
Release 26.1.201
Table 4-35 NRF 26.1.201 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 39690026 | NRF request combinations changed from 5xx responses to other HTTP status codes | NRF returns different HTTP status codes for some request combinations than in previous releases. Certain request combinations return HTTP 503 Service Unavailable instead of HTTP 500 Internal Server Error while continuing to report an error condition.
|
The response code changes from Workaround: There is no workaround. |
3 | 25.2.201 |
| 39690007 | NRF request combinations changed from 4xx responses to other HTTP status codes | NRF returns different HTTP status codes for some request combinations than in previous releases. Certain request combinations return a different HTTP 4xx response code while continuing to report the same client error condition.
|
The HTTP response code for certain Workaround: There is no workaround. |
3 | 25.2.201 |
| 39588761 | NRF does not consistently preserve the existing Via header chain when forwarding subscription update and delete requests | NRF does not consistently preserve the existing Via header chain when forwarding subscription update and delete requests. Instead of appending the local Via entry, NRF drops the existing Via header chain before forwarding the request.
|
Dropping earlier Workaround: There is no workaround. |
3 | 26.1.200 |
| 39273759 | NRF Nnrf_NFManagement_NfUpdate accepts add /nfStatus for an existing attribute and emits an inconsistent NF_PROFILE_CHANGED partial notification
|
NRF accepts Nnrf_NFManagement_NfUpdate request that uses the add operation for an existing nfStatus attribute and updates the NF status. The generated NF_PROFILE_CHANGED partial notification contains op=ADD with the original value instead of the expected op=REPLACE.
|
NRF updates the Workaround: There is no workaround. |
3 | 26.1.200 |
4.3.11 SCP Known Bugs
Release 26.1.202
There are no new known bugs in this release. The known bugs from 26.1.201 have been forward ported to release 26.1.202.
Release 26.1.201
Table 4-36 SCP 26.1.201 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 38952387 | Case mismatch in Localities for INTER SCP cases (USWEST and USWest) results in incorrect population of worker inter-SCP routing maps | A case mismatch in localities for inter-SCP scenarios, such as USWEST and USWest, results in incorrect population of worker inter-SCP routing maps.
|
Inter-SCP routing is affected only when localities are misconfigured. Workaround: Correct locality information in the NF profile. |
3 | 25.2.200 |
| 38782868 | Routing continues to a deleted NF type when profile deregistration fails | Routing continues to a deleted NF type when profile deregistration fails. |
Routing can continue using stale rules when an NF type is deleted but its profile deregistration fails. This has very low functional impact because of the limited use case. Workaround: Do not delete the NF type configuration while NF profiles are still registered. |
3 | 25.2.200 |
| 38008367 | Overlapping regex validation missing for apiSpecificResourceUri in routing configuration API
|
The routing configuration REST API allows overlapping regex patterns in the apiSpecificResourceUri field, leading to ambiguous routing when a request matches multiple patterns.
|
Conflicting routing-configuration selection can occur when regex patterns overlap in Workaround: Do not configure overlapping regex patterns. |
3 | 25.1.100 |
| 37995299 | SCP cannot delete foreign SCP routing details after deregistration | When a foreign SCP profile is unregistered, SCP fails to remove associated routing details for certain profiles. |
There is no impact because SCP redeployment is required to update Workaround: There is no workaround. |
3 | 25.1.200 |
| 37970295 | Worker pod restart observed due to coherence timeout when a single cache pod is used | When increasing the number of worker pods from 1 to 23 with only one cache pod, worker pods restart because of a coherence timeout. |
A deployment with a single cache pod can result in worker-pod restarts under high rate-limit traffic. Workaround: There is no workaround. |
3 | 25.1.200 |
| 37949191 | ocscp_metric_nf_lci_tx_total increments when no LCI headers are received from peer NFs
|
The ocscp_metric_nf_lci_tx_total metric increments even when no LCI headers are received from peer NFs.
|
There is a minor observability impact. Workaround: There is no workaround. |
3 | 25.1.200 |
| 37622431 | Audit failures observed during overload when traffic exceeds pod limits by 50% | When traffic operates at maximum rated capacity and exceeds pod limits by 50%, audit failures occur while SCP is in overload condition. |
In overload conditions, the SCP Worker pod-protection mechanism discards some internally generated NRF audit requests. Workaround: Audits are periodic and eventually succeed after the overload condition subsides. |
3 | 25.1.100 |
| 37575057 | Duplicate routing when producer responses contain a Location header in 3xx cases | SCP performs duplicate routing when the producer NF responds with a Location header in 3xx cases. |
SCP sends requests to the producer NF again when the producer NF in the redirect URL and alternate routing rules are the same. Workaround: There is no workaround. |
3 | 25.1.100 |
| 36757321 | 429 errors due to pod-overload discards during upgrade and rollback | During an upgrade from SCP 24.1.0 to 24.2.0, five worker nodes consumed more than six vCPUs while handling 60K MPS, resulting in 429 errors. |
Some traffic loss can occur during an upgrade under bursty traffic conditions because of the SCP Worker pod-protection mechanism. Workaround: Perform upgrades during periods of low traffic to avoid overloading pods. |
3 | 24.2.0 |
| 39740833 | Intermittent duplicate on-demand audits during static-to-DNS NRF migration | During static-to-DNS NRF migration, SCP can queue two on-demand audits when DNS SRV targets for the same NRF set are created sequentially and the preferred NRF changes during evaluation. |
On-demand audit requests can be duplicated in some cases, but there is no functional impact. Workaround: There is no workaround. |
3 | 26.1.201 |
| 39732803 | interPlmnFqdnValidationEnabled deploys as false although documentation states the default is true
|
SCP deploys interPlmnFqdnValidationEnabled as false, while documentation identifies the default value as true.
|
For fresh installations, the default value should be true. If it is not set, SCP alternate routing does not restrict routing to inter-PLMN FQDNs. Workaround: Use the System Options REST API to explicitly set |
3 | 25.1.205 |
| 39715345 | Notification-rejection metric is not updated under queue-full conditions with multiple updates for the same NF | SCP does not increment ocscp_notification_nf_profile_rejected_total when a full notification queue receives multiple updates for the same NF.
|
If a persistently high rate of NF profile notifications is sent to SCP over an extended period, the metric is not incremented. This can affect observability by preventing accurate metric reporting. Workaround: Monitor queue-full metrics and notification logs to identify and investigate these conditions. |
3 | 26.1.200 |
| 39690644 | Model-D discovery cache is not updated by local refresh after producer NF status-change notification in inter-SCP routing | For inter-SCP routing, SCP does not update the Model-D discovery cache through local refresh after receiving a producer NF status-change notification. |
There is no functional impact on Model-D-based routing when the Model-D cache is enabled. NF status changes are applied during Workaround: There is no workaround. |
3 | 26.1.200 |
| 39678455 | Outlier Detection PUT API does not apply defaults for omitted optional fields before persistence or SSE | The Outlier Detection PUT API does not apply default values for omitted optional attributes before persisting and applying the configuration. |
If optional attributes are omitted from the REST API request payload, default values are not applied and the Outlier Detection configuration can behave incorrectly. Workaround: After configuring an Outlier Detection rule, verify that all relevant attributes are present. Explicitly include all attributes defined in the payload, including optional ones. |
3 | 26.1.200 |
| 39672610 | Runtime-update ATS lacks a case where an error profile is configured with 3xx error codes | ATS does not cover the runtime-update case in which an error profile specifies 3xx error codes. |
There is no functional impact. Manual testing confirmed that the functionality works as expected. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39672032 | SCP NRF Bootstrap Info Migration performs audit for non-applicable NRF sets in migrated mode | In migrated mode, SCP can initiate an on-demand audit for NRF sets that do not apply when the performAudit attribute changes from false to true.
|
There is no functional impact. Changing Workaround: There is no workaround. |
3 | 25.2.104 |
| 39671406 | scp51 retains Outlier Detection state from the previous scenario after profile deregistration
|
SCP can retain the previous Outlier Detection state for an inter-SCP destination after the foreign SCP NF profile is deregistered. |
In a rare condition, the prior Outlier Detection state is not cleared after the foreign SCP NF profile is deregistered. This issue could not be reproduced. Workaround: Ensure that either a successful response is received or no traffic is sent to this peer SCP destination during the interval configured in the Outlier Detection rule. |
3 | 26.1.200 |
| 39588774 | SCP does not return redirect response with alternate URI | In an inter-SCP routing scenario, SCP cannot reselect and route a request when a producer-side SCP returns a self-generated 307 redirect response with an alternate SCP URI. |
If the producer-side SCP returns a self-generated 307 Redirect response containing the redirect URL of another producer-side SCP, the consumer-side SCP cannot reselect the redirected SCP and route to it. Workaround: Do not return a 307 Redirect response containing a redirect URL in this scenario. |
3 | 26.1.200 |
| 39587422 | Inconsistent ocscp_peer_scp_fqdn values are reported in peer-SCP unhealthy metrics
|
The ocscp_peer_scp_fqdn dimension can report an IP address instead of an FQDN in peer-SCP unhealthy metrics.
|
There is no functional impact. The dimension can display an IP address regardless of whether host preference is configured to use an FQDN or IP address. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39525762 | Error cause and detail need an update during deletion of a 3GPP-defined discovery query parameter | Documentation specifies an incorrect error cause and detail for deletion of a 3GPP-defined discovery query parameter. |
There is no functional impact. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39523758 | CNLB annotation examples are missing from SCP documentation | SCP documentation does not include CNLB annotation examples. |
There is no functional impact. Workaround: There is no workaround. |
3 | 25.1.204 |
| 39505209 | NF profiles learned through a deleted NRF Set ID are not deregistered | When an NRF Set ID is removed from the NRF bootstrap configuration, SCP does not automatically deregister NF profiles learned through that NRF Set. |
When an NRF set is configured and the network topology is learned through it, removing the NRF set from the NRF bootstrap configuration does not automatically remove the related learned topology. Workaround: Remove the NRF set only after all NFs registered through it have been deregistered. Alternatively, use a script, such as one using |
3 | 26.1.200 |
| 39491413 | Unable to configure Consumer Info Configuration | SCP returns an insufficiently specific REST API configuration error when it cannot configure Consumer Info Configuration. |
There is no functional impact. The REST API error message needs to provide a more specific reason for the error. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39417928 | scpinstanceid and operation="NF_LIST_RETRIEVAL" are missing from the ocscp_audit_tx_req_total user-guide entry
|
The SCP user guide does not document scpinstanceid and operation="NF_LIST_RETRIEVAL" for ocscp_audit_tx_req_total.
|
There is no functional impact. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39348771 | Range of priority, capacity, and load for the self SCP profile is missing from the User Guide and REST Guide | The SCP User Guide and REST API Guides do not document the ranges for priority, capacity, and load in the self SCP profile. |
There is no functional impact. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39332752 | SCP inquiry about recommended tolerationSeconds values for NoExecute toleration
|
The documented behavior for tolerationSeconds does not state the recommended value for a NoExecute toleration when an SCP pod is evicted and rescheduled.
|
There is no functional impact. This scenario evaluates the time required to evict and reschedule an SCP pod after a Kubernetes node becomes unreachable or enters the Workaround: Set |
3 | 25.1.200 |
| 39332708 | Error cause and detail are incorrect for an invalid baseEjectionTime value in Outlier Detection configuration
|
SCP returns an incorrect error cause and detail for an invalid baseEjectionTime value in Outlier Detection configuration.
|
There is no functional impact. The level of detail in error messages for mandatory or optional attributes with out-of-range values is under review. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39304820 | SCP profile configuration update and deletion need correction in the CNCC section of the User Guide | The CNC Console section of the SCP User Guide does not describe SCP profile configuration updates and deletion. |
There is no functional impact. Workaround: There is no workaround. |
3 | 26.1.200 |
| 39270613 | Canary Release feature details | Canary configuration changes can continue to use Model-D cached data, and single-digit capacity values can produce weights that do not achieve the intended traffic distribution. |
Changes to the canary attribute or canary traffic percentage might not take effect for Model-D-based traffic because routing continues to use cached data. Single-digit capacity values can also produce weights too low to achieve the intended traffic-distribution ratio. Workaround: Disable the Model-D cache before applying canary configuration changes through the REST API, then re-enable it afterward. Configure capacity values in the canary NF profile as multiples of 100. |
3 | 24.3.0 |
| 39189619 | SCP intermittently returns 504 TARGET_NOT_REACHABLE for AMF notifications after successful AMF profile retrieval | SCP intermittently returns 504 TARGET_NOT_REACHABLE for an AMF notification after successfully retrieving the AMF profile from NRF. |
There is no functional impact because multiple NF profiles cannot have the same FQDN within the network. Workaround: There is no workaround. |
3 | 25.2.200 |
| 38098107 | SCP does not consider Version and Trailer fields from Jetty response | SCP does not consider version and trailer fields from Jetty responses. |
There is no impact because these fields are not currently used. Workaround: There is no workaround. |
4 | 25.1.200 |
| 38079614 | SCP All Services: Replace java.util.date and org.joda.time with java.time |
SCP services rely on java.util.date and org.joda.time for date and time handling, which are not thread-safe and lack modern functionality.
|
There is no impact because this is a minor code enhancement. Workaround: There is no workaround. |
4 | 25.1.200 |
| 39715249 | SCP logs “Exception occurred. Failed to get ServiceEntry” while deregistering an NF profile | SCP logs the exception when it deregisters an NF profile that has no services. |
There is no functional impact. The log message is misleading because no service entry is expected for an NF profile without services. Workaround: There is no workaround. The log message can be safely ignored. |
4 | 26.1.200 |
| 39710459 | Low-severity code issues identified during the 26.1.200 release code audit | Low-severity code issues identified during the SCP 26.1.200 code audit remain open. |
There is no functional impact. Multiple issues identified during the code-review audit are addressed. Workaround: There is no workaround. |
4 | 26.1.200 |
| 39664694 | “Page not found” exceptions occur in the configuration pod during a Model-D duration run | During a Model-D duration run, the configuration pod logs “Page not found” exceptions for non-SBI requests that use an incorrect resource URI. |
There is no functional impact. Some non-SBI requests, such as metrics-scraping requests, use an incorrect resource URI and cause this error. Workaround: Correct the resource path, or safely ignore the error if it is expected. |
4 | 26.1.200 |
| 39458013 | SMF ingress NF type reconfiguration does not update fallback ingress_SMF-NA bucket
|
Reconfiguring the SMF ingress NF type does not update the fallback ingress_SMF-NA bucket, leaving a stale rate-limit value.
|
There is no functional impact. Workaround: There is no workaround. |
4 | 26.1.200 |
| 39418028 | Pod name is reported twice in ocscp_worker_health_check_rx_req_total |
The ocscp_worker_health_check_rx_req_total metric reports the pod-name dimension twice.
|
There is no functional impact. The pod-name dimension appears twice only for this metric. Workaround: There is no workaround. |
4 | 26.1.200 |
| 39148745 | Global error handler maps validation and deserialization errors to INVALID_VALUE instead of 3GPP-compliant causes | The global error handler maps validation and deserialization errors to INVALID_VALUE rather than applicable 3GPP causes such as MANDATORY_IE_INCORRECT and OPTIONAL_IE_INCORRECT.
|
There is no functional impact. The traffic feed-related configuration APIs must be aligned with 3GPP specifications. Workaround: There is no workaround. |
4 | 26.1.200 |
4.3.12 SEPP Known Bugs
Release 26.1.201
There are no known bugs in this release.
Release 26.1.200
Table 4-37 SEPP 26.1.200 Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 39138384 | SEPP does not remove x-next-hop-authority header for requests toward Remote PLMN
|
SEPP forwards x-next-hop-authority and other x-headers to the partner. Removing these headers globally breaks N32-C routing. The issue requires header handling for N32-F and N32-C traffic.
|
There is a security breach risk during RH SEPP to E/// SEPP integration. Workaround: There is no workaround. |
3 | 25.1.201 |
| 39131855 | Conformance HTTP/2: Request with nonconforming pseudo-headers is not considered malformed | SEPP handles malformed HTTP/2 pseudo-header requests incorrectly. A request missing :scheme returns 404, and a request missing :method gives no response instead of a stream reset or protocol error.
|
Standards conformance affects interoperability and testing. Workaround: There is no workaround. |
3 | 25.1.201 |
| 39091133 | Intermittent failures observed in multiple Create and Delete RS and RSS call flows - v25.2.200 | In 25.2.200-rc.1, CreateRSS, CreateRS, DeleteRSS, and DeleteRS flows intermittently return 500, 403, or 404 instead of the expected 201 or 204 responses. This indicates inconsistent behavior in RS and RSS operations. |
RS and RSS lifecycle call flows have internal stability and reliability impact. Workaround: There is no workaround. |
3 | 25.2.200 |
| 39332895 | SEPP: Inquiry about recommended tolerationSeconds values for NoExecute toleration
|
SEPP requires guidance for recommended NoExecute toleration values so that pods can be evacuated after node shutdowns or reboots.
|
Customers need guidance for SEPP pod evacuation behavior after abrupt shutdowns or reboots. Workaround: No final workaround is documented; internal portfolio/SA review is pending. |
3 | 25.1.200 |
| 39559658 | Default error code profile mentioned in “Pod Protection by Rate Limiting” does not exist | The default error-code profile referenced under Pod Protection by Rate Limiting does not match the profile available in Error Code Profiles. |
Default error-code profile references are inconsistent between Pod Protection by Rate Limiting and Error Code Profiles. Workaround: No explicit workaround is documented in Jira. |
3 | 26.1.200 |
SEPP 26.1.200 Gateway Known Bugs
Table 4-38 SEPP 26.1.200 Gateway Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 38810446 | [SEPP-APIGW] Missing ignoremaxresponsertime & sbiRoutingWeightBasedEnabled under metadata in EGW CNCC screen | The Egress Gateway CNC Console screen does not show ignoremaxresponsertime and sbiRoutingWeightBasedEnabled under metadata. Because the SBITimer feature behavior depends on these metadata values, users cannot include them when they configure or edit routes through CNC Console. |
SBITimer and NRF route automation functionality over Egress Gateway are impacted, and the feature may not work correctly. Workaround: Configure through Helm. |
3 | 26.1.200 |
| 38810483 | [SEPP-APIGW] No support for header based predicate under EGW Routesconfiguration in CNCC screen | The Egress Gateway Routes configuration screen in CNC Console does not support header-based predicates. |
Users are impacted when they configure routes through REST with a header name as the filter. Workaround: Configure through Helm. |
3 | 26.1.200 |
| 38769835 | [SEPP-IGW] SBITimer Feature: Misleading logger in the IGW, when request contains 3gpp-Sbi-Origination-Timestamp and gpp-Sbi-Sender-Timestamp but no 3gpp-Sbi-Max-Rsp-Time | IGW prints a misleading log message when the request includes 3gpp-Sbi-Origination-Timestamp and 3gpp-Sbi-Sender-Timestamp but does not include 3gpp-Sbi-Max-Rsp-Time. The log suggests that sender or origin headers are missing instead of indicating that 3gpp-Sbi-Max-Rsp-Time is missing. |
Users may be misled when they review the logs. Workaround: There is no workaround. |
3 | 26.1.200 |
| 38771574 | [SEPP-IGW] SBITimer Feature Enabled- sbiTimerTimezone related Issues | The sbiTimerTimezone behavior has multiple issues. When the gateway is configured as ANY and the request contains PDT timezone, processing uses GMT instead of PDT. When the gateway is configured as ANY and the request has no timezone, a Late Arrival Error occurs. When the gateway is configured as GMT and the request contains PDT, the expected behavior is unclear. |
Not provided. Workaround: Not provided. |
3 | 26.1.200 |
4.3.13 Common Services Known Bugs
4.3.13.1 Alternate Route Service Known Bugs
Release 26.1.2xx
There are no known bugs in this release.
4.3.13.2 Egress Gateway Known Bugs
Release 26.1.2xx
Table 4-39 Egress Gateway 26.1.2xx Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 39123626 | DestinationHost dimension is missing from the outgoing IP type metric | The DestinationHost dimension is absent from the occnp_oc_egressgateway_outgoing_ip_type metric in Gateway Services 25.2.109. |
Observability in error scenarios and system performance are affected. Workaround: There is no workaround. |
3 | 25.2.109 |
| 38304085 | EGW does not validate 3gpp-sbi-message-priority parameters during POP25 and overload | Egress Gateway does not validate the 3gpp-sbi-message-priority header parameters in pod-protection overload scenarios. |
Invalid values can cause the feature to malfunction. Workaround: The consumer NF should send valid header values. |
3 | 25.2.100 |
| 39088228 | Host dimension in Egress Gateway response metrics still has cardinality explosion | The Host dimension remains part of the response-metric cardinality in the Egress Gateway 25.2.109 test release. |
Observability in error scenarios and system performance are affected. Workaround: There is no workaround. |
3 | 25.2.109 |
| 39049678 | Improve logging for NPE during Jetty bean creation when TLS is disabled | An unexpected NullPointerException error log can be emitted during REST API mode installation while Jetty web-client beans are created with TLS disabled. |
Installation observability may be affected by the unexpected error log. Workaround: There is no workaround. |
3 | 25.2.108 |
| 38810483 | No support for header-based predicates in EGW route configuration on the CNCC screen | The CNCC screen does not support configuring a header-based predicate for Egress Gateway routes. |
NRF route configuration can be affected because it relies on a header-based predicate at PLMN Egress Gateway, potentially affecting inter-PLMN NRF requests through SEPP. Workaround: There is no workaround. |
3 | 25.2.106 |
| 38294514 | NPE during OAuth access request when nrfClientQueryEnabled is enabled | A NullPointerException occurs during an OAuth access request when nrfClientQueryEnabled is enabled. |
The OAuth token request does not reach NRF, causing additional calls to fail. Workaround: There is no workaround. |
3 | 25.2.100 |
| 38279961 | oauthDeltaExpiryTime functionality does not work during traffic | Egress Gateway can request an NRF OAuth token before the configured oauthDeltaExpiryTime has expired. |
No traffic impact because token processing occurs before timer expiry. Workaround: There is no workaround. |
3 | 25.2.100 |
| 38778598 | Outgoing IP type metric remains IPv4 after DNS changes to IPv6 | In an IPv6-preferred dual-stack deployment, the outgoing IP type metric can remain set to IPv4 after DNS removes the IPv4 address. |
The metric can report incorrect active-connection information after DNS address-family changes. Workaround: There is no workaround. |
3 | 25.2.104 |
| 38810446 | Required metadata parameters are missing from the EGW CNCC screen | The CNCC screen does not expose ignoremaxresponsertime and sbiRoutingWeightBasedEnabled under Egress Gateway route metadata. |
Producer-NF load sharing is unavailable by default, and SBITimer cannot be used for PLMN Egress Gateway unless IgnoreMaxRspTimeHeader is explicitly configured. Workaround: Configure the routes using REST APIs instead of using the CNC Console. |
3 | 25.2.106 |
| 38351114 | EGW returns 500 instead of 503 when a configured static NRF is unavailable | When a static NRF is unavailable, Egress Gateway returns an HTTP 500 internal-server error instead of the expected HTTP 503 service-unavailable response. |
The response does not clearly identify the static NRF availability failure. Workaround: There is no workaround. |
4 | 25.2.100 |
| 39016184 | TLS connection and disconnection logs are missing in Egress Gateway | Egress Gateway does not produce messages confirming successful TLS connection establishment or disconnection. Corresponding messages remain available in Ingress Gateway. |
Not provided. Workaround: There is no workaround. |
4 | 26.1.200 |
4.3.13.3 Ingress Gateway Known Bugs
Release 26.1.2xx
Table 4-40 Ingress Gateway 26.1.2xx Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 38405814 | Post-rollback validation fails at alternate-route logging-level validation | After rollback, SM validation reports a mismatch in the Alternate Route logging-level values. |
No production impact. The log level is not changed from WARN to DEBUG. Workaround: There is no workaround. |
3 | 25.2.100 |
| 39706472 | Failure counts are updated for services regardless of whether ocPolicyMapping is enabled | Failure counts can be maintained for route-configured services absent from ocPolicyMapping. PerfInfo and APIGW use only OC-policy-mapped services for overload calculation and action. |
No functional impact to NRF. Workaround: There is no workaround. |
3 | 26.1.204 |
| 38310333 | IGW request and response latency metrics are not updated for TLS 401 rejection | In a TLS setup, Ingress Gateway request and response latency metrics are not updated when Ingress Gateway rejects a request with HTTP 401. |
Observability is affected because the latency metric is not updated. Workaround: There is no workaround. |
3 | 25.2.100 |
| 35526243 | Operational state change should be disallowed when required pre-configurations are absent | Ingress Gateway allows an operational-state change even when controlledshutdownerrormapping and errorcodeprofiles are not configured. A pre-check should prevent the state change when these required configurations are missing. |
Gateway Services may process a request that should have been rejected. Workaround: There is no workaround. |
3 | 23.2.0 |
| 38902043 | Configurable error-code profiles incorrectly include “Name or service not known” in error_reason | Ingress Gateway appends “Name or service not known” to the configured error_reason value for all error-code profiles. The error reason should contain only the configured value. |
No traffic impact. Workaround: There is no workaround. |
4 | 26.1.200 |
| 38807819 | Incorrect OAuth error response when producer PLMN ID validation fails | Ingress Gateway can reject an OAuth token with a 401 response even when the token contains the correct producer PLMN ID. The returned title also incorrectly refers to an NRF instance-ID mismatch. |
A valid request can be rejected with an incorrect OAuth validation response. Workaround: There is no workaround. |
3 | 25.2.200 |
| 38293511 | IGW does not validate 3gpp-sbi-message-priority parameters during POP25 and overload | Ingress Gateway does not validate the 3gpp-sbi-message-priority header parameters in pod-protection overload scenarios. |
Invalid values can cause the feature to malfunction. Workaround: The consumer NF should send valid header values. |
3 | 25.2.100 |
| 39706361 | Overload failure count is not aligned for all IGW-generated 4xx and 5xx error codes | Ingress Gateway-generated validation failures occur before the request reaches the backend and are therefore not counted for backend overload control. Configured failure counting applies to matching backend responses and supported Ingress Gateway-to-backend exceptions. |
No functional impact to NRF or backend overload handling. Workaround: There is no workaround. |
3 | 26.1.204 |
| 38769987 | SBITimer time-zone mismatch gauge does not reset | The oc_ingressgateway_sbitimer_timezone_mismatch metric remains at 1 after it is pegged and does not reset to 0. |
Observability is affected because the metric does not reset. Workaround: There is no workaround. |
3 | 25.2.105 |
| 39527997 | Intermittent NullPointerException in IGW when a route has an empty CustomReqHeaderEntryFilter headers list | When an Ingress Gateway route is configured through REST with an empty CustomReqHeaderEntryFilter headersList, an intermittent NullPointerException can occur while processing traffic, resulting in an HTTP 500 response. |
Not provided. Workaround: There is no workaround. |
3 | 26.2.200 |
| 38771574 | SBITimer time-zone handling issues | When the configured time zone is ANY or GMT, certain timestamp and missing-time-zone combinations can be interpreted incorrectly and return an incorrect late-arrival error. |
Requests can receive an incorrect late-arrival error instead of the expected format or time-zone handling. Workaround: Ensure that the configuration and timestamp header use compatible time zones. |
3 | 25.2.105 |
4.3.13.4 Common Configuration Service Known Bugs
Release 26.1.2xx
Table 4-41 Common Configuration Service 26.1.2xx Known Bugs
| Bug Number | Title | Description | Customer Impact | Severity | Found in Release |
|---|---|---|---|---|---|
| 39063477 | Missing upper-limit validation allows oversized global configuration objects | Global Configuration APIs do not enforce maximum item counts. Oversized configurations can be persisted and may fail later or affect runtime processing. |
Potential performance, memory, database, or processing impact when oversized configurations are loaded and evaluated. Workaround: There is no workaround. |
3 | 26.1.200 |