ROX-12848: Set Postgres flag to permanently enabled#4690
ROX-12848: Set Postgres flag to permanently enabled#4690connorgorman merged 9 commits intomasterfrom
Conversation
|
Images are ready for the commit at 6cdef58. To use with deploy scripts, first |
eeba4fb to
2f01ef9
Compare
|
/test openshift-newest-qa-e2e-tests openshift-penultimate-qa-e2e-tests openshift-oldest-qa-e2e-tests |
|
/test openshift-newest-qa-e2e-tests openshift-penultimate-qa-e2e-tests openshift-oldest-qa-e2e-tests |
822335d to
372fb20
Compare
| from ci_tests import NonGroovyE2e | ||
| from post_tests import PostClusterTest, FinalPost | ||
|
|
||
| # Postgres is on by default |
There was a problem hiding this comment.
Can you elaborate this comment why these tests are not executed with postgres enabled, instead exit early? I am lacking context to understand this.
There was a problem hiding this comment.
Sure, this is because these tests expect Postgres to be off and these are covered by the go version of these tests
| from post_tests import PostClusterTest, FinalPost | ||
|
|
||
| # Postgres is on by default | ||
| exit(0) |
There was a problem hiding this comment.
Can you elaborate this comment why these tests are not executed with postgres enabled, instead exit early? I am lacking context to understand this.
There was a problem hiding this comment.
I added a better comment
tests/e2e/run-e2e-tests.sh
Outdated
| ;; | ||
| *) | ||
| die "database $DATABASE not supported" | ||
| export ROX_POSTGRES_DATASTORE="true" |
There was a problem hiding this comment.
Can the case block be removed? It looks like export ROX_POSTGRES_DATASTORE="true" is always executed.
| # Enter central-db image to use (default: "docker.io/stackrox/central-db:2.21.0-15-g448f2dc8fa"): | ||
| # Enter central-db image to use (default: "stackrox.io/central-db:3.67.x-296-g56df6a892d"): | ||
| # Enter central-db image to use (default: "registry.redhat.io/advanced-cluster-security/rhacs-central-db-rhel8:3.68.x-30-g516b4e7a6c-dirty"): |
There was a problem hiding this comment.
Are these defaults hardcoded? Where are they coming from?
Especially the -dirty tags looks like a non-default to me because it is mostly build locally and never pushed to a registry.
There was a problem hiding this comment.
This is just a comment to illustrate the expect below cases
central/processlisteningonport/datastore/datastore_impl_test.go
Outdated
Show resolved
Hide resolved
janisz
left a comment
There was a problem hiding this comment.
I think this should be splitted into smaller PRs.
- Fix go code and prepare it for this change
- fix shell and makefile
- everything else
e2ac78b to
17c7d36
Compare
1d46472 to
b259daf
Compare
8377bd0 to
fb7bc8c
Compare
|
@connorgorman: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
|
The fact that all openshift-*qa-e2e-tests failed worries me. For example: Are we sure these failures are not related to this change @connorgorman ? |
Description
Sets the Postgres flag to always be the default value of the setting
Tests that need to be ported:
Checklist
If any of these don't apply, please comment below.
Testing Performed
CI