ci: pin fog-json to resolve gem conflict#13707
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the CI workflow’s Vagrant/libvirt setup to avoid a RubyGems conflict caused by Vagrant’s embedded Ruby preloading an older json gem spec, by pinning fog-json to a compatible version before installing vagrant-libvirt.
Changes:
- Add an explicit
vagrant plugin install fog-json --plugin-version 1.2.0step prior to installingvagrant-libvirt.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
2b11d2e to
b8dcd71
Compare
Vagrant 2.4.x bundles an embedded Ruby 3.3.0 runtime that loads the default specification json-2.7.2 during initialization. When installing vagrant-libvirt, RubyGems resolves the newly released fog-json 1.4.0, which requires json (~> 2.19). Because json-2.7.2 is already active in memory when Vagrant starts up, RubyGems raises a Gem::ConflictError. To avoid this conflict, pin fog-json to version 1.2.0 before installing vagrant-libvirt. Since CI caches /root/.vagrant.d across runs, also uninstall fog-json first to remove any conflicting version left in cache by a previous job. Assisted-by: Antigravity Signed-off-by: Samuel Karp <[email protected]>
b8dcd71 to
84112c7
Compare
AkihiroSuda
added
cherry-picked/1.7.x
|
/cherry-pick release/1.7 |
|
@AkihiroSuda: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherry-pick release/2.1 Forgot this one? 😄 |
|
@samuelkarp: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
It will reach EOL tomorrow though |
github-project-automation
Bot
moved this from Needs Triage
to Review In Progress
in Pull Request Review
fuweid
added
the
cherry-picked/2.1.x
github-project-automation
Bot
moved this from Review In Progress
to Done
in Pull Request Review
|
@AkihiroSuda: new pull request created: #13711 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@AkihiroSuda: new pull request created: #13712 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@AkihiroSuda: new pull request created: #13713 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@AkihiroSuda: new pull request created: #13714 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@samuelkarp: new pull request created: #13715 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Vagrant 2.4.x bundles an embedded Ruby 3.3.0 runtime that loads the default specification json-2.7.2 during initialization. When installing vagrant-libvirt, RubyGems resolves the newly released fog-json 1.4.0, which requires json (~> 2.19). Because json-2.7.2 is already active in memory when Vagrant starts up, RubyGems raises a Gem::ConflictError.
Pinning fog-json to version 1.2.0 before installing vagrant-libvirt ensures compatible gem resolution against Vagrant's embedded default json specification.
Assisted-by: Antigravity