Skip to content

Remove Java and Timezone notices - when upgrading from 4.14+#219

Merged
yadvr merged 2 commits into4.15from
4.15-to-4.15.1
Jul 5, 2021
Merged

Remove Java and Timezone notices - when upgrading from 4.14+#219
yadvr merged 2 commits into4.15from
4.15-to-4.15.1

Conversation

@andrijapanicsb
Copy link
Copy Markdown
Contributor

@andrijapanicsb andrijapanicsb commented Jun 7, 2021

Removed the notice about Java 11 version and timezone in my.cnf or db.properties - as these already HAVE to be in place in order to even run the 4.15.0 (this is upgrade page FROM 4.15.0 to 4.15.1).

ping @rhtyd @DaanHoogland for review pls (need to do the same for upgrade FROM 4.14)

@andrijapanicsb
Copy link
Copy Markdown
Contributor Author

@blueorangutan docbuild

@blueorangutan
Copy link
Copy Markdown

@andrijapanicsb a Jenkins job has been kicked to build the document. I'll keep you posted as I make progress.

@blueorangutan
Copy link
Copy Markdown

Doc build preview: http://qa.cloudstack.cloud/docs/WIP-PROOFING/pr/219. (SL-JID 86)

..as they are already in place in 4.14.
@andrijapanicsb andrijapanicsb changed the title Update upgrade-4.15.rst Remove Java and Timezone notices - when upgrading from 4.14+ Jun 7, 2021
@yadvr yadvr added this to the 4.15 milestone Jun 7, 2021
@yadvr
Copy link
Copy Markdown
Member

yadvr commented Jun 7, 2021

LGTM on the java include, but what about the timezone fix? Is that not required anymore?

@andrijapanicsb
Copy link
Copy Markdown
Contributor Author

You are upgrading from 4.14 (4.14.1) or 4.15 - and the timezone in db.properties needs to be there to be able to run those (older) versions - i.e. it's already there.

So no need to add it "again" - that's why both changes/removals I've proposed.

Copy link
Copy Markdown
Member

@GabrielBrascher GabrielBrascher left a comment

Choose a reason for hiding this comment

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

LGTM

@yadvr yadvr merged commit d21a473 into 4.15 Jul 5, 2021
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