Skip to content

Adding application high availability check in operator upgrade tests #2039

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

Merged
merged 7 commits into from
Nov 9, 2020

Conversation

vanajamukkara
Copy link
Member

@vanajamukkara vanajamukkara commented Nov 6, 2020

Adding application high availability check in operator upgrade tests.
An application is deployed to the cluster in the domain and the application is continuously accessed from a separate thread while the operator is being upgraded and after the upgrade.

This check is added only for operator releases 3.0.0 and later, Ryan confirmed this is not needed for older releases.

Jenkins results:
sequential run - https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/3056/
Just upgrade test - https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/3054/

Upgrade tests are not run in parallel

@vanajamukkara vanajamukkara marked this pull request as ready for review November 9, 2020 15:24
@anpanigr
Copy link
Member

anpanigr commented Nov 9, 2020

Add an Upgrade Test for Release 3.0.3 in this PR

appAccessedAfterUpgrade = true;
}

try {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason for the delay here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed as upgrade is not taking much time. This was added to introduce some delay if the other thread is going to take long time.

@@ -169,7 +190,9 @@ public void testOperatorUpgradeFrom3_0_2(@Namespaces(3) List<String> namespaces)
*/
@AfterEach
public void tearDown() {
if (System.getenv("SKIP_CLEANUP") == null) {
if (System.getenv("SKIP_CLEANUP") == null
|| (System.getenv("SKIP_CLEANUP") != null
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the point of checking for both null and not null? If its null isn't it the next statement going to throw NPE?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

clarified on slack

vanajamukkara and others added 4 commits November 9, 2020 18:14
@vanajamukkara
Copy link
Member Author

vanajamukkara commented Nov 9, 2020

Add an Upgrade Test for Release 3.0.3 in this PR

Added, here is the Jenkins results with 3.0.3 upgrade test.
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/3077/

Copy link
Member

@sankarpn sankarpn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@anpanigr anpanigr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rjeberhard rjeberhard merged commit daad271 into develop Nov 9, 2020
@rjeberhard rjeberhard deleted the highavailabilitytests branch January 5, 2021 22:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants