Hi,

Today (20221105), I've just updated my Tumbleweed to snapshot 20221103 :

bbo@gecko:~> head -n 2 /etc/os-release
NAME="openSUSE Tumbleweed"
# VERSION="20221103"

This snapshot updated vagrant to 2.3.2. According to my /var/log/zypp/history :

2022-11-05
13:17:25|install|vagrant|2.3.2-1.1|x86_64||repo-oss|5c35f723a05ea166df41aae4980cfa0ec1f951f6bfa187d5f0f583138e5dba0b|
2022-11-05
13:18:13|install|vagrant-vim|2.3.2-1.1|noarch||repo-oss|005affabcdd374fc0a5183924c2d7a8906bfdc83e074b4ee020f0f24cf117fb4|
2022-11-05
13:18:13|install|vagrant-bash-completion|2.3.2-1.1|noarch||repo-oss|99cc0511d63e14c56e24917fae0f7b00e06bc206fb29185775c454b5bc811230|


After the update, it's impossible to execute a vagrant command on my laptop.
For example :

bbo@gecko:~> vagrant init opensuse/Leap-15.4.x86_64
/usr/lib64/ruby/3.1.0/rubygems/specification.rb:1401:in `rescue in block in
activate_dependencies': Could not find 'googleapis-common-protos-types' (~>
1.3) among 144 total gem(s) (Gem::MissingSpecError)
Checked in
'GEM_PATH=/usr/lib64/ruby/gems/3.1.0:/usr/share/vagrant/gems:/home/bbo/.vagrant.d/gems'
at: /usr/share/vagrant/gems/specifications/vagrant-2.3.2.gemspec, execute `gem
env` for more information
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1398:in `block in
activate_dependencies'
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1387:in `each'
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1387:in
`activate_dependencies'
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1369:in `activate'
        from /usr/lib64/ruby/3.1.0/rubygems.rb:286:in `block in
activate_bin_path'
        from /usr/lib64/ruby/3.1.0/rubygems.rb:285:in `synchronize'
        from /usr/lib64/ruby/3.1.0/rubygems.rb:285:in `activate_bin_path'
        from /usr/share/vagrant/gems/bin/vagrant:25:in `<main>'
/usr/lib64/ruby/3.1.0/rubygems/dependency.rb:311:in `to_specs': Could not find
'googleapis-common-protos-types' (~> 1.3) among 144 total gem(s)
(Gem::MissingSpecError)
Checked in
'GEM_PATH=/usr/lib64/ruby/gems/3.1.0:/usr/share/vagrant/gems:/home/bbo/.vagrant.d/gems'
, execute `gem env` for more information
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1399:in `block in
activate_dependencies'
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1387:in `each'
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1387:in
`activate_dependencies'
        from /usr/lib64/ruby/3.1.0/rubygems/specification.rb:1369:in `activate'
        from /usr/lib64/ruby/3.1.0/rubygems.rb:286:in `block in
activate_bin_path'
        from /usr/lib64/ruby/3.1.0/rubygems.rb:285:in `synchronize'
        from /usr/lib64/ruby/3.1.0/rubygems.rb:285:in `activate_bin_path'
        from /usr/share/vagrant/gems/bin/vagrant:25:in `<main>'

To make it work again, I had to install ruby3.1-rubygem-grpc (which pulls
ruby3.1-rubygem-googleapis-common-protos-types) and ruby3.1-rubygem-grpc GEMs.

Here is my ruby version :

bbo@gecko:~> ruby -v
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]

I'm using libvirt as Vagrant provider : 

bbo@gecko:~> rpm -qa |grep vagrant-libvirt
vagrant-libvirt-0.10.2-1.1.x86_64

I did not have this problem with Vagrant 2.2.19-6.2.