-
Notifications
You must be signed in to change notification settings - Fork 71
Bug 1991662: Catalog switcher #144
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
Conversation
* Implement catalog switching proposal - implements catalog switching proposal See https://github.com/operator-framework/enhancements/blob/master/enhancements/automatic-catalog-switching-annotations.md - picks up v0.10.3 - change sed command in copy_crds.sh to be posix compliant The command + in sed is non-portable. The posix compliant version of this command is {1,} This change allows this script to run on a mac too (which uses BSD sed) See https://riptutorial.com/sed/topic/9436/bsd-macos-sed-vs--gnu-sed-vs--the-posix-sed-specification Note: GVK was implemented but disabled due to security concerns. Future versions will address these concerns Signed-off-by: John Hunkins <[email protected]> * Address review comments from ecordell - reorganize imports - change logging common case to debug Signed-off-by: John Hunkins <[email protected]> * removed all watcher related code - this is the commit that should be reviewed later when it comes time to re-enable the GVK code Signed-off-by: John Hunkins <[email protected]> * update vendor to remove dynamic lister code Signed-off-by: John Hunkins <[email protected]> * fix incorrect names and improper error usage - fix names that don't match Golang convention - fix misspelled package name - return nil for sync function casting Signed-off-by: John Hunkins <[email protected]> * change code block organization and add mutex Signed-off-by: John Hunkins <[email protected]> * remove all traces of GVK template feature - clean up every instance of the GVK templating feature - add last minute change for RWMutex instead of Mutex - this is the second commit that should be reviewed later when it comes time to re-enable the GVK code Signed-off-by: John Hunkins <[email protected]> * return status update errors and adjust logging Signed-off-by: John Hunkins <[email protected]> * address review comments - update logging for clarity - clean up code blocks - refactor catalogsource helper functions: - remove mutex - remove two step get/update* in preference to update* even though this may result in more "the object has been modified" errors - rename helper functions to clarify usage - clarify the update helper function docs Signed-off-by: John Hunkins <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: 5f6fcd14f08a7e2a81b016fa83132ea68242f335
/retest |
This lgtm to me but we're waiting for either exception approval or this to land as a bug in z-stream. /hold |
/retest |
/hold cancel |
/retest |
3 similar comments
/retest |
/retest |
/retest |
Looks like we're not resilient to cache invalidation and need to add retry logic. I believe these failures are valid /hold so we don't keep wasting test resources |
Upstream-repository: operator-lifecycle-manager Upstream-commit: d55593954671505ef56bf09eb2e7900069fedecb
/hold cancel tests updated, should avoid that flake now |
In some cases, the discovery client can return a kube server version with the minor version field as a non uint value. To properly parse the value and get all version fields correctly, instead directly parse the GitVersion string for all values of the kube server version Upstream-repository: operator-lifecycle-manager Upstream-commit: 31350db3ec552fbabbedda33929538983155dea9
/test e2e-gcp |
/retest |
/test e2e-gcp |
/test e2e-upgrade |
/test e2e-gcp |
/retest |
1 similar comment
/retest |
/test e2e-upgrade |
2 similar comments
/test e2e-upgrade |
/test e2e-upgrade |
/test e2e-upgrade |
} | ||
|
||
// make the update if possible | ||
if _, err := client.OperatorsV1alpha1().CatalogSources(catsrc.GetNamespace()).Update(context.TODO(), catsrc, metav1.UpdateOptions{}); err != 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.
There is a bug in this function as this Update
call only updates the spec, not the status. Another call UpdateStatus
is needed here.
This is the downstream PR so this needs to be fixed upstream first.
/test e2e-upgrade |
3 similar comments
/test e2e-upgrade |
/test e2e-upgrade |
/test e2e-upgrade |
/bugzilla refresh |
@kevinrizza: An error was encountered searching for bug 1991662 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
could not unmarshal response body: invalid character '<' looking for beginning of value
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
@kevinrizza: An error was encountered searching for bug 1991662 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
could not unmarshal response body: invalid character '<' looking for beginning of value
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dinhxuanvu, kevinrizza 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 |
/retest |
1 similar comment
/retest |
@kevinrizza: An error was encountered searching for external tracker bugs for bug 1991662 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details. Full error message.
could not unmarshal response body: invalid character '<' looking for beginning of value
Please contact an administrator to resolve this issue, then request a bug refresh with 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. |
OLM is unable to properly handle the case where a bundle author explicitly adds a hardcoded reference to a service account with a name that matches the name of the service account defined by the deployment spec in the CSV. This commit adds a validation method to ensure that the name of the service account in a bundle does not match deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec Upstream-repository: api Upstream-commit: 0fe04f80e0102dc6973109a221a7babd6bee005e
OLM is unable to properly handle the case where a bundle author explicitly adds a hardcoded reference to a service account with a name that matches the name of the service account defined by the deployment spec in the CSV. This commit adds a validation method to ensure that the name of the service account in a bundle does not match deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec Upstream-repository: api Upstream-commit: 0fe04f80e0102dc6973109a221a7babd6bee005e
OLM is unable to properly handle the case where a bundle author explicitly adds a hardcoded reference to a service account with a name that matches the name of the service account defined by the deployment spec in the CSV. This commit adds a validation method to ensure that the name of the service account in a bundle does not match deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec Upstream-repository: api Upstream-commit: 0fe04f80e0102dc6973109a221a7babd6bee005e
OLM is unable to properly handle the case where a bundle author explicitly adds a hardcoded reference to a service account with a name that matches the name of the service account defined by the deployment spec in the CSV. This commit adds a validation method to ensure that the name of the service account in a bundle does not match deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec Upstream-repository: api Upstream-commit: 0fe04f80e0102dc6973109a221a7babd6bee005e
OLM is unable to properly handle the case where a bundle author explicitly adds a hardcoded reference to a service account with a name that matches the name of the service account defined by the deployment spec in the CSV. This commit adds a validation method to ensure that the name of the service account in a bundle does not match deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec Upstream-repository: api Upstream-commit: 0fe04f80e0102dc6973109a221a7babd6bee005e
OLM is unable to properly handle the case where a bundle author explicitly adds a hardcoded reference to a service account with a name that matches the name of the service account defined by the deployment spec in the CSV. This commit adds a validation method to ensure that the name of the service account in a bundle does not match deployment.Spec.Template.Spec.ServiceAccountName in the csv's spec Upstream-repository: api Upstream-commit: 0fe04f80e0102dc6973109a221a7babd6bee005e
See https://github.com/operator-framework/enhancements/blob/master/enhancements/automatic-catalog-switching-annotations.md
The command + in sed is non-portable. The posix compliant version of
this command is {1,}
This change allows this script to run on a mac too (which uses BSD sed)
See https://riptutorial.com/sed/topic/9436/bsd-macos-sed-vs--gnu-sed-vs--the-posix-sed-specification
Note: GVK was implemented but disabled due to security concerns.
Future versions will address these concerns
Signed-off-by: John Hunkins [email protected]
Signed-off-by: John Hunkins [email protected]
when it comes time to re-enable the GVK code
Signed-off-by: John Hunkins [email protected]
Signed-off-by: John Hunkins [email protected]
Signed-off-by: John Hunkins [email protected]
Signed-off-by: John Hunkins [email protected]
clean up every instance of the GVK templating feature
add last minute change for RWMutex instead of Mutex
this is the second commit that should be reviewed later
when it comes time to re-enable the GVK code
Signed-off-by: John Hunkins [email protected]
Signed-off-by: John Hunkins [email protected]
this may result in more "the object has been modified" errors
Signed-off-by: John Hunkins [email protected]
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 5f6fcd14f08a7e2a81b016fa83132ea68242f335