New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't use "kexec" as both a package name and a variable name #9771
Conversation
(Also, get rid of some uses of os/exec in places where we're also using kexec.)
@openshift/networking can someone take a look? easy fix |
LGTM |
[merge] |
re[merge] |
Seems like a transient error... error: running '/bin/sh -c curl -L -o /etc/yum.repos.d/origin-next-epel-7.repo https://copr.fedoraproject.org/coprs/maxamillion/origin-next/repo/epel-7/maxamillion-origin-next-epel-7.repo && INSTALL_PKGS="openvswitch" && yum install -y $INSTALL_PKGS && rpm -V $INSTALL_PKGS && yum clean all && chmod +x /usr/local/bin/*' failed with exit code 1 re[merge] |
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7203/ flaked due to #9775, [merge] |
re[merge] |
Failure was:
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7306/) (Image: devenv-rhel7_4715) |
re[merge] -- that was a bad Jenkins job config |
Evaluated for origin merge up to a50b49b |
leftover nit from #9520, requested by @liggitt
(we were previously using os/exec in a few places as well, but the interface returned by kexec.New() has the same API as os/exec, so renaming that variable to "exec" makes the os/exec import unnecessary/conflicting)