@Dzahn: is this expected? The phorge install doesn’t seem open so I can’t tell if it was migrated.

It was definitely correct to report this nevertheless. Thanks for the ticket. We shoud talk separately about creating the same thing but on bullseye and eventually shutting down the buster and all phabricator instances in favor of a bullseye/phorge instance that is like future production.

Added comments here: T334519#8787677 to make sure we shut this instance down when the time comes. with that the "wmflabs" part should also go away. will be replaced by https://phorge.wmcloud.org

@Aklapper Wondering, what makes you consider this to not be Phabricator?

@Dzahn: The domain. :) Could you elaborate how this is related to Phabricator? Maybe I misunderstand something here.

It is the place where Phabricator changes are supposed to be tested before they hit production, at least in theory.

Remember when "labs" was originally started it was the idea that every service in production has a staging/testing counterpart in cloud and nothing that is actually production runs there.

But by this logic each owner of a service in production also owns it in cloud.

I connected to the instance and mysql is up and running and I see the phabricator databases inside it.

Makes no sense?

I did a systemctl restart mysql and that fixed it.

I could connect to mysql shell though BEFORE the restart as well.

So I guess the only explanation is that some GRANTS had not been reloaded yet?!