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
Bug 1898745: set progressing false on imagestream events as well if no active streams #338
Bug 1898745: set progressing false on imagestream events as well if no active streams #338
Conversation
had a couple of unrelated sig-storage and sig-network flakes |
@@ -379,5 +379,5 @@ func (h *Handler) processImportStatus(is *imagev1.ImageStream, cfg *v1.Config) ( | |||
} | |||
} | |||
|
|||
return cfg, nonMatchDetail, err | |||
return cfg, err |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
forgot to clean this now unused return field when BUILD-125 merged
e2e-aws
|
ocp image-eco more env and lower level in the stack hoopla ... more of these sample operator pod logs and installed imagestreams were fine |
596c671
to
7026e73
Compare
/retest |
/test e2e-aws-operator |
2e435a6
to
d99a921
Compare
/test e2e-aws-upgrade |
samples operator upgrade looks good in the last 2 e2e-aws-upgrade runs ... other operators had issues /test e2e-aws-upgrade |
samples still good on upgrade /test e2e-aws-upgrade |
samples still good in the failing e2e-aws-upgrade test |
673c854
to
bf58580
Compare
do not just depend on configmap events (many of which are deletes so no relist) more proactive version update, move off migration condition to configmap/sample inspection
bf58580
to
1ae50ef
Compare
/assign @coreydaley |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few nits, but overall seems to be resolving the issue.
pkg/stub/config.go
Outdated
@@ -221,6 +221,10 @@ func (h *Handler) buildFileMaps(cfg *v1.Config, forceRebuild bool) error { | |||
cm = &corev1.ConfigMap{} | |||
cm.Name = util.IST2ImageMap | |||
cm.Namespace = v1.OperatorNamespace | |||
if cm.Annotations == nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a nit, but you could move this one and the one inside of the if err == nil
block right under the cm, err := h.configmapclientwrapper.Get(util.IST2ImageMap)
to de-duplicate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but the Get
will return a nil for cm
though, right? ... at least I believe that is what I observed
that said, I don't need the nil check when I'm constructing the cm from scratch here ... so I will at least get rid of that
for key, value := range h.imagestreatagToImage { | ||
cm.Data[key] = value | ||
} | ||
_, err = h.configmapclientwrapper.Update(cm) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if _, err = h.configmapclientwrapper.Update(cm); err != nil {
return err
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
part of next push
pkg/stub/configmap.go
Outdated
return err | ||
} | ||
logrus.Printf("clearImageStreamTagError: stream %s already deleted so no worries on clearing tags", | ||
isName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: This shouldn't need to be on it's own line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
part of next push
updates pushed in separate commit @coreydaley ... PTAL |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: coreydaley, gabemontero The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
thanks @coreydaley I'll squash the separate commit I had for you comments and then reapply lgtm |
…rased in tag clean)
b304168
to
2c44279
Compare
New changes are detected. LGTM label has been removed. |
/hold given the e2e aws instability around openshift kube apiserver auth errors and the flakes we've seen over the last few days that is getting worked will unhold when that clears up to avoid repeated e2e launching |
/retest |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
/override ci/prow/okd-e2e-aws |
@gabemontero: Overrode contexts on behalf of gabemontero: ci/prow/okd-e2e-aws In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@gabemontero: All pull requests linked via external trackers have merged: Bugzilla bug 1898745 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Seen a few runs in CI today for various repos fail where the the samples operator did not get out of progressing == true state
When examining the pods logs, some odd message after our attempt to update progressing to false after getting a configmap delete event failed:
Even with returning an error, the delete event for the config map is not requeued.
We continue to get imagestream events.
This change (re)adds attempts to set progressing to false on imagestream events as well, when it is clear all the imagestream configmaps are gone. We may get a few conflicts when several imagestreams come in at the same time, but in the end that is no big deal.