Page MenuHomePhabricator

Request to add user gmodena to analytics-research-admins group
Closed, ResolvedPublic

Description

Hi,

I'd need access to this group in order to deploy https://gitlab.wikimedia.org/repos/research/knowledge-gaps/-/issues/3 to an-airflow1002.eqiad.wmnet.

Event Timeline

Approved, and I'll make it happen :)

Change 779096 had a related patch set uploaded (by Ottomata; author: Ottomata):

[operations/puppet@production] Add gmodena to analytics-research-admins for airflow access

https://gerrit.wikimedia.org/r/779096

Change 779096 merged by Ottomata:

[operations/puppet@production] Add gmodena to analytics-research-admins for airflow access

https://gerrit.wikimedia.org/r/779096

jcrespo added a subscriber: jcrespo.

@gmodena Did the access work?

Change 779542 had a related patch set uploaded (by Ottomata; author: Ottomata):

[operations/puppet@production] Allow analytics-research-admins to access deploy_airflow key

https://gerrit.wikimedia.org/r/779542

Change 779542 merged by Ottomata:

[operations/puppet@production] Allow analytics-research-admins to access deploy_airflow key

https://gerrit.wikimedia.org/r/779542

@gmodena Did the access work?

Hey @jcrespo, I tried a deployment that failed with:

== DEFAULT ==
:* an-airflow1002.eqiad.wmnet
11:38:04 ['/usr/bin/scap', 'deploy-local', '-v', '--repo', 'airflow-dags/research', '-g', 'default', 'fetch', '--refresh-config'] (ran as analytics-research@an-airflow1002.eqiad.wmnet) returned [255]: sign_and_send_pubkey: signing failed: agent refused operation
analytics-research@an-airflow1002.eqiad.wmnet: Permission denied (publickey,keyboard-interactive).

11:38:04 connection to an-airflow1002.eqiad.wmnet failed and future stages will not be attempted for this target
airflow-dags/research: fetch stage(s): 100% (in-flight: 0; ok: 0; fail: 1; left: 0)
11:38:04 1 targets had deploy errors
11:38:04 1 targets failed
11:38:04 1 of 1 default targets failed, exceeding limit

@Ottomata is helping me out with troubleshooting.

Ottomata claimed this task.

The access works though! We'll figure out the deployment issues separately.