Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

Conversation

fidencio
Copy link
Member

@fidencio fidencio commented May 7, 2021

This commit forces all the checks and references to point to stable-2.1
branch rather than pointing to main. This will guarantee that changes
done on main won't affect the testing of this specific branch.

Signed-off-by: Fabiano Fidêncio [email protected]

@fidencio fidencio requested a review from a team as a code owner May 7, 2021 13:28
@fidencio
Copy link
Member Author

fidencio commented May 7, 2021

/test

@fidencio fidencio added the wip Work in Progress (PR incomplete - needs more work or rework) label May 7, 2021
@fidencio fidencio force-pushed the wip/refer-to-stable-2.1-branch-on-stable-2.1-branch-content branch from fc23172 to adeda4d Compare May 7, 2021 13:30
@fidencio
Copy link
Member Author

fidencio commented May 7, 2021

/test

@fidencio fidencio force-pushed the wip/refer-to-stable-2.1-branch-on-stable-2.1-branch-content branch from adeda4d to 150e3b0 Compare May 7, 2021 14:44
@fidencio fidencio removed the wip Work in Progress (PR incomplete - needs more work or rework) label May 7, 2021
@fidencio
Copy link
Member Author

fidencio commented May 7, 2021

/test

@fidencio
Copy link
Member Author

fidencio commented May 7, 2021

/test-fedora

Copy link
Member

@c3d c3d left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

It looks like this is not documented in the release process https://github.com/kata-containers/kata-containers/blob/main/docs/Release-Process.md. Would it make sense to add it there?

@fidencio
Copy link
Member Author

Looks good to me.

It looks like this is not documented in the release process https://github.com/kata-containers/kata-containers/blob/main/docs/Release-Process.md. Would it make sense to add it there?

It'd make sense to, somehow, automate it, in the same way we did for the kata-deploy versions.
I'll take care of opening an issue and work on that as time allows. Thanks for the suggestion!

Copy link

@cmaf cmaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fidencio nit: extra slash in readme

README.md Outdated
@@ -160,7 +159,7 @@ You need to install the following to run Kata Containers tests:
- [golang](https://golang.org/dl)

To view the versions of go known to work, see the `golang` entry in the
[versions database](https://github.com/kata-containers/kata-containers/blob/main/versions.yaml).
[versions database](https://github.com/kata-containers/kata-containers/blob/stable-2.1//versions.yaml).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fidencio there is an extra forward slash in this line

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, fixed!

@fidencio fidencio force-pushed the wip/refer-to-stable-2.1-branch-on-stable-2.1-branch-content branch from 150e3b0 to cb01516 Compare May 10, 2021 19:24
@fidencio
Copy link
Member Author

/test

1 similar comment
@fidencio
Copy link
Member Author

/test

@snir911
Copy link
Member

snir911 commented May 11, 2021

@fidencio, thanks, why does this last merge commit is needed?

As we still didn't get CRI-O unit tests to run against shimv2, we
removed those from our tree as part 816aee4. However, we left some
documentation behind and that will break the static check.

Fixes: kata-containers#3505

Backport of kata-containers#3506

Signed-off-by: Fabiano Fidêncio <[email protected]>
This commit forces all the checks and references to point to stable-2.1
branch rather than pointing to `main`.  This will guarantee that changes
done on `main` won't affect the testing of this specific branch.

Fixes: kata-containers#3507

Signed-off-by: Fabiano Fidêncio <[email protected]>
@fidencio fidencio force-pushed the wip/refer-to-stable-2.1-branch-on-stable-2.1-branch-content branch from 73f85c4 to f597ebe Compare May 11, 2021 07:19
@fidencio
Copy link
Member Author

@fidencio, thanks, why does this last merge commit is needed?

I must admit I don't understand why GitHub doesn't understand my rebase atop of stable-2.1. I just rebased and pushed again and this is what I see:
Captura de pantalla de 2021-05-11 09-22-35

That's the reason why we ended up with a merge commit.

@fidencio fidencio changed the base branch from main to stable-2.1 May 11, 2021 07:24
@fidencio
Copy link
Member Author

@fidencio, thanks, why does this last merge commit is needed?

I must admit I don't understand why GitHub doesn't understand my rebase atop of stable-2.1. I just rebased and pushed again and this is what I see:
Captura de pantalla de 2021-05-11 09-22-35

That's the reason why we ended up with a merge commit.

D'uh! I opened this PR against main. That's the reason. Let me go and brew more energy.

@fidencio
Copy link
Member Author

/test

Copy link
Member

@snir911 snir911 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fidencio
Copy link
Member Author

fidencio commented May 11, 2021

@wainersm, since we merged the ability to use a cached kernel I've noticed failures like:

09:40:32 I am ubuntu or debian
09:40:32 INFO: Configure chrony file /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/ubuntu_rootfs/etc/chrony/chrony.conf
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/rootfs-builder/rootfs.sh: line 576: rustup: command not found
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/tests /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder
09:40:32 INFO: Build agent
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/src/agent /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder
09:40:32 INFO: checkout failed!
09:40:32 make[1]: Entering directory '/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/src/agent'
09:40:32 /bin/sh: 1: cargo: not found
09:40:32 make[1]: cargo: Command not found
09:40:32 Makefile:153: recipe for target 'clean' failed
09:40:32 make[1]: *** [clean] Error 127
09:40:32 make[1]: Leaving directory '/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/src/agent'
09:40:32 Makefile:87: recipe for target '/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/.ubuntu_rootfs.done' failed
09:40:32 make: *** [/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/.ubuntu_rootfs.done] Error 2
09:40:32 Failed at 44: sudo -E USE_DOCKER="${use_docker}" DISTRO="${distro}" make -e "${target_image}"
09:40:32 Failed at 22: "${cidir}/install_kata_image.sh" "${tag}"

I would like to believe those are not related, I really do, but I think those can be.
Are we short-circuiting somewhere? Are we skipping too early in the process that we don't get things properly installed?

This comes from http://jenkins.katacontainers.io/job/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/251/

@fidencio fidencio added the backport Change from a newer branch / repository label May 11, 2021
@fidencio fidencio closed this May 11, 2021
@fidencio fidencio reopened this May 11, 2021
@fidencio
Copy link
Member Author

/test

@fidencio
Copy link
Member Author

I had to close and re-open because some checks were stuck.

@fidencio
Copy link
Member Author

@wainersm, since we merged the ability to use a cached kernel I've noticed failures like:

09:40:32 I am ubuntu or debian
09:40:32 INFO: Configure chrony file /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/ubuntu_rootfs/etc/chrony/chrony.conf
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/rootfs-builder/rootfs.sh: line 576: rustup: command not found
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/tests /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder
09:40:32 INFO: Build agent
09:40:32 /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/src/agent /tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder
09:40:32 INFO: checkout failed!
09:40:32 make[1]: Entering directory '/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/src/agent'
09:40:32 /bin/sh: 1: cargo: not found
09:40:32 make[1]: cargo: Command not found
09:40:32 Makefile:153: recipe for target 'clean' failed
09:40:32 make[1]: *** [clean] Error 127
09:40:32 make[1]: Leaving directory '/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/src/agent'
09:40:32 Makefile:87: recipe for target '/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/.ubuntu_rootfs.done' failed
09:40:32 make: *** [/tmp/jenkins/workspace/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/go/src/github.com/kata-containers/kata-containers/tools/osbuilder/.ubuntu_rootfs.done] Error 2
09:40:32 Failed at 44: sudo -E USE_DOCKER="${use_docker}" DISTRO="${distro}" make -e "${target_image}"
09:40:32 Failed at 22: "${cidir}/install_kata_image.sh" "${tag}"

I would like to believe those are not related, I really do, but I think those can be.
Are we short-circuiting somewhere? Are we skipping too early in the process that we don't get things properly installed?

This comes from http://jenkins.katacontainers.io/job/kata-containers-tests-ubuntu-PR-cloud-hypeprvisor-k8s-containerd/251/

Still about this, @jcvenegas, @likebreath, have you faced this before?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport Change from a newer branch / repository
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants