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

MySQL8 autotests are failing due to "Temporary failure in name resolution" #6747

Closed
rdimaio opened this issue May 2, 2024 · 5 comments · Fixed by #6761
Closed

MySQL8 autotests are failing due to "Temporary failure in name resolution" #6747

rdimaio opened this issue May 2, 2024 · 5 comments · Fixed by #6761
Assignees
Labels
backport Issues which are backported to additional releases Testing

Comments

@rdimaio
Copy link
Contributor

rdimaio commented May 2, 2024

(pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'mysql8' ([Errno -3] Temporary failure in name resolution)")

Example: https://github.com/rucio/rucio/actions/runs/8918099209/job/24492187039

Related issue: docker-library/mysql#1048

@rdimaio rdimaio self-assigned this May 2, 2024
@rdimaio
Copy link
Contributor Author

rdimaio commented May 2, 2024

Deprecation and Removal Notes
Important Change: The deprecated mysql_native_password authentication plugin is now disabled by default. It can be enabled by starting MySQL with the new --mysql-native-password=ON server option, or by adding mysql_native_password=ON to the [mysqld] section of your MySQL configuration file.
For more information, see Native Pluggable Authentication. (Bug #36337893)

rdimaio added a commit to rdimaio/rucio that referenced this issue May 2, 2024
@rdimaio
Copy link
Contributor Author

rdimaio commented May 2, 2024

I tried rolling back to MySQL 8.3 in this commit: rdimaio@595afe9

With this change, I get this error (which is likely related to me not having specified the MySQL version properly):

 rucio.common.exception.ConfigNotFound: Configuration not found.
Details: Could not load Rucio configuration file. Rucio looked in the following paths for a configuration file, in order:
	/opt/rucio/etc/rucio.cfg

(see: https://github.com/rdimaio/rucio/actions/runs/8925397636/job/24514035997)

Then I tried this rdimaio@326fb8f, and I get this error:

WARNING:root:Still waiting for database: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'mysql8' ([Errno 111] Connection refused)")
...
sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (6125, "Failed to add the foreign key constraint. Missing unique key for constraint 'SOURCES_REPLICA_FK' in the referenced table 'replicas'")
[SQL: ALTER TABLE rucio.sources ADD CONSTRAINT `SOURCES_REPLICA_FK` FOREIGN KEY(scope, name, rse_id) REFERENCES rucio.replicas (scope, name, rse_id)]
(Background on this error at: https://sqlalche.me/e/20/e3q8)
Failed to run alembic migration!

(see https://github.com/rdimaio/rucio/actions/runs/8925833658/job/24515450220)

It's a bit unclear to me how we're defining the tests, specifically the versions for the DB systems in our tests. I think the changes that I made here rdimaio@326fb8f should be correct, and it might be an issue that the test pulls the cached image?

@rdimaio rdimaio removed their assignment May 2, 2024
rdimaio added a commit to rdimaio/rucio that referenced this issue May 2, 2024
@rdimaio
Copy link
Contributor Author

rdimaio commented May 2, 2024

By specifying MySQL 8.3 correctly, this way rdimaio@61d00a3:

I think ideally we should use MySQL 8.4 in tests, and fix the deprecated command mentioned here #6747 (comment) (like I attempted in this commit: rdimaio@326fb8f)

Edit: the conveyor stage tests for MySQL 8.3 are unrelated to this issue. See this issue for more: #6751

So we can fix this by pinning to MySQL8.3.

@rdimaio
Copy link
Contributor Author

rdimaio commented May 6, 2024

Discussed with @bari12 and we agreed to pin to mysql:8.3 for now, and update in this follow-up issue: #6759.

bari12 pushed a commit that referenced this issue May 7, 2024
bari12 pushed a commit that referenced this issue May 7, 2024
@rdimaio rdimaio self-assigned this May 7, 2024
maxnoe pushed a commit to maxnoe/rucio that referenced this issue Jun 3, 2024
bari12 pushed a commit that referenced this issue Jun 11, 2024
labkode pushed a commit to labkode/rucio that referenced this issue Jun 26, 2024
rdimaio added a commit to rdimaio/rucio that referenced this issue Jul 11, 2024
@bari12
Copy link
Member

bari12 commented Sep 25, 2024

Backport 32.8.3

@bari12 bari12 added Testing backport Issues which are backported to additional releases labels Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Issues which are backported to additional releases Testing
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants