| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Found UI changes, kicking a new UI QA build |
Sorry, something went wrong.
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Found UI changes, kicking a new UI QA build |
Sorry, something went wrong.
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
UI build: ✔️ |
Sorry, something went wrong.
|
UI build: ✔️ |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 3785 |
Sorry, something went wrong.
|
Found UI changes, kicking a new UI QA build |
Sorry, something went wrong.
|
@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
UI build: ✔️ |
Sorry, something went wrong.
|
SonarCloud Quality Gate failed. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM but really needs testing against the said version of support veeam B&R
Sorry, something went wrong.
|
@harikrishna-patnala should this be fixed in 4.17 branch? |
Sorry, something went wrong.
|
@SadiJr Can you please help me test this PR with the Veeam version v11.0.1.1261 ? Though this version is not fully supported from a fresh install, it will still work with older version and even after upgrading to the v11.0.1.1261. You can also try any test environment if you have by upgrading it to this version v11.0.1.1261. Thanks in advance. |
Sorry, something went wrong.
|
@shwstppr a Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 3943 |
Sorry, something went wrong.
|
@rohityadavcloud a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-4663)
|
Sorry, something went wrong.
|
Test failures are unrelated, merging based on approvals and testing |
Sorry, something went wrong.
|
@harikrishna-patnala sorry for the delay in answer. I tested in my lab with the Veeam build 11.0.1.1261 P20211211, comparing with the main commit bca6076, and the error reported in issue #6465 is fixed. About issue #6554, I cannot reproduce the second example; can you please inform your version of Windows and PowerShell? |
Sorry, something went wrong.
Fixes issue apache#6465 where listing backup restore points are failing with Veeam version v11.0.1.1261. Though this version is not fully supported for backup and recovery, existing backups, restore points for the VMs can continue to work with the Veeam version v11.0.1.1261. I've created a separate ticket here to fully support the version apache#6554
| Back | FazBrowse Home | New Git URL |
Description
This PR fixes the issue #6465 where listing backup restore points are failing with Veeam version v11.0.1.1261.
Though this version is not fully supported for backup and recovery, existing backups, restore points for the VMs can continue to work with the Veeam version v11.0.1.1261. I've created a separate ticket here to fully support the version #6554
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?