-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operator reports that its installed multiple times #431
Comments
@Numblesix perhaps I'm missing something here. Can you explain what you mean by "Operator reports that it is installed multiple times"? From your |
It’s the last line of the output. Repeated 182 times over 14 hours. |
Hi sorry , yeah i find it quite weird that it shows this line hear:
Shouldnt that be displayed only once ? |
@innergy 👍 |
Thanks a lot :) Seemed strange to me but then its okay :) |
We plan to provide a fix for this by improving the message. |
As part of each reconcile loop Operator sets status as well as event message in accordance with the current state of Trident. There is a logic in place to not to update the CR status if it is same as old status (to avoid continuous CR updates). However, event messages are set each and every time thus resulting in the above behaviour and increment of the age counter. This behaviour is benign but can cause confusion, to avoid this confusion operator should only update the event message if the status is actually getting changed, else not. |
Hi, we experience almost the same problem as described here but we are running Openshift 4.4. But in our case new secrets are generated over and over again also. I guess on each restart it generates a new secret leading to this many: ➜ oc describe tprov -n trident trident
Name: trident
Namespace: trident
Labels: app.kubernetes.io/instance=**************.com-trident
Annotations: kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"trident.netapp.io/v1","kind":"TridentProvisioner","metadata":{"annotations":{},"labels":{"app.kubernetes.io/instance":"****...
API Version: trident.netapp.io/v1
Kind: TridentProvisioner
Metadata:
Creation Timestamp: 2020-05-14T10:14:44Z
Generation: 3
Resource Version: 102031764
Self Link: /apis/trident.netapp.io/v1/namespaces/trident/tridentprovisioners/trident
UID: 38c0978c-2c9b-4c49-a48f-d6bb947599ee
Spec:
Debug: true
Trident Image: netapp/trident:20.07
Status:
Current Installation Params:
IPv6: false
Autosupport Image: netapp/trident-autosupport:20.07.0
Autosupport Proxy:
Debug: true
Image Pull Secrets:
Image Registry: quay.io
k8sTimeout: 30
Kubelet Dir: /var/lib/kubelet
Log Format: text
Silence Autosupport: false
Trident Image: netapp/trident:20.07
Message: Trident installed
Status: Installed
Version: v20.07.0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Installed 2m49s (x1165 over 4d) trident-operator.netapp.io Trident installed
➜ oc get secrets -n trident | grep -c trident-csi-token
1168 |
This is fixed in the Trident 20.07.1 release. |
Hi, we are on trident 20.10.1 running on opsh4.6 and still get the following message every x minutes:
Is this expected/normal behaviour? |
Yes this is expected with you version of trident once you update to 20.07 this is fixed see the comment above |
Sorry, my bad, corrected the version in my previous post, we are on |
aah okay :) Seems we got the issue back im still on
|
@gnarl please reopen :) or Shall i open a new Issue and reference :) ? |
@Numblesix Thanks for the quick help 🎉 |
Please reopen this. I just upgraded from v20.04.0 to v20.10.1 and the operator still reports installs very frequently: Normal Installed 2m42s (x9 over 26m) trident-operator.netapp.io Trident installed |
Reopening this issue as Trident is still reporting installs more than once. |
This is fixed with commit a60b7a which is included in the Trident 21.01 release. |
Describe the bug
Operator reports installed in a "loop"
Environment
Provide accurate information about the environment to help us reproduce the issue.
To Reproduce
Steps to reproduce the behavior: Install via Operator as described in DOc
Expected behavior
Trident install should only be reported once
Additional context
The text was updated successfully, but these errors were encountered: