Gestor de Docker "ReferenceError: bootbox is not defined" al hacer clic en "Reset Upgrade"

[jnm]

Hola, tuve un problema con una actualización que se quedó atascada debido a un error de permisos en el sistema de archivos. Después de solucionarlo y ejecutar ./launcher rebuild web_only (este sitio tiene una configuración de dos contenedores), Discourse y todos los complementos seguían mostrando “Actualizando actualmente”. Hice clic en “Restablecer actualización”, pero no sucedió nada, excepto que se registró este error en la consola del navegador:

docker-manager-app-888922f3ec4fc42543c1916f533f3fecb9af503803eb6b8b59904a2310219d1d.js:33 Uncaught ReferenceError: bootbox is not defined
    at n.resetUpgrade (docker-manager-app-888922f3ec4fc42543c1916f533f3fecb9af503803eb6b8b59904a2310219d1d.js:33)
    at n.send (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:2327)
    at docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:1423
    at a (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:2934)
    at docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:1423
    at e.n._run (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:4194)
    at e.n._join (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:4193)
    at e.n.join (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:4159)
    at f (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:3009)
    at e.t.handler (docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:1422)
resetUpgrade @ docker-manager-app-888922f3ec4fc42543c1916f533f3fecb9af503803eb6b8b59904a2310219d1d.js:33
send @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:2327
(anonymous) @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:1423
a @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:2934
(anonymous) @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:1423
n._run @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:4194
n._join @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:4193
n.join @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:4159
f @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:3009
t.handler @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:1422
(anonymous) @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:2646
dispatch @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:658
v.handle @ docker-manager-vendor-91af87077979e715f4d5034ea05c612f734c3aece05878051e901d07e84878ee.js:653

Solucioné el problema eliminando las claves upgrade: de Redis:

@sam

./launcher enter app
rails c
$redis.keys('upgrade:*').each{|key| $redis.del key }

…pero pensé que debía reportar el problema con el botón “Restablecer actualización”. Parece muy similar a un tema anterior (bloqueado):

Docker Manager "Reset Upgrade" Button is broken

Earlier today I started an update of a plugin (discourse-assign) and all it pritned was the header (“this can take a while”). after 10 minutes it still said the same so I tried the reset button, which didn’t do anything. Figuring I might as well do a rebuild I did the app rebuild but it’s still on that status: [afbeelding] And reset doesn’t work either. How can I manually reset this?

[codinghorror (Jeff Atwood)]

¿Deberíamos asignar esto a @eviltrout?

[eviltrout (Robin Ward)]

No estoy seguro de cómo sucedió, pero bootbox faltaba en nuestro paquete de vendor en docker_manager. He reconstruido nuestros recursos y ahora funciona, aunque tendrás que actualizar docker_manager a la última versión.

[eviltrout (Robin Ward)]

Por tu información, esto no necesita ser retrotraído debido a la forma en que se actualizan los complementos. Todos lo recibirán cuando actualicen su complemento docker_manager.