Skip to content
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

unable to run the tests scaffold for the projects without the kb bin in /usr/local/kubebuilder/bin #1599

Closed
camilamacedo86 opened this issue Jul 19, 2020 · 7 comments · Fixed by #1608
Assignees

Comments

@camilamacedo86
Copy link
Member

camilamacedo86 commented Jul 19, 2020

The following error is faced when the KB is installed from master or its bin be added in another place when the tests are executed via the makefile targets:

  Unexpected error:
      <*fmt.wrapError | 0xc000109ec0>: {
          msg: "failed to start the controlplane. retried 5 times: fork/exec /usr/local/kubebuilder/bin/etcd: no such file or directory",
          err: {
              Op: "fork/exec",
              Path: "/usr/local/kubebuilder/bin/etcd",
              Err: 0x2,
          },
      }
      failed to start the controlplane. retried 5 times: fork/exec /usr/local/kubebuilder/bin/etcd: no such file or directory
  occurred

Root cause explained in: #686 (comment)

@camilamacedo86
Copy link
Member Author

/assign @camilamacedo86

@camilamacedo86
Copy link
Member Author

/reopen

@k8s-ci-robot
Copy link
Contributor

@camilamacedo86: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot reopened this Jul 23, 2020
@camilamacedo86
Copy link
Member Author

An possible solution is to setup the bins as:

OS=$(uname -s | tr '[:upper:]' '[:lower:]')
ARCH=$(uname -m | sed 's/x86_64/amd64/')
curl -fsL "https://storage.googleapis.com/kubebuilder-tools/kubebuilder-tools-1.16.4-${OS}-${ARCH}.tar.gz" -o kubebuilder-tools
tar -zvxf kubebuilder-tools
sudo mv kubebuilder/ /usr/local/kubebuilder

@georgettica
Copy link
Contributor

if these files are required, integrating into brew is also helpful

@camilamacedo86
Copy link
Member Author

Hi @georgettica,

If you run brew install kubebuilder it will install the binaries because they are shipped with Kubebuilder currently. The goal here is in the long term we do not need to ship them.

It was solved for v3+. See: #1626

So, when we are able to removed the support for v2 and removed it from the projects as was done for v1 it will be solved.

@georgettica
Copy link
Contributor

@camilamacedo86 I installed kubebuilder and they were not installed

georgettica added a commit to georgettica/route-monitor-operator that referenced this issue Sep 7, 2020
as this tool requies etcd in a specific location
and the error was not solved (see kubernetes-sigs/kubebuilder#1599)

commenting out and leaving like that until fixed
georgettica added a commit to georgettica/route-monitor-operator that referenced this issue Sep 8, 2020
now sample resembles what needs to run on the cluster

also:
- shorten service name so deploy will work
- fix(suite_test): remove test
	as this tool requies etcd in a specific location
	and the error was not solved (see kubernetes-sigs/kubebuilder#1599)
	commenting out and leaving like that until fixed
- fix(crd): add crd
	somehow this was not added before
openshift-merge-robot pushed a commit to openshift/route-monitor-operator that referenced this issue Sep 8, 2020
now sample resembles what needs to run on the cluster

also:
- shorten service name so deploy will work
- fix(suite_test): remove test
	as this tool requies etcd in a specific location
	and the error was not solved (see kubernetes-sigs/kubebuilder#1599)
	commenting out and leaving like that until fixed
- fix(crd): add crd
	somehow this was not added before
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants