I have a blocking issue that’s preventing me from upgrading my tutor-based system.
It manifests as
> [learning-common 5/5] RUN make OPENEDX_ATLAS_PULL=true ATLAS_OPTIONS="--repository=openedx/openedx-translations --revision=open-release/redwood.3 " pull_translations:
0.581 tx pull -f --mode reviewed --languages="ar,fr,es_419,zh_CN,pt,it,de,uk,ru,hi,fr_CA"
0.599 /bin/sh: 1: tx: not found
0.599 make: *** [Makefile:47: pull_translations] Error 127
when I attempt upgrade via
pip install "tutor[full]==v18.2.2"
tutor config save
tutor images build all
I posted a ticket about it both to the tutor issues and openedx-translations issues, because I wasn’t clear if it was a tutor-specific issue or a regression in openedx-translations.
While someone helpfully replied to the first ticket, their solution didn’t work. My remaining questions a
Is this a tutor-specific issue (and therefore I should close the second openedx-translations ticket)?
Does anyone have any other ideas on how to work around this?
Seems like a custom code issue. We don’t use tx anymore and I’m unsure what is learning-common anyway.
Woud you mind sharing more how did you reach this and it seems that you’ve used an outdated cookie-cuttor or a previous release with some bad merge conflicts.
I don’t think it’s custom code on my part (so are you saying you think it’s a custom tutor code problem @omar?), because I’m specifically leaving out any building of containers with my forked edx-platform, just to test the upgrade.
I start from Palm (Tutor 16.1.8), and then I first upgrade successfully to Quince (Tutor 17) with:
pip install "tutor[full]==v17.0.6"
tutor config save
tutor images build all
tutor local upgrade --from=palm
tutor local launch
It’s only when I then do the above upgrade to Redwood that the same steps don’t work.
Are you saying perhaps that I need to re-build my Palm images without any customizations before upgrading, because somehow the customizations are staying resident even though I’m saying to rebuild all the images (without giving any CLI arg to use my forks)?
It’s hard to tell what’s going wrong without looking into all parameters i.e. checking the server first-hand.
But it’s definitly that Redwood image builds are trying to run pull_translations on an image which doesn’t have the Redwood version of pull_translations
For a background, pre-Redwood pull_translations calls tx, but from Redwood onward, it’s using atlas so Docker images and the source code (Makefiles) are not in the same version.