-
Notifications
You must be signed in to change notification settings - Fork 141
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
Artifactory Upgrades #373
Comments
Is there specific documentation for migrating your MySQL DB and filestore to another host and getting it to the latest version? I am trying also to use Ansible Automation, which doesn't address MySQL installation, migration, etc. What files to bring over, aka licenses file? other configuration files? Should I just be able to
Why am I getting the above DB error? Any help would greatly be appreciated. |
@darthVikes - MySQL upgrades are not part of the ansible upgrade process. What I can suggest is to first upgrade MySQL for 7.19.4 to MySQL 5.7 and subsequently do the upgrade for Artifactory to latest version. I'll suggest reaching out JFrog Support or JFrog Community Support for further help. |
Ok thanks. Hopefully they can help with these db issues. |
Is this a request for help?: Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one): No
behavior/change you'd like to see.
Which installer: Ansible
Which product and version (eg: ansible & collection version - 7.24.2): Currently on 7.19.4
Which operating system and version(eg: ubuntu & version - 20.4): Ubuntu currently, but migrating to RHEL 9.x
Which product license (Enterprise/Pro): PRO
JFrog support reference (if already raised with the support team): NA
What happened:
Should I be able to upgrade to the latest version? Or do I need to upgrade to X version before going to X version? aka more step upgrade?
What you expected to happen:
Deploy build X and that on startup will upgrade the database information?
How to reproduce it (as minimally and precisely as possible):
Tried to upgrade to 7.77.3 but with the migration to another MySQL which requires us to go from 5.x to 8.x there are some challenges. Currently, it's giving me a bunch of permissions issues.
2024-02-07T22:12:21.859Z ^[[1;33m[jfac ]^[[0;39m ^[[1;31m[ERROR]^[[0;39m [23239644096eaeec] [.s.d.u.AccessJdbcHelperImpl:73] [Catalina-utility-2 ] - Could not initialize database:
org.flywaydb.core.api.FlywayException: Detected failed migration to version 7.44 (Add access permission v2 ref)
at org.flywaydb.core.internal.info.MigrationInfoImpl.validate(MigrationInfoImpl.java:218)
at org.flywaydb.core.internal.info.MigrationInfoServiceImpl.validate(MigrationInfoServiceImpl.java:327)
at org.flywaydb.core.internal.command.DbValidate$2.call(DbValidate.java:174)
at org.flywaydb.core.internal.command.DbValidate$2.call(DbValidate.java:164)
at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:75)
at org.flywaydb.core.internal.command.DbValidate.validate(DbValidate.java:164)
at org.flywaydb.core.Flyway.doValidate(Flyway.java:1017)
at org.flywaydb.core.Flyway.access$100(Flyway.java:72)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:934)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:930)
at org.flywaydb.core.Flyway.execute(Flyway.java:1413)
at org.flywaydb.core.Flyway.migrate(Flyway.java:930)
The text was updated successfully, but these errors were encountered: