-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Installation fails with foreign key constraint error #681
Comments
After updating my stack to use |
Thank you. I think it is a bug. I will try reproduce it. |
Experienced the same error when trying to do a regular installation on Rocky Linux 8.4. Problem appeared when using "MariaDB-server-10.6.4-1.el8.x86_64" from the official MariaDB CentOS repository. Seeing @kolbyjack had succeeded using MySQL 5.6 I figured it might be a new feature/change/deprecation in MariaDB and I tried going back to "mariadb-server-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64" from the Rocky Linux repos. Also made sure to remove the MariaDB data directory contents before switching to 10.3.28. Error disappeared and Semaphore server is now starting up without issue. |
Same error on Ubuntu 20.04.3 LTS using 10.6.4+maria~focal.
|
Same error on Debian 11.0 using 10.5.11-MariaDB
|
Thank you. I will check MariaDB |
Troubleshooting detail: Environment: NAME="AlmaLinux" / VERSION="8.4 (Electric Cheetah)" / ID="almalinux" / ID_LIKE="rhel centos fedora" / VERSION_ID="8.4" What Works: Completed a mysqldump of 10.4.21-MariaDB after a fresh setup from semaphore_2.7.16_linux_amd64.rpm. [Dump script below] The failure seems to be related to the actual migration script itself ... near v1.0.0 as documented by HuTaeh. The bug surfaces with the use of MariaDB 10.6+ during 'setup'. == -- MariaDB dump 10.19 Distrib 10.4.21-MariaDB, for Linux (x86_64) /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; -- DROP TABLE IF EXISTS `access_key`; -- DROP TABLE IF EXISTS `event`; -- DROP TABLE IF EXISTS `migrations`; -- DROP TABLE IF EXISTS `project`; -- DROP TABLE IF EXISTS `project__environment`; -- DROP TABLE IF EXISTS `project__inventory`; -- DROP TABLE IF EXISTS `project__repository`; -- DROP TABLE IF EXISTS `project__schedule`; -- DROP TABLE IF EXISTS `project__template`; -- DROP TABLE IF EXISTS `project__user`; -- DROP TABLE IF EXISTS `session`; -- DROP TABLE IF EXISTS `task`; -- DROP TABLE IF EXISTS `task__output`; -- DROP TABLE IF EXISTS `user`; -- DROP TABLE IF EXISTS `user__token`; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; ==EDIT==
|
Fixed, Meriadb supported. |
@fiftin can you let us know how it was fixed? |
I'm trying to set up an semaphore docker stack using the docker-compose file from #148 (comment), but when I run docker-compose up, the container fails with
The text was updated successfully, but these errors were encountered: