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

[robrap]

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

[github-actions]

Follow-up checklist (for Arch-BOM usage)

• Is the issue flaky or consistent?
• Does it affect multiple people or multiple types of systems?
• Update the devstack troubleshooting documentation page if necessary
  • Do we need a new troubleshooting section?
  • Did a troubleshooting section already exist, but it wasn't easy to find given the symptoms?
  • If a recurring issue, should we ticket an automated resolution in place of the doc?

[justinhynes]

Did anything change with Devstack and provisioning due to any changes with edx-themes?

The problem isn't related to a change in edx-themes, rather a change in how settings are handled in edx-platform.

When provisioning the LMS in devstack, we try to setup comprehensive theming too. Provisioning manipulates the devstack.py file that is part of the edx-platform project. The settings in devstack.py are stale and don't conform to the recent settings changes introduced in commit openedx/edx-platform@3227566.

[justinhynes]

(x-post of info from Slack [https://twou.slack.com/archives/C04A66RDPEZ/p1741887423563689?thread_ts=1741787941.101469&cid=C04A66RDPEZ])

I was able to reproduce the issue provisioning a new local devstack from scratch on my machine.

Here are the changes I needed to fix the issue:

1. fix: fixup devstack.py settings file openedx/edx-platform#36375
2. fix: fixup theming setup during devstack provisioning #121

I'm not sure the fix is totally correct because the devstack.py file is deprecated. It may be something we can use in the short term to ensure provisioning works as intended, for now.

Happy to take another go at it if there is another way to work around modifying the deprecated settings file in edx-platform.