Skip to content
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

QA: Test downgrade from master to the last LTS #27002

Closed
bryanboza opened this issue Dec 13, 2023 · 1 comment
Closed

QA: Test downgrade from master to the last LTS #27002

bryanboza opened this issue Dec 13, 2023 · 1 comment

Comments

@bryanboza
Copy link
Member

bryanboza commented Dec 13, 2023

Problem Statement

As part of the process, we need to be able to support the follow cases :

  • We need to be able to downgrade from master to the last LTS versions
  • We need be able to have an instance of master and LTS both in a cluster instance pointing to the same database

Steps to Reproduce

  • Test a downgrade
  • Try a cluster with both nodes pointing to the same DB

Acceptance Criteria

Both scenarios should work without problems.

dotCMS Version

Test on docker // Master

Proposed Objective

Quality Assurance

Proposed Priority

Priority 1 - Show Stopper

@bryanboza
Copy link
Member Author

bryanboza commented Dec 15, 2023

Fixed, tested trying to downgrade from master to the last LTS release and we are starting the servers without problems. I'm able to reindex, open/edit/remove contents.

Also all the portlets continue working as expected.

Also tested, starting a cluster with nodes of master and other one in LTS, no errors detected for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

4 participants