From d94fd1f9464114d806dadef71a97006049b1be61 Mon Sep 17 00:00:00 2001 From: Gwynne Monahan Date: Thu, 13 Nov 2025 07:55:17 -0600 Subject: [PATCH] OSDOCS-17313 [NETOBSERV] Refactor rel notes 1.6.1-1.6.2 --- ...ator-release-notes-1-6-0-fixed-issues.adoc | 2 +- ...ity-operator-release-notes-1-6-1-cves.adoc | 12 +++++++++++ ...ator-release-notes-1-6-1-fixed-issues.adoc | 21 +++++++++++++++++++ ...vability-operator-release-notes-1-6-1.adoc | 11 ++++++++++ ...ity-operator-release-notes-1-6-2-cves.adoc | 11 ++++++++++ ...ator-release-notes-1-6-2-fixed-issues.adoc | 11 ++++++++++ ...ator-release-notes-1-6-2-known-issues.adoc | 11 ++++++++++ ...vability-operator-release-notes-1-6-2.adoc | 11 ++++++++++ ...bility-operator-release-notes-archive.adoc | 16 ++++++++++++-- 9 files changed, 103 insertions(+), 3 deletions(-) create mode 100644 modules/network-observability-operator-release-notes-1-6-1-cves.adoc create mode 100644 modules/network-observability-operator-release-notes-1-6-1-fixed-issues.adoc create mode 100644 modules/network-observability-operator-release-notes-1-6-1.adoc create mode 100644 modules/network-observability-operator-release-notes-1-6-2-cves.adoc create mode 100644 modules/network-observability-operator-release-notes-1-6-2-fixed-issues.adoc create mode 100644 modules/network-observability-operator-release-notes-1-6-2-known-issues.adoc create mode 100644 modules/network-observability-operator-release-notes-1-6-2.adoc diff --git a/modules/network-observability-operator-release-notes-1-6-0-fixed-issues.adoc b/modules/network-observability-operator-release-notes-1-6-0-fixed-issues.adoc index 9cbee179e67a..0ab81952c278 100644 --- a/modules/network-observability-operator-release-notes-1-6-0-fixed-issues.adoc +++ b/modules/network-observability-operator-release-notes-1-6-0-fixed-issues.adoc @@ -8,7 +8,7 @@ [role="_abstract"] You can review the following fixed issues for the Network Observability Operator 1.6.0. -* Previously, a dead link to the OpenShift containter platform documentation was displayed in the Operator Lifecycle Manager (OLM) form for the `FlowMetrics` API creation. Now the link has been updated to point to a valid page. (link:https://issues.redhat.com/browse/NETOBSERV-1607[*NETOBSERV-1607*]) +* Previously, a dead link to the {product-title} documentation was displayed in the Operator Lifecycle Manager (OLM) form for the `FlowMetrics` API creation. Now the link has been updated to point to a valid page. (link:https://issues.redhat.com/browse/NETOBSERV-1607[*NETOBSERV-1607*]) * Previously, the Network Observability Operator description in the Operator Hub displayed a broken link to the documentation. With this fix, this link is restored. (link:https://issues.redhat.com/browse/NETOBSERV-1544[*NETOBSERV-1544*]) * Previously, if Loki was disabled and the Loki `Mode` was set to `LokiStack`, or if Loki manual TLS configuration was configured, the Network Observability Operator still tried to read the Loki CA certificates. With this fix, when Loki is disabled, the Loki certificates are not read, even if there are settings in the Loki configuration. (link:https://issues.redhat.com/browse/NETOBSERV-1647[*NETOBSERV-1647*]) * Previously, the `oc` `must-gather` plugin for the Network Observability Operator was only working on the `amd64` architecture and failing on all others because the plugin was using `amd64` for the `oc` binary. Now, the Network Observability Operator `oc` `must-gather` plugin collects logs on any architecture platform. diff --git a/modules/network-observability-operator-release-notes-1-6-1-cves.adoc b/modules/network-observability-operator-release-notes-1-6-1-cves.adoc new file mode 100644 index 000000000000..431c0e701567 --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-1-cves.adoc @@ -0,0 +1,12 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-1-cves_{context}"] += Network Observability Operator release notes 1.6.1 CVEs + +[role="_abstract"] +You can review the CVEs for the Network Observability Operator 1.6.1 release. + +* link:https://access.redhat.com/errata/RHSA-2024:4237[RHSA-2024:4237] +* link:https://access.redhat.com/errata/RHSA-2024:4212[RHSA-2024:4212] \ No newline at end of file diff --git a/modules/network-observability-operator-release-notes-1-6-1-fixed-issues.adoc b/modules/network-observability-operator-release-notes-1-6-1-fixed-issues.adoc new file mode 100644 index 000000000000..87d6a12df867 --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-1-fixed-issues.adoc @@ -0,0 +1,21 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-1-fixed-issues_{context}"] += Network Observability Operator release notes 1.6.1 fixed issues + +[role="_abstract"] +You can review the fixed issues for the Network Observability Operator 1.6.1 release. + +* Previously, information about packet drops, such as the cause and TCP state, was only available in the Loki datastore and not in Prometheus. For that reason, the drop statistics in the OpenShift web console plugin *Overview* was only available with Loki. With this fix, information about packet drops is also added to metrics, so you can view drops statistics when Loki is disabled. (link:https://issues.redhat.com/browse/NETOBSERV-1649[*NETOBSERV-1649*]) +* When the eBPF agent `PacketDrop` feature was enabled, and sampling was configured to a value greater than `1`, reported dropped bytes and dropped packets ignored the sampling configuration. While this was done on purpose, so as not to miss any drops, a side effect was that the reported proportion of drops compared with non-drops became biased. For example, at a very high sampling rate, such as `1:1000`, it was likely that almost all the traffic appears to be dropped when observed from the console plugin. With this fix, the sampling configuration is honored with dropped bytes and packets. (link:https://issues.redhat.com/browse/NETOBSERV-1676[*NETOBSERV-1676*]) +* Previously, the SR-IOV secondary interface was not detected if the interface was created first and then the eBPF agent was deployed. It was only detected if the agent was deployed first and then the SR-IOV interface was created. With this fix, the SR-IOV secondary interface is detected no matter the sequence of the deployments. (link:https://issues.redhat.com/browse/NETOBSERV-1697[*NETOBSERV-1697*]) +* Previously, when Loki was disabled, the *Topology* view in the OpenShift web console displayed the *Cluster* and *Zone* aggregation options in the slider beside the network topology diagram, even when the related features were not enabled. With this fix, the slider now only displays options according to the enabled features. (link:https://issues.redhat.com/browse/NETOBSERV-1705[*NETOBSERV-1705*]) +* Previously, when Loki was disabled, and the OpenShift web console was first loading, an error would occur: `Request failed with status code 400 Loki is disabled`. With this fix, the errors no longer occur. (link:https://issues.redhat.com/browse/NETOBSERV-1706[*NETOBSERV-1706*]) +* Previously, in the *Topology* view of the OpenShift web console, when clicking on the *Step into* icon next to any graph node, the filters were not applied as required in order to set the focus to the selected graph node, resulting in showing a wide view of the *Topology* view in the OpenShift web console. With this fix, the filters are correctly set, effectively narrowing down the *Topology*. As part of this change, clicking the *Step into* icon on a *Node* now brings you to the *Resource* scope instead of the *Namespaces* scope. (link:https://issues.redhat.com/browse/NETOBSERV-1720[*NETOBSERV-1720*]) +* Previously, when Loki was disabled, in the *Topology* view of the OpenShift web console with the *Scope* set to *Owner*, clicking on the *Step into* icon next to any graph node would bring the *Scope* to *Resource*, which is not available without Loki, so an error message was shown. With this fix, the *Step into* icon is hidden in the *Owner* scope when Loki is disabled, so this scenario no longer occurs. (link:https://issues.redhat.com/browse/NETOBSERV-1721[*NETOBSERV-1721*]) +* Previously, when Loki was disabled, an error was displayed in the *Topology* view of the OpenShift web console when a group was set, but then the scope was changed so that the group becomes invalid. With this fix, the invalid group is removed, preventing the error. (link:https://issues.redhat.com/browse/NETOBSERV-1722[*NETOBSERV-1722*]) +* When creating a `FlowCollector` resource from the OpenShift web console *Form view*, as opposed to the *YAML view*, the following settings were incorrectly managed by the web console: `agent.ebpf.metrics.enable` and `processor.subnetLabels.openShiftAutoDetect`. These settings can only be disabled in the *YAML view*, not in the *Form view*. To avoid any confusion, these settings have been removed from the *Form view*. They are still accessible in the *YAML view*. (link:https://issues.redhat.com/browse/NETOBSERV-1731[*NETOBSERV-1731*]) +* Previously, the eBPF agent was unable to clean up traffic control flows installed before an ungraceful crash, for example a crash due to a SIGTERM signal. This led to the creation of multiple traffic control flow filters with the same name, since the older ones were not removed. With this fix, all previously installed traffic control flows are cleaned up when the agent starts, before installing new ones. (link:https://issues.redhat.com/browse/NETOBSERV-1732[*NETOBSERV-1732*]) +* Previously, when configuring custom subnet labels and keeping the OpenShift subnets auto-detection enabled, OpenShift subnets would take precedence over the custom ones, preventing the definition of custom labels for in cluster subnets. With this fix, custom defined subnets take precedence, allowing the definition of custom labels for in cluster subnets. (link:https://issues.redhat.com/browse/NETOBSERV-1734[*NETOBSERV-1734*]) \ No newline at end of file diff --git a/modules/network-observability-operator-release-notes-1-6-1.adoc b/modules/network-observability-operator-release-notes-1-6-1.adoc new file mode 100644 index 000000000000..cadadf90bb5f --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-1.adoc @@ -0,0 +1,11 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-1_{context}"] += Network Observability Operator release notes 1.6.1 advisory + +[role="_abstract"] +You can review the advisory for the Network Observability Operator 1.6.1 release. + +* link:https://access.redhat.com/errata/RHSA-2024:4785[2024:4785 Network Observability Operator 1.6.1] \ No newline at end of file diff --git a/modules/network-observability-operator-release-notes-1-6-2-cves.adoc b/modules/network-observability-operator-release-notes-1-6-2-cves.adoc new file mode 100644 index 000000000000..f3e47ec57eac --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-2-cves.adoc @@ -0,0 +1,11 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-2-cves_{context}"] += Network Observability Operator release notes 1.6.2 CVEs + +[role="_abstract"] +You can review the CVEs for the Network Observability Operator 1.6.2 release. + +* link:https://access.redhat.com/security/cve/CVE-2024-24791[CVE-2024-24791] \ No newline at end of file diff --git a/modules/network-observability-operator-release-notes-1-6-2-fixed-issues.adoc b/modules/network-observability-operator-release-notes-1-6-2-fixed-issues.adoc new file mode 100644 index 000000000000..a783e2df036e --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-2-fixed-issues.adoc @@ -0,0 +1,11 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-2-fixed-issues_{context}"] += Network Observability Operator release notes 1.6.2 fixed issues + +[role="_abstract"] +You can review the fixed issues for the Network Observability Operator 1.6.2 release. + +* When the secondary interface support was added, there was a need to iterate multiple times to register the per network namespace with the netlink to learn about interface notifications. At the same time, unsuccessful handlers caused a leaking file descriptor because with TCX hook, unlike TC, handlers needed to be explicitly removed when the interface went down. Now, there are no longer leaking file descriptors when creating and deleting pods. (link:https://issues.redhat.com/browse/NETOBSERV-1805[*NETOBSERV-1805*]) \ No newline at end of file diff --git a/modules/network-observability-operator-release-notes-1-6-2-known-issues.adoc b/modules/network-observability-operator-release-notes-1-6-2-known-issues.adoc new file mode 100644 index 000000000000..0235b02f7faa --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-2-known-issues.adoc @@ -0,0 +1,11 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-2-known-issues_{context}"] += Network Observability Operator release notes 1.6.2 known issues + +[role="_abstract"] +You can review the known issues for the Network Observability Operator 1.6.2 release. + +* There was a compatibility issue with console plugins that would have prevented network observability from being installed on future versions of an {product-title} cluster. By upgrading to 1.6.2, the compatibility issue is resolved and network observability can be installed as expected. (link:https://issues.redhat.com/browse/NETOBSERV-1737[*NETOBSERV-1737*]) \ No newline at end of file diff --git a/modules/network-observability-operator-release-notes-1-6-2.adoc b/modules/network-observability-operator-release-notes-1-6-2.adoc new file mode 100644 index 000000000000..7f4c9d29905f --- /dev/null +++ b/modules/network-observability-operator-release-notes-1-6-2.adoc @@ -0,0 +1,11 @@ +// Module included in the following assemblies: +// * network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc + +:_mod-docs-content-type: REFERENCE +[id="network-observability-operator-release-notes-1-6-2_{context}"] += Network Observability Operator release notes 1.6.2 advisory + +[role="_abstract"] +You can review the advisory for the Network Observability Operator 1.6.2 release. + +* link:https://access.redhat.com/errata/RHSA-2024:7074[2024:7074 Network Observability Operator 1.6.2] \ No newline at end of file diff --git a/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc b/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc index 7e469647c3da..0ebcf3b1eb64 100644 --- a/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc +++ b/observability/network_observability/release_notes_archive/network-observability-operator-release-notes-archive.adoc @@ -25,8 +25,20 @@ include::modules/network-observability-operator-release-notes-1-9-2-bug-fixes.ad //netobserv 1.8.1 //netobserv 1.8.0 //netobserv 1.7.0 -//netobserv 1.6.2 -//netobserv 1.6.1 + +include::modules/network-observability-operator-release-notes-1-6-2.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-6-2-cves.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-6-2-fixed-issues.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-6-2-known-issues.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-6-1.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-6-1-cves.adoc[leveloffset=+1] + +include::modules/network-observability-operator-release-notes-1-6-1-fixed-issues.adoc[leveloffset=+1] include::modules/network-observability-operator-release-notes-1-6-0.adoc[leveloffset=+1]