Skip to content
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.

[Bug]: Errors provisioning due to MySQL 8 migration. #1110

Closed
dianakhuang opened this issue Jun 28, 2023 · 5 comments
Closed

[Bug]: Errors provisioning due to MySQL 8 migration. #1110

dianakhuang opened this issue Jun 28, 2023 · 5 comments
Assignees
Labels
bug Report of or fix for something that isn't working as intended

Comments

@dianakhuang
Copy link
Contributor

dianakhuang commented Jun 28, 2023

Describe the bug that you are seeing.

During provisioning of a new devstack, we are seeing this error:

 ✔ Container edx.devstack.mysql57  Running                                                                                                                                                                                               0.0s
+ docker-compose up -d mysql80
[+] Running 0/1
 ⠇ mysql80 Pulling                                                                                                                                                                                                                       2.8s
no matching manifest for linux/arm64/v8 in the manifest list entries
make[1]: *** [impl-dev.provision] Error 18

In order to get past this, we need to run

export DOCKER_DEFAULT_PLATFORM=linux/x86_64/v8

Then it fails on creating new users in credentials.

In order to work around it, one user did this:

Ok, so I executed the contents from provision-mysql80.sql and commented it out during the next make dev.provision call and it moved ahead.

Did this happen on the host (your machine or the remote instance) or in the container?

host

Steps to reproduce.

It seems to be when trying to provision a new devstack install on a Apple Silicon machine.

What system was this issue seen on?

Apple Silicon

Acceptance Criterion

  1. Fresh installs of devstack do not run into MySQL 8.0 container issues during provisioning.
@dianakhuang dianakhuang added the bug Report of or fix for something that isn't working as intended label Jun 28, 2023
@github-actions
Copy link

Follow-up checklist (for Arch-BOM usage)

  • Is the issue flaky or consistent?
  • Does it affect multiple people or multiple types of systems?
  • Update the devstack troubleshooting documentation page if necessary
    • Do we need a new troubleshooting section?
    • Did a troubleshooting section already exist, but it wasn't easy to find given the symptoms?
    • If a recurring issue, should we ticket an automated resolution in place of the doc?

@dianakhuang
Copy link
Contributor Author

dianakhuang commented Jun 28, 2023

We don't know if these issues are affecting hosted devstack as well, which would make this even more urgent.

EDIT: we believe this isn't affecting hosted devstack or Apple Intel machines at all.

@timmc-edx
Copy link
Contributor

Created a separate ticket for the credentials DB user issue: #1111

@rgraber rgraber self-assigned this Jul 6, 2023
@rgraber
Copy link
Contributor

rgraber commented Jul 6, 2023

Adding platform: linux/amd64 to the mysql80 service definition in docker-compose.yml worked for me

@rgraber
Copy link
Contributor

rgraber commented Jul 10, 2023

Fixed with #1116

@rgraber rgraber closed this as completed Jul 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Report of or fix for something that isn't working as intended
Projects
None yet
Development

No branches or pull requests

3 participants