Page MenuHomePhabricator

clean up phabricator test host situation
Closed, ResolvedPublic

Description

Currently we have multiple phab/phorge test hosts and multiple webproxy URLs in Horizon
but they all have some issue or another.

Recently a user asked which test host to use.

This ticket is to clean this all up.

  • delete test hosts on old version
  • fix test hosts on new version /compare to production
  • make ONE of the web URLs work and communicate it, delete the other proxies

proxies:

https://phabricator-prod.wmflabs.org -> http://172.16.0.173:443

https://phab.wmflabs.org/ -> http://172.16.0.173:80

https://phab-prod-usercontent.wmflabs.org -> http://172.16.0.173:80

https://phabricator.wmflabs.org -> http://172.16.0.173:80

https://phorge.wmcloud.org -> http://172.16.7.98:80

https://phab-bull.wmcloud.org/ -> http://172.16.4.197:80

instances:

phabricator-bullseye (172.16.4.197)

phabricator-prod-1001 (172.16.0.173)

(deleted) (172.16.7.98) NXDOMAIN

Event Timeline

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T19:12:13Z] <mutante> deleting web proxy phorge.wmcloud.org which pointed to 172.16.7.98 which doesn't exist anymore T356530

https://phabricator-prod.wmflabs.org - points to buster VM but times out

https://phab.wmflabs.org/ - points to buster VM, shows database connection error

https://phab-prod-usercontent.wmflabs.org - points to buster VM, redirects to https://phab.wmflabs.org/, database connection error

https://phabricator.wmflabs.org - points to buster VM, redirects to https://phabricator.wikimedia.org

https://phab-bull.wmcloud.org - points to bullseye VM, shows "Site Not Found", no site is configured error

virtual hosts actually configured:

buster:

<VirtualHost *:80>
  ServerName phab.wmflabs.org
  ServerAlias phab-prod-usercontent.wmflabs.org
  ServerAlias bugzilla.wikimedia.org
  ServerAlias bugs.wikimedia.org

bullseye:

<VirtualHost *:80>
  ServerName phab-bull.wmcloud.org
  ServerAlias phab-prod-usercontent.wmflabs.org
  ServerAlias bugzilla.wikimedia.org
  ServerAlias bugs.wikimedia.org

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T19:29:39Z] <mutante> deleting web proxy phabricator-prod.wmflabs.org which pointed to port 443 on the buster instance and timed out T356530

dzahn@deploy-1004:/srv/deployment/phabricator/deployment$ scap deploy
20:10:12 Started deploy [phabricator/deployment@24a2a2a]
20:10:12 Deploying Rev: HEAD = 24a2a2a6f90c3ef6883ef1f9b02ff9340cbf7596
20:10:12 Started deploy [phabricator/deployment@24a2a2a]: (no justification provided)
20:10:12 
== DEFAULT ==
:* phabricator-bullseye.devtools.eqiad1.wikimedia.cloud
:* phabricator-prod-1001.devtools.eqiad1.wikimedia.cloud
20:10:15 phabricator/deployment: fetch stage(s):  50% (in-flight: 1; ok: 1; fail: 0; left: 0) /

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T20:13:54Z] <mutante> running "scap deploy" in /srv/deployment/phabricator/deployment on deploy-1004 which deploys to phabricator-bullseye and phabricator-prod-1001 T356530

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T20:17:03Z] <mutante> editing proxies phab.wmflabs.org and phab-prod-usercontent.wmflabs.org to point to bullseye instance instead of buster T356530

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T20:38:34Z] <mutante> deleting proxy phab-bull.wmcloud.org after previous proxy names are switched to bullseye backend T356530

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T20:41:44Z] <mutante> shutting down instance phabricator-prod-1001 (buster), replaced by phab-bullseye (bullseye) T356530

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T20:59:51Z] <mutante> - changing phabricator domain in instance Hiera of phabricator-bullseye to phab.wmflabs.org and running puppet to update apache config/rewrite rules T356530

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T22:26:59Z] <mutante> - deleted proxies phab.wmflabs.org, phab-prod-usercontent.wmflabs.org, phabricator.wmflabs.org - created proxies phabricator.wmcloud.org, phab-usercontent.wmcloud.org - wmflabs names are legacy and should migrate T356530

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T22:31:58Z] <mutante> - phabricator-bullseye, instance hiera: setting phabricator_domain to phabricator.wmcloud.org and phabricator_altdomain to phab-usercontent.wmcloud.org T356530

Change 995366 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] cloud/devtools: update phabricator domain and altdomain

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

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T22:37:21Z] <mutante> - phabricator-bullseye - /srv/deployment/phabricator/deployment/phabricator/bin$ sudo ./config set phabricator.base-uri 'http://phabricator.wmcloud.org/' T356530

Change 995366 merged by Dzahn:

[operations/puppet@production] cloud/devtools: update phabricator domain and altdomain

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

Mentioned in SAL (#wikimedia-cloud) [2024-02-02T22:53:05Z] <mutante> - phabricator-bullseye sudo ./config set phabricator.base-uri 'http://phabricator.wmcloud.org/' | sudo ./config set security.alternate-file-domain 'https://phab-usercontent.wmcloud.org' | delete proxy phab-prod-usercontent, create proxy phab-usercontent.wmcloud.org, restart apache T356530

https://phabricator.wmcloud.org is now the new and fixed test host for phorge (phabricator) (on bullseye).

We don't have any authentication providers though for now and I think we are not allowed to use wikitech LDAP. So no logins so far.

I could confirm though that the admin user can create test tickets in maniphest.

unlocked the auth config option with shell command:

phabricator/bin$ sudo ./auth unlock

configured the most simple auth provider that lets users register with password

locked the auth config option again.

Can we redirect https://phab.wmflabs.org/ to the current instance, as its the documented testing environment? It's even the main page of our normal phab environment.

I would prefer to fix the documentation since both the term "phab" and the term "labs" are legacy and should be phased out.

But of course it's valid that any mention of it should be replaced.

I updated the main page of this instance.

https://wikitech.wikimedia.org/wiki/Nova_Resource:Redirects can be used to serve a redirect for the old name if needed.

LSobanski triaged this task as Medium priority.Feb 6 2024, 2:29 PM
LSobanski moved this task from Incoming to Backlog on the collaboration-services board.

https://wikitech.wikimedia.org/wiki/Nova_Resource:Redirects can be used to serve a redirect for the old name if needed.

Thanks for pointing out this project.

It seems debatable whether I should use "phorge.wmcloud" because Phorge is the upstream name now or "phabricator.wmcloud" because it matches production and is less confusing. Renaming the production service would of course be a bigger deal.

Now I have set it up so that all variants redirect, so:

https://phab.wmflabs.org -> https://phabricator.wmcloud.org
https://phorge.wmflabs.org -> https://phabricator.wmcloud.org
https://phab.wmcloud.org -> https://phabricator.wmcloud.org
https://phorge.wmcloud.org -> https://phabricator.wmcloud.org

I don't see much else to update in Google. Editing old ticket titles seems to be going too far and we have the redirects in place. Guess that's it? Correct me if you think I am missing something else please.

I cleaned up the references I could find on mwwiki, and remarked the pages for translation (i think)

Mentioned in SAL (#wikimedia-cloud) [2024-02-09T19:08:40Z] <mutante> deleting instance phabricator-prod-1001 (shut down a couple days ago, buster instance replaced by phabricator-bullseye instance) T356530