[Bug]: Provisioning is broken on edx-theme changes

Describe the bug that you are seeing.

This may or may not be true. I have not run into this issue myself, but I am creating a ticket based on notes from https://twou.slack.com/archives/C04A66RDPEZ/p1741695463382449.

Did anything change with Devstack and provisioning due to any changes with edx-themes? Do we need to clone this into a different directory? Why are some people running into this?

Possibilities:

• Document the issue and the manual workaround. Communicate to 2U devs.
• Fix the issue to automate the solution.

Additionally, some engineers are being added to the edx org in github without being added to the pull-all team, and thus do not have read-only access to edx-themes. I believe an SRE ticket is needed to get this access.

Did this happen on the host (your machine or the remote instance) or in the container?

TBD

Steps to reproduce.

No response

What system was this issue seen on?

TBD

Aucun fichier, test ni étape reproductible n’est fourni. Commencez par déterminer si l’échec se produit sur l’hôte ou dans le conteneur et comparez le provisionnement après les modifications apportées à edx-themes ; confirmez l’emplacement requis pour le clone et l’accès à pull-all. Le travail est considéré comme terminé lorsqu’une cause et une solution de contournement documentées, ou un correctif automatisé, sont disponibles, et que le chemin d’accès GitHub requis est clarifié.