Docker Manager "ReferenceError: bootbox is not defined" when clicking "Reset Upgrade"

[jnm]

Hello, I had an upgrade get stuck due to a filesystem permission issue. After fixing that and using ./launcher rebuild web_only (this site has a two-container setup), Discourse and all plugins still showed “Currently Upgrading”. I clicked “Reset Upgrade”, but nothing happened, except that this error was logged in the browser’s console:

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

I worked around this by removing the upgrade: keys from Redis:

@sam

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

…but I thought I should report the “Reset Upgrade” button issue. It seems very similar to an older (locked) topic:

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)]

Should we assign this @eviltrout?

[eviltrout (Robin Ward)]

I’m not sure how it happened but bootbox was missing from our vendor package in docker_manager. I rebuilt our assets and it’s working now, although you will have to upgrade docker_manager to the latest version.

[eviltrout (Robin Ward)]

FYI this needn’t be backported due to the way plugins are updated. Everyone will get it when they update their docker_manager plugin.