Enable git repo creation in Diffusion again
Closed, ResolvedPublicBUG REPORT
Actions

Assigned To

Authored By

	QChris
	Jan 23 2024, 8:02 AM

Description

While creating a git repository in Diffusion worked up at least up to 2024-01-15, it now fails (from both API and Web interface) since at least 2024-01-17 with error message:

This install is configured in cluster mode, but all available repository cluster services are closed to new allocations. At least one service must be open to allow new allocations to take place.

Could we please allow repo creation again?

More context:

When adding a new git repo in Gerrit, we typically set up a corresponding mirror in Diffusion. This Diffusion mirror allows to use commit hashes in Phabricator task descriptions and have them automatically link to the corresponding commit, which is handy.

Details

	Title	Reference	Author	Source Branch	Dest Branch
	Reinstate custom rPHABd8dd5f4b71ea8af64831dde779c598554a0a50f9	repos/phabricator/phabricator!37	aklapper	diffRepoCreateT355644	wmf/stable

Customize query in GitLab

Related Objects
Search...

		Status	Subtype	Assigned	Task
		Open	Feature	None	T262219 Mirror all Gerrit and GitLab repos that are currently not mirrored to Diffusion
		Resolved	BUG REPORT	Aklapper	T355644 Enable git repo creation in Diffusion again

Event Timeline

QChris created this task.Jan 23 2024, 8:02 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJan 23 2024, 8:02 AM

taavi added a project: Phabricator.Jan 23 2024, 8:07 AM

ping :-)

Do we want to do use the "corresponding mirror[s] in Diffusion"? They're such a mess in random pings in Phabricator and otherwise never used?

In T355644#9502223, @Jdforrester-WMF wrote:

Do we want to do use the "corresponding mirror[s] in Diffusion"?

Back in the day, when I still used Phabricator more, I certainly liked to be able to easily link to commits. And I saw others using this functionality as well.
But if it's no longer used, or it became a nuisance, let's no longer create them and decline this task :-)

(I pretty much do not care either way, as setting up the mirrors is scripted anyways, so creating mirrors does not incur work for me ... that is: as long as Phabricator is not in cluster modes and prohibits repo creation)

Is there some consensus about declining this task?

Uhm, looks like an unexpected regression from T352530 so reverting https://gitlab.wikimedia.org/repos/phabricator/phabricator/-/commit/7aab490d91b519324ee29e46d73581348c13a793 could be worth a shot