Problem/Motivation

MariaDB 10.3.22 conf/setup.sql creates a user that already exists when the image is spin up in GitlabCI. That causes the container not to run and make tests fail (check parent issue).

I've tested this building a local image of drupalci:mariadb10.3.22 and using this for gitlab-ci-local in parent's MR code

Steps to reproduce

Proposed resolution

Remove the first line "CREATE USER ..." from "db/mariadb-10.3.22/conf/setup.sql"

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

  • dev Comparechanges, plain diff MR !30

Comments

dimitriskr created an issue. See original summary.

dimitriskr’s picture

Title: MariaDB 10.3.22 setup.sql creates a user that exists » MariaDB 10.3.22 setup.sql creates a user that already exists
Issue summary: View changes

fjgarlin’s picture

I see that the approach taken in the "mysql" images is different, where the commands to create the user and flush priviledges is done in the startup.sh script. "mariadb" images follow a different approach, so I wonder if the user is created at all.

andypost’s picture

Let's unify the approach, I think pgsql images makes sense to check as well as they were the last anybody touch

dimitriskr’s picture

Core tests still pass with the new approach.
As discussed in a Slack thread, no changes will take place at MariaDB 10.2 version yet

fjgarlin’s picture

@dimitriskr - is this ready for review or are you planning to do some more work here?

dimitriskr’s picture

Status: Active » Needs review

Ah sorry, yeap, it's ready for review.

fjgarlin’s picture

The refactoring looks good to me, but probably @andypost will be better positioned to fully review and merge this.
As soon as it's merged to "dev" or "prod" images, we can test the core issue. Thanks!

dimitriskr’s picture

@andypost, shall we unify the approaches of all DBs here on this issue, or create a follow-up?

catch’s picture

For me I think we should do the consolidation in a follow-up. This will issue will allow us to switch off more DrupalCI jobs, and bring us closer to being able to shut it down (for core testing at least) altogether.

andypost’s picture

It looks good to me but I have no ability to test/merge it in next 2 days

Probably I need to squash commits via Gitlab to simplify cherry-picking to production branch

fjgarlin’s picture

Just following up. Any update on this? If it gets merged to dev we'd be able to further review and test here #3385621: [GitlabCI] MariaDB currently not working.

andypost’s picture

Status: Needs review » Reviewed & tested by the community

Merged to dev so it can be tested as pipeline passed https://git.drupalcode.org/project/drupalci_environments/-/commit/176e3d...

andypost’s picture

Status: Reviewed & tested by the community » Needs work

andypost’s picture

Status: Needs work » Reviewed & tested by the community

Looks now it working https://git.drupalcode.org/issue/drupal-3385621/-/pipelines/54549

the issue hew is that the image no longer maintained(

  • andypost committed 1038da61 on production authored by dimitriskr
    MariaDB 10.3.22 - remove "create user" statement #3399858
    
    
    (cherry...
andypost’s picture

Status: Reviewed & tested by the community » Fixed
fjgarlin’s picture

Big THANK YOU.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.