ISV Operator Automation#24433
Conversation
|
/hold I think that before we merge this, we need to settle on openshift/enhancements#183 I do not believe that we want these tests to block a kubernetes update. |
|
@bandrade: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
|
@bandrade: PR needs rebase. DetailsInstructions 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. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
already migrated to openshift-tests repository, so closing this one. |
PR Created to automate
ISV Operatorstest, now it's coveringBasic Testingas explained on https://github.com/openshift/osde2e#operator-testing .Features implemented:
OperatorSourcesSingleNamespaceandOwnNamespace, a specific project is created with specificOperatorGroup. ForAllNamespacesit creates a subscription intoopenshift-operatorsnamespace. After creating the aSubscriptionand wait forClusterServiceVersionsucceed. And if so, it removes all Operator dependencies to unsure that Operator can be successfully uninstalled.Dry run execution:
@ecordell @njhale @kevinrizza. please have a review. Thanks! cc: @scolange @chengzhang1016 @emmajiafan @jianzhangbjz @tbuskey @shawn-hurley