Bug 1825085

Summary:	Duplicate "Annotations" appears in etcd-operator pod
Product:	OpenShift Container Platform	Reporter:	ge liu <geliu>
Component:	Networking	Assignee:	Tomofumi Hayashi <tohayash>
Networking sub component:	multus	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	unspecified	CC:	bbennett, slaznick
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:27:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Standa Laznicka 2020-04-17 10:27:59 UTC

It appears like that because they are in fact there, and they are not doubled, one of the annotations is k8s.v1.cni.cncf.io/network-status and the other one k8s.v1.cni.cncf.io/networks-status. These seem to be added by multus, moving to sdn team.

Comment 2 Tomofumi Hayashi 2020-04-17 13:44:02 UTC

As Standa mentioned, this is not duplicated, 'k8s.v1.cni.cncf.io/networks-status' and 'k8s.v1.cni.cncf.io/network-status', networks v.s. network.

Let me introduce the history.
Previously multus-cni uses "k8s.v1.cni.cncf.io/networks-status" for network status as original implementation. Then Kubernetes Networking Plumbing working group creates the de-facto standard, multi-net-spec.
https://github.com/k8snetworkplumbingwg/multi-net-spec/tree/master/v1.1

In this spec, "k8s.v1.cni.cncf.io/network-status" is used, then we, multus team in upstream, decides to change it.
Currently we're in transitional phase, hence we need to keep old one and new one for compatibility. That is why we have two status.
We are going to remove old one after a few releases.

So if you don't mind it, I am going to change this bz to 'closed'.
Please let me know if you have question/comments.

Comment 3 ge liu 2020-04-21 03:50:51 UTC

I agree with Tomofumi's comment 2, thanks

Comment 5 errata-xmlrpc 2020-07-13 17:27:59 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409