Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

kata-runtime installation fails #322

Closed
RuijingGuo opened this issue Jan 30, 2019 · 8 comments
Closed

kata-runtime installation fails #322

RuijingGuo opened this issue Jan 30, 2019 · 8 comments

Comments

@RuijingGuo
Copy link

worker2:  kata-runtime : Depends: qemu-lite (>= 2.11.0+git.f886228-56) but 2.11.0+git.87517afd72-57 is to be installed
worker2: E: Unable to correct problems, you have held broken packages.

==> worker2: An error occurred. The error will be shown after all tasks complete.

@egernst
Copy link
Member

egernst commented Jan 30, 2019

@bergwolf have you seen this?

@guoruijing what distro are you on?

@RuijingGuo
Copy link
Author

I used Ubuntu 16.04. this is regression.

@grahamwhaley
Copy link
Contributor

That feels very related to the open issue kata-containers/runtime#1184 ?

@jodh-intel
Copy link
Contributor

@guoruijing - thanks for reporting. But we really could benefit from a little more details here:

  • What version of Kata were you using before the install failed?
  • Can we see more complete logs please?

I've just tried installing Kata on 16.04 using https://github.com/kata-containers/documentation/blob/master/install/installing-with-kata-manager.md and it's working fine. Hence, the problem is presumably an update issue.

Another data point and more proof that we need to implement kata-containers/ci#10 asap though.

@RuijingGuo
Copy link
Author

  1. I use vagrant box "ceph/ubuntu-xenial"
  2. vagrant@worker1:~$ cat /etc/issue
    Ubuntu 16.04 LTS \n \l
  3. run the following commands with fresh OS by vagrant:
    sudo sh -c "echo 'deb http://download.opensuse.org/repositories/home:/katacontainers:/release/xUbuntu_$(lsb_release -rs)/ /' > /etc/apt/sources.list.d/kata-containers.list"
    curl -sL http://download.opensuse.org/repositories/home:/katacontainers:/release/xUbuntu_$(lsb_release -rs)/Release.key | sudo apt-key add -
    sudo -E apt-get update
    sudo -E apt-get -y install kata-runtime kata-proxy kata-shim

log:
vagrant@worker1:~$ sudo -E apt-get -y install kata-runtime kata-proxy kata-shim
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
kata-runtime : Depends: qemu-lite (>= 2.11.0+git.f886228-56) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

@RuijingGuo
Copy link
Author

the package came from http://download.opensuse.org/repositories/home:/katacontainers:/release/xUbuntu_16.04/

kata-runtime_1.4.0+git.21f0059-55_amd64.deb
kata-proxy_1.4.0+git.e1856c2-40_amd64.deb
qemu-lite_2.11.0+git.87517afd72-57_amd64.deb

@bergwolf
Copy link
Member

It seems the 1.5.0 release artifacts didn't make it to the apt repo (http://download.opensuse.org/repositories/home:/katacontainers:/release/xUbuntu_16.04/) although obs reported that the build succeeded
https://build.opensuse.org/project/show/home:katacontainers:releases:x86_64:master

Well, there is a different repo: http://download.opensuse.org/repositories/home:/katacontainers:/releases:/x86_64:/master/xUbuntu_16.04/

Note that it is releases instead of release in the url.

I remember there were discussion about releases vs. release before. Which one did we decide to use? cc @marcov

@guoruijing Please use http://download.opensuse.org/repositories/home:/katacontainers:/releases:/x86_64:/master/xUbuntu_16.04/ as a workaround for now.

@marcov
Copy link
Contributor

marcov commented Jan 31, 2019

Hi, the problem here is that, in the release project, {runtime, shim, proxy} fail to build for Ubuntu 16.04. We had the same in use in releases:x86_64:master, and it was fixed by setting up the project config so that a more recent GCC version was picked when building packages.

In the future, to avoid these kind of situations, new releases should first be tested in temporary project branches on OBS, then submitted to the official OBS project and finally accepted / rejected for merge by reviewers. That's what we do with all the openSUSE packages.

I remember there were discussion about releases vs. release before. Which one did we decide to use? cc @marcov

It's discussed here. If there isn't a strong reason to keep release around, we should nuke it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants