Skip to content

Vagrantfile.fedora: upgrade Fedora to 38#3835

Closed
AkihiroSuda wants to merge 1 commit intoopencontainers:mainfrom
AkihiroSuda:fedora-38
Closed

Vagrantfile.fedora: upgrade Fedora to 38#3835
AkihiroSuda wants to merge 1 commit intoopencontainers:mainfrom
AkihiroSuda:fedora-38

Conversation

@AkihiroSuda
Copy link
Member

@AkihiroSuda AkihiroSuda commented Apr 21, 2023

No description provided.

@AkihiroSuda
Vagrantfile.fedora: upgrade Fedora to 38
d35b080 
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
@AkihiroSuda AkihiroSuda added area/ci backport/1.1-todo A PR in main branch which needs to be backported to release-1.1 labels Apr 21, 2023
@AkihiroSuda
Copy link
Member Author

AkihiroSuda commented Apr 24, 2023 

Bringing machine 'default' up with 'libvirt' provider...
==> default: Box 'fedora/38-cloud-base' could not be found. Attempting to find and install...
    default: Box Provider: libvirt
    default: Box Version: >= 0
==> default: Loading metadata for box 'fedora/38-cloud-base'
    default: URL: https://vagrantcloud.com/fedora/38-cloud-base
==> default: Adding box 'fedora/38-cloud-base' (v38.20230413.1) for provider: libvirt
    default: Downloading: https://vagrantcloud.com/fedora/boxes/38-cloud-base/versions/38.20230413.1/providers/libvirt.box

An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

HTTP/2 stream 0 was not closed cleanly: PROTOCOL_ERROR (err 1)

@kolyshkin
Copy link
Contributor

kolyshkin commented Apr 26, 2023

This looks like hashicorp/vagrant#12921 (plus a combination of some server-side changes, I guess).

The code in question was added 5 years ago in vagrant 2.1.3 (hashicorp/vagrant@447e58d) , and it was fixed (by hashicorp/vagrant@c7ef689) in vagrant 2.3.1.

Now, apparently we use vagrant 2.2.19 in CI, thus the issue.

kolyshkin added a commit to kolyshkin/runc that referenced this pull request Apr 27, 2023
@kolyshkin
ci/cirrus: use vagrant from hashicorp repo
7ba156a 
A version of vagrant available from the stock repos (2.2.19) is too old
and contains a bug that prevents downloading Fedora 38 image (see [1]).

Use packages from hashicorp repo, which currently has vagrant 2.3.4.
This resolves the problem of downloading the latest Fedora image.

Also, vagrant-libvirt plugin from Ubuntu repos is not working with
vagrant from hashicorp, so switch to using "vagrant plugin install".
The downside it, this takes extra 4 minutes or so in our CI, and I
am not sure how to cache it or speed it up.

[1] opencontainers#3835 (comment)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@AkihiroSuda
Copy link
Member Author

AkihiroSuda commented Apr 27, 2023

kolyshkin added a commit to kolyshkin/runc that referenced this pull request Apr 27, 2023
@kolyshkin
ci/cirrus: use vagrant from hashicorp repo
33b6ec2 
A version of vagrant available from the stock repos (2.2.19) is too old
and contains a bug that prevents downloading Fedora 38 image (see [1]).

Use packages from hashicorp repo, which currently has vagrant 2.3.4.
This resolves the problem of downloading the latest Fedora image.

Also, vagrant-libvirt plugin from Ubuntu repos is not working with
vagrant from hashicorp, so switch to using "vagrant plugin install".
The downside it, this takes extra 4 minutes or so in our CI, and I
am not sure how to cache it or speed it up.

[1] opencontainers#3835 (comment)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
@kolyshkin
Copy link
Contributor

kolyshkin commented Apr 27, 2023

Filed a bug to Ubuntu: https://bugs.launchpad.net/vagrant/+bug/2017828

@kolyshkin kolyshkin removed the backport/1.1-todo A PR in main branch which needs to be backported to release-1.1 label Apr 27, 2023
kolyshkin added a commit to kolyshkin/runc that referenced this pull request May 22, 2023
@kolyshkin
ci/cirrus: use vagrant from hashicorp repo
3f1a57c 
A version of vagrant available from the stock repos (2.2.19) is too old
and contains a bug that prevents downloading Fedora 38 image (see [1]).

Use packages from hashicorp repo, which currently has vagrant 2.3.4.
This resolves the problem of downloading the latest Fedora image.

Also, vagrant-libvirt plugin from Ubuntu repos is not working with
vagrant from hashicorp, so switch to using "vagrant plugin install".
The downside it, this takes extra 4 minutes or so in our CI, and I
am not sure how to cache it or speed it up.

[1] opencontainers#3835 (comment)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
(cherry picked from commit 33b6ec2)
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
kolyshkin added a commit to kolyshkin/runc that referenced this pull request Jun 6, 2023
@kolyshkin
ci/cirrus: use vagrant from hashicorp repo
27b86b4 
A version of vagrant available from the stock repos (2.2.19) is too old
and contains a bug that prevents downloading Fedora 38 image (see [1]).

Use packages from hashicorp repo, which currently has vagrant 2.3.4.
This resolves the problem of downloading the latest Fedora image.

Also, vagrant-libvirt plugin from Ubuntu repos is not working with
vagrant from hashicorp, so switch to using "vagrant plugin install".
The downside it, this takes extra 4 minutes or so in our CI, and I
am not sure how to cache it or speed it up.

[1] opencontainers#3835 (comment)

Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
(cherry picked from commit 33b6ec2)
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

area/ci

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@AkihiroSuda @kolyshkin