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

PowerVS e2e test is failing #1255

Closed
Amulyam24 opened this issue Jun 6, 2023 · 2 comments · Fixed by #1256
Closed

PowerVS e2e test is failing #1255

Amulyam24 opened this issue Jun 6, 2023 · 2 comments · Fixed by #1256
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/bug Categorizes issue or PR as related to a bug.

Comments

@Amulyam24
Copy link
Contributor

Amulyam24 commented Jun 6, 2023

/kind bug
/area provider/ibmcloud

capibmadm powervs network create --name capi-net-jNKWN --service-instance-id d53da3bf-1f4a-42fa-9735-acf16b1a05cd --zone osa21
Creating PowerVS network service-instance-id="d53da3bf-1f4a-42fa-9735-acf16b1a05cd" zone="osa21"
Error: You are not authorized to use this API.

The version of capibmadm - 0.5.0 does not have the fix for the above issue.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. area/provider/ibmcloud Issues or PRs related to ibmcloud provider labels Jun 6, 2023
@Amulyam24
Copy link
Contributor Author

@mkumatag, since the cherry-pick is failing with a conflict, I decided to submit the fix against branch 0.5.
However, in the E2E tests, capibmadm binary is downloaded from GitHub release artifacts. Should we create a new 0.5.x release or consider building capibmadm from main from here on? wdyt?

@mkumatag
Copy link
Member

mkumatag commented Jun 6, 2023

I feel its good to build locally and use that one, otherwise it is going to be challenging always.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/provider/ibmcloud Issues or PRs related to ibmcloud provider kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants