Upstream OLM + API sync 12-14#229
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: timflannagan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
It looks like we didn't pull in the OLM commits in the right order last time so there were some missing test/e2e commit(s) that newer commits reference which failed the e2e-aws-olm check. Updated to include all (:crossed_fingers:) of those missing commits. |
|
/retest |
|
/lgtm |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
10 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
1 similar comment
|
/retest |
c701ed9 to
fa7d0c6
Compare
…test failures (#2442) * Introduce mechanism for gathering test artifacts during individual test failures Update the testing e2e suite and add a mechanism for gathering test artifacts during individual test failures. Currently, container logs are gathered when deprovisioning upstream kind clusters, yet we lack fine-grain ability to diagnose test failures further. Note: test failures use the `CurrentGinkgoTestDescription.Failed` field to determine failures. Testing artifacts are only gathered when the base $ARTIFACTS_DIR environment variable has been specified. Add a collect-ci-artifacts.sh bash script, responsible for gathering OLM native resources for an individual testing namespace. This bash script will be called when tearing down the generated testing namespace for relevant e2e packages. Currently, the artifact gathering process is restricted to only a single namespace - longer term, it might be possible to instead migrate towards collecting resources that all share a similar label selector, and utilizing that label selector to handle multi-namespace testing scenarios. Introduce another helper function in test/e2e/util_test.go that's responsible for gathering test artifacts (i.e. calling this newly introduced script) when the test case had failed, and in either case, delete the namespace. Signed-off-by: timflannagan <timflannagan@gmail.com> * test/e2e: Refactor the bundle e2e tests to avoid using global test namespace Signed-off-by: timflannagan <timflannagan@gmail.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: 4cc28bb74ff6721eb41491ec57c55cc47bc1ad84
Update the testing e2e packages and ensure that the $KUBECONFIG
environment variable is correctly set before running the bash script
responsible for collecting CI artifacts.
This should fix the following error message that was popping up in
individual CI runs:
```
collecting logs in the ./artifacts/ artifacts directory
../test/e2e/collect-ci-artifacts.sh: line 7: KUBECONFIG: parameter null or not set
failed to collect namespace artifacts: exit status 1
```
Update the kind provisioner to avoid prematurely removing the temporary
directory that contains the constructed (and ephemeral) kubeconfig file
and track that metadata in the TestContext structure. In the case that
field is unset for that object, fall back to the os.Getenv("KUBECONFIG")
value.
Signed-off-by: timflannagan <timflannagan@gmail.com>
Upstream-repository: operator-lifecycle-manager
Upstream-commit: 6dc902654d4f2089da9da56cc6b1d574be995d20
Signed-off-by: Daniel Sover <dsover@redhat.com> Co-authored-by: Daniel Sover <dsover@redhat.com> Upstream-repository: operator-lifecycle-manager Upstream-commit: d36949bb3b7353a43d8e8fc02033e0f09b7252bb
…parser (openshift#203) * feat(constraints): add compound constraints and olm.constraint value parser Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com> * renaming and add yaml tags Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com> Upstream-repository: api Upstream-commit: 40cb9fd4036ae1a58d84d29d4d14a47649b5f7f4
Upstream-repository: api Upstream-commit: 7f43803893b09e6160fbaffdb2e32e0c269005ff
|
/retest |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/test e2e-aws-olm |
Welp hopefully that's a transient error /retest |
|
/retest-required |
|
We may need to pivot to non-AWS tomorrow if infra flakes continue. /retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required |
|
looks like it's still failing to bring up an aws cluster /retest |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest |
|
/retest-required |
|
/retest |
|
Looks like the OLMConfig controller isn't playing well with downstream as of now. #232 just passed all test that's a clone of this PR minus the OLMConfig commit. lgtm-ing that PR so that the rest of the commits can go in, and then we can dig into the OLMConfig commit. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
6 similar comments
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
No description provided.