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

Veeam Compatibility issue #8461

Closed
omurozlu opened this issue Jan 8, 2024 · 13 comments · Fixed by #8241
Closed

Veeam Compatibility issue #8461

omurozlu opened this issue Jan 8, 2024 · 13 comments · Fixed by #8241

Comments

@omurozlu
Copy link

omurozlu commented Jan 8, 2024

ISSUE TYPE
  • Bug Report
COMPONENT NAME

Veeam B&R v12.0 Plugin

CLOUDSTACK VERSION

4.18.0.1


##### CONFIGURATION

##### OS / ENVIRONMENT

##### SUMMARY
We are trying connect Veeam B&R and getting the below error message. When will Veeam B&R 12 API be available?  
Error message we got;
"Request failed. (530) Veeam B&R API call unauthorized, please ask your administrator to fix integration issues."

##### EXPECTED RESULTS
We want to use Veeam B&R 12 
@weizhouapache
Copy link
Member

@omurozlu
please keep an eye on #8241

@omurozlu
Copy link
Author

omurozlu commented Jan 8, 2024

@weizhouapache
I cannot see this configuration in the backup.plugin.veeam.version UI section.

Am I looking for something in the wrong place?

Screenshot 2024-01-08 at 15 51 39

@weizhouapache
Copy link
Member

@weizhouapache I cannot see this configuration in the backup.plugin.veeam.version UI section.

Am I looking for something in the wrong place?

Screenshot 2024-01-08 at 15 51 39

@omurozlu
The PR #8241 is not merged yet. It is still in testing

@omurozlu
Copy link
Author

omurozlu commented Jan 8, 2024

@weizhouapache ow sorry ty for answer

@weizhouapache
Copy link
Member

Fixed via #8241 and #8570

@omurozlu
Copy link
Author

omurozlu commented Feb 6, 2024

same error cloudstack v.19.0.0

@weizhouapache
Copy link
Member

weizhouapache commented Feb 6, 2024

same error cloudstack v.19.0.0

@omurozlu
4.19.0.0 does not have the fix.
Please wait for 4.18.2.0 or 4.19.0.0
You can build the packages from source code of 4.18/4.19 branch as well

@omurozlu
Copy link
Author

omurozlu commented Feb 6, 2024

I probably thought wrong
Screenshot 2024-02-07 at 01 56 06
I thought it was fixed

@weizhouapache
Copy link
Member

weizhouapache commented Feb 6, 2024

I probably thought wrong
Screenshot 2024-02-07 at 01 56 06
I thought it was fixed

That is wrong. @omurozlu
The commit was merged to 4.19 branch after 4.19.0.0

cc @shwstppr

@shwstppr
Copy link
Contributor

shwstppr commented Feb 7, 2024

@weizhouapache @omurozlu Release notes page should be fixed now. It gt merged during RCs and that resulted in showing up in changes.
@omurozlu sorry but for this fix will have to wait for 4.18.2 or 4.19.1

@shwstppr
Copy link
Contributor

shwstppr commented Feb 7, 2024

@omurozlu if you just need to test the compatibility for testing purpose, you may try the latest nightly package,
https://download.cloudstack.org/testing/nightly/

(should be available in the upcoming 2024-02-07 4.19/4.20 packages)

@weizhouapache
Copy link
Member

@omurozlu if you just need to test the compatibility for testing purpose, you may try the latest nightly package, https://download.cloudstack.org/testing/nightly/

(should be available in the upcoming 2024-02-07 4.19/4.20 packages)

thanks @shwstppr !

@omurozlu
as @shwstppr said, you can try the nightly build of 4.19/4.20. The packages of 2024-02-06 contain the bug fix.

@omurozlu
Copy link
Author

omurozlu commented Feb 7, 2024

@omurozlu if you just need to test the compatibility for testing purpose, you may try the latest nightly package, https://download.cloudstack.org/testing/nightly/
(should be available in the upcoming 2024-02-07 4.19/4.20 packages)

thanks @shwstppr !

@omurozlu as @shwstppr said, you can try the nightly build of 4.19/4.20. The packages of 2024-02-06 contain the bug fix.

ty for answer @weizhouapache and @shwstppr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants