서드파티 플러그인 오류로 최신 버전 업그레이드 실패

안녕하세요,

최근 Discourse를 최신 버전(beta4에서 beta5)으로 업그레이드하려고 시도했습니다.
먼저 관리자 인터페이스를 통해 업그레이드를 시도했으나 오류가 발생했고, 불행히도 메시지를 읽지 못해 로그 텍스트를 저장하지 못했습니다. 이후 중요한 업데이트가 사용 가능하다는 메시지를 보았지만, 새 버전을 확인해 보니 모든 것이 최신 상태라고 나타났습니다.
그 후 저는 Discourse 컨테이너를 다시 빌드하기로 결정했습니다. 그 결과 포럼이 중단되고 다음과 같은 오류가 발생했습니다:

I, [2019-10-02T06:49:25.567952 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
NameError: uninitialized constant #<Class:#<Plugin::Instance:0x0000563c89408050>>::Validators
/var/www/discourse/plugins/discourse-quick-messages/plugin.rb:45:in `block in activate!'
/var/www/discourse/lib/plugin/instance.rb:329:in `block in notify_after_initialize'
/var/www/discourse/lib/plugin/instance.rb:327:in `each'
/var/www/discourse/lib/plugin/instance.rb:327:in `notify_after_initialize'
/var/www/discourse/config/application.rb:307:in `each'
/var/www/discourse/config/application.rb:307:in `block in <class:Application>'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:69:in `block in execute_hook'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:62:in `with_execution_control'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:67:in `execute_hook'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:52:in `block in run_load_hooks'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:51:in `each'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/lazy_load_hooks.rb:51:in `run_load_hooks'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/application/finisher.rb:129:in `block in <module:Finisher>'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/initializable.rb:32:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/initializable.rb:32:in `run'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/initializable.rb:61:in `block in run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/initializable.rb:60:in `run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/application.rb:363:in `initialize!'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/railtie.rb:190:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/railtie.rb:190:in `method_missing'
/var/www/discourse/config/environment.rb:7:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.10/lib/zeitwerk/kernel.rb:23:in `require'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.10/lib/zeitwerk/kernel.rb:23:in `require'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `block in require'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:291:in `load_dependency'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/activesupport-6.0.0/lib/active_support/dependencies.rb:325:in `require'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/application.rb:339:in `require_environment!'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/railties-6.0.0/lib/rails/application.rb:515:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rake-12.3.3/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => db:migrate => environment
(See full trace by running task with --trace)
I, [2019-10-02T06:49:42.040895 #1]  INFO -- : gem install holidays -v 7.1.0 -i /var/www/discourse/plugins/discourse-calendar/gems/2.6.4 --no-document --ignore-dependencies --no-user-install
Successfully installed holidays-7.1.0
1 gem installed

168:signal-handler (1569998982) Received SIGTERM scheduling shutdown...
I, [2019-10-02T06:49:42.041625 #1]  INFO -- : Terminating async processes
I, [2019-10-02T06:49:42.041737 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 51
I, [2019-10-02T06:49:42.041825 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 168
2019-10-02 06:49:42.041 UTC [51] LOG:  received fast shutdown request
2019-10-02 06:49:42.088 UTC [51] LOG:  aborting any active transactions
2019-10-02 06:49:42.092 UTC [51] LOG:  worker process: logical replication launcher (PID 60) exited with exit code 1
2019-10-02 06:49:42.092 UTC [55] LOG:  shutting down
168:M 02 Oct 2019 06:49:42.103 # User requested shutdown...
168:M 02 Oct 2019 06:49:42.103 * Saving the final RDB snapshot before exiting.
2019-10-02 06:49:42.221 UTC [51] LOG:  database system is shut down
168:M 02 Oct 2019 06:49:42.441 * DB saved on disk
168:M 02 Oct 2019 06:49:42.441 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 609 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
211e22376351c9b68dc74efc4e98436330f7e3ecea76985928c29c45072901bf
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.

discourse-doctor는 다음과 같은 결과를 반환했습니다:

DISCOURSE DOCTOR Wed Oct 2 10:11:59 MSK 2019
OS: Linux klerk-discourse 3.10.0-957.1.3.el7.x86_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux


Can't find app.yml or web_only.yml.
Giving up.

이후 Discourse 컨테이너는 시작되지만, Discourse에는 웹 접근이 불가능한 상태입니다.
Discourse를 성공적으로 업그레이드하고 시작하려면 어떻게 해야 하나요?

위 오류 메시지에 표시된 대로, 문제는 서드파티 플러그인입니다. 플러그인을 제거한 후 다시 빌드하세요.

이제 빌드 구성에서 discourse-quick-messages 플러그인을 제외했습니다. 그 후 컨테이너가 성공적으로 재빌드되었고 Discourse가 시작되었습니다. 현재 Discourse 버전과 discourse-quick-message 플러그인이 호환되지 않는 것 같습니다. 새로운 플러그인 버전을 기다리고 있습니다.

감사합니다. discourse-quick-messages 플러그인이었네요.