665867 - enable mysql access from autoland-staging{01,02}.build

Status: RESOLVED FIXED

(Data & BI Services Team :: DB: MySQL, task)

Description

[Lukas Blakk [:lsblakk] use ?needinfo]

+++ This bug was initially created as a clone of Bug #663017 +++

+++ This bug was initially created as a clone of Bug #657764 +++

Probably need both mysql ACLs and firewall access granted.

Comment 1

[[e-mail] (:bhearsum)]

Just for the staging databases, right?

Comment 2

[Lukas Blakk [:lsblakk] use ?needinfo]

no, i need to be able to read the real production data (try pushes and other branches) for testing - read only so if there's a user account set up for read-only than that will work for this.

Comment 3

[Matt Pressman [:mpressman]]

which database[s] do you need read-only access to?

Comment 4

[Lukas Blakk [:lsblakk] use ?needinfo]

read-only access for user buildbot_reader to tm-b01-slave01.mozilla.org/buildbot_schedulers

Comment 5

[Dustin J. Mitchell [:dustin] (he/him)]

The MySQL slave has a noticeable delay (seconds) from the master - is that going to lead to timing problems where the autoland code expects rows in the database that may not have arrived yet?  If not, woo for finding a use for the r/o slave!

Comment 6

[Matt Pressman [:mpressman]]

The replication delay from the slave is most likely due to locked tables where the insert thread has to wait for a table, most likely a MyISAM table that is in use. This certainly can lead to timing problems. There are some tuning options that can give a higher priority to the writing thread of the master that will help to prevent that delay, however, the drawback is that read queries may yield longer.

Comment 7

[Lukas Blakk [:lsblakk] use ?needinfo]

(In reply to comment #5)
> The MySQL slave has a noticeable delay (seconds) from the master - is that
> going to lead to timing problems where the autoland code expects rows in the
> database that may not have arrived yet?  If not, woo for finding a use for
> the r/o slave!

seconds of delay will not be a problem for this use case.

Comment 8

[Aaron]

Network access should be open.

Comment 9

[Marc Jessome[:mjessome]]

Getting permission error:

sqlalchemy.exc.OperationalError: (OperationalError) (1130, "Host '10.12.51.250' is not allowed to connect to this MySQL server") None None

connecting to url:
mysql://buildbot_reader:[e-mail]/buildbot_schedulers

Comment 10

[Marc Jessome[:mjessome]]

Is it possible to get this done asap? My last day here and it would be nice to get some full staging runs done before the end of the day.

Comment 11

[Lukas Blakk [:lsblakk] use ?needinfo]

Thanks to Matt Pressman who added the autoland-staging01 host address to the allowed list of connections for buildbot_reader we are now able to connect.

Comment 12

[Marc Jessome[:mjessome]]

tm-b01-slave01.mozilla.org is unreachable from autoland-staging02.
Accessing through mysql://buildbot_reader:[e-mail]/buildbot_schedulers
Looking at the history of this bug, access was only ever added for autoland-staging01.

This is blocking us moving forward with staging of Autoland.

Thanks.

Comment 13

[Sheeri Cabral [:sheeri]]

mysql> GRANT SELECT, CREATE TEMPORARY TABLES ON `buildbot_schedulers`.* TO 'buildbot_reader'@'10.12.51.251'  IDENTIFIED BY PASSWORD 'ELIDED';

(note: the password *was* elided....the password is not the word ELIDED). Same pass as buildbot_reader@10.12.51.250.

Comment 14

[Marc Jessome[:mjessome]]

Netflow has been opened, can successfully connect.