Foreman-nightly-deb-pipeline 839 failed

Foreman DEB nightly pipeline failed:

https://ci.theforeman.org/job/foreman-nightly-deb-pipeline/839/

foreman-pipeline-foreman-nightly-ubuntu2004-install (failed) (remote job)
foreman-pipeline-foreman-nightly-debian11-install (passed) (remote job)
foreman-pipeline-foreman-nightly-debian10-upgrade (passed) (remote job)
foreman-pipeline-foreman-nightly-debian10-install (passed) (remote job)
foreman-pipeline-foreman-nightly-ubuntu2004-upgrade (failed) (remote job)

2022-01-07 08:04:22 [DEBUG ] [configure] /Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]/unless: /usr/share/rubygems-integration/all/gems/bundler-2.1.4/lib/bundler/runtime.rb:312:in `check_for_activated_spec!': 
You have already activated thor 1.1.0, but your Gemfile requires thor 1.2.1. Prepending `bundle exec` to your command may solve this. (Gem::LoadError)

Hmmm… Wat?

Ah, I see, new thor was released: thor | RubyGems.org | your community gem host

Wonder why it doesn’t freak out Debian tho…

What requires thor 1.2.1? We explicitly install 1.1.0 (and have packages for that in buster & focal). I can see only this:

$ grep thor Gemfile.lock 
      thor (>= 1.0.1, < 2.0)
      thor (>= 0.20.3, < 2.0)
    thor (1.2.1)

Great question I have no answer for.

Ah, we don’t explicitly install thor, just fetch it, to pre-warm the cache. But then bundle install decides to fetch a newer one…

Let’s see if explicitly pin thor to 1.1.0 by evgeni · Pull Request #7449 · theforeman/foreman-packaging · GitHub helps.

It does, but now building foreman is broken (for unrelated reasons) and we need to wait

this is now fixed