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

CAPM3RELEASEBRANCH: unbound variable when running e2e locally #915

Closed
mboukhalfa opened this issue Mar 31, 2023 · 7 comments
Closed

CAPM3RELEASEBRANCH: unbound variable when running e2e locally #915

mboukhalfa opened this issue Mar 31, 2023 · 7 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@mboukhalfa
Copy link
Member

What steps did you take and what happened:
After cloning capm3 and running make test-e2e the test failed in the following line

source "${M3_DEV_ENV_PATH}/lib/releases.sh"
with :

+ source /opt/metal3-dev-env/metal3-dev-env/lib/releases.sh                                              
++ CAPM3RELEASEPATH='{https://api.github.com/repos/metal3-io/cluster-api-provider-metal3/releases}'      
++ CAPIRELEASEPATH='{https://api.github.com/repos/kubernetes-sigs/cluster-api/releases}'                 
++ BMORELEASEPATH='{https://api.github.com/repos/metal3-io/baremetal-operator/releases}'                 
/opt/metal3-dev-env/metal3-dev-env/lib/releases.sh: line 52: CAPM3RELEASEBRANCH: unbound variable        
make: *** [Makefile:135: test-e2e] Error 1   

What did you expect to happen:
run e2e tests

/kind bug

@metal3-io-bot metal3-io-bot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Mar 31, 2023
@Rozzii
Copy link
Member

Rozzii commented Apr 26, 2023

/triage accepted
/help

@metal3-io-bot
Copy link
Contributor

@Rozzii:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/triage accepted
/help

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.

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Apr 26, 2023
@Rozzii
Copy link
Member

Rozzii commented Jun 7, 2023

/cc @mboukhalfa wasn't this fixed already? If so , please close this.

@mboukhalfa
Copy link
Member Author

mboukhalfa commented Jun 12, 2023

No it is not fixed yet

@Sunnatillo
Copy link
Member

Fixed in #1079

@Sunnatillo
Copy link
Member

/close

@metal3-io-bot
Copy link
Contributor

@Sunnatillo: Closing this issue.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

4 participants