| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Found Java/XML changes, kicking packaging job |
Sorry, something went wrong.
|
@acs-robot 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 3204 |
Sorry, something went wrong.
PR Coverage Report
|
Sorry, something went wrong.
|
Hi @weizhouapache @Pearl1594 can you please review? |
Sorry, something went wrong.
|
@blueorangutan test centos7 vmware-65u2 |
Sorry, something went wrong.
|
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-65u2) has been kicked to run smoke tests |
Sorry, something went wrong.
|
@weizhouapache I think the error message is very descriptive as it is but will be +1 to point to a single location with all the information - @SadiJr please advise |
Sorry, something went wrong.
|
@blueorangutan test centos7 vmware-65u2 |
Sorry, something went wrong.
|
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-65u2) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian Build Failed (tid-3997) |
Sorry, something went wrong.
|
Found UI changes, kicking a new UI QA build |
Sorry, something went wrong.
|
@weizhouapache @nvazquez thansk for the suggestion. I changed the description of the PR, adding all the links, and adding the link of this PR in the final message. What do you think? |
Sorry, something went wrong.
PR Coverage Report
|
Sorry, something went wrong.
|
@nvazquez 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.
|
@blueorangutan test centos7 vmware-65u2 |
Sorry, something went wrong.
|
@blueorangutan test centos7 vmware-65u2 |
Sorry, something went wrong.
|
@nvazquez a Trillian-Jenkins test job (centos7 mgmt + vmware-65u2) has been kicked to run smoke tests |
Sorry, something went wrong.
|
Trillian test result (tid-4018)
|
Sorry, something went wrong.
|
@SadiJr thanks for the changes in the error message - I was not able to reproduce the issue on main branch using vmware 6.5 + NFS following the steps in the PR description, however changes LGTM |
Sorry, something went wrong.
Done, thanks for the suggestion. |
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.
There was a problem hiding this comment.
code lgtm
Sorry, something went wrong.
|
@weizhouapache 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.
PR Coverage Report
|
Sorry, something went wrong.
|
Packaging result: ✔️ el7 ✔️ el8 ✔️ debian ✔️ suse15. SL-JID 3312 |
Sorry, something went wrong.
* Fix exception, in VMWare 6.5, when trying to detach volume * Address reviews * Address reviews Co-authored-by: SadiJr <sadi@scclouds.com.br>
[VMWare] error when detaching volume (apache#6283)
| Back | FazBrowse Home | New Git URL |
Description
Using the VMWare (version 6.5), when trying to detach a volume, vCenter detaches it successfully; however, ACS throws an exception. It already was reported in VMWare and ACS' communities, but it hasn't been fixed yet. For more information about this error, please check this links ([1], [2], [3]).
To know why ACS tries to check folder content, please check these links ([4], [5]). This error apparently only occurs with datastores that use the NFS protocol and n specific versions of VMWare. Users using VMFS or VMWare versions greater than 6.7 have not reported this error. If the operation performed is a volume detach, it was successful. If you want to know why this error occurs in VMWare, please contact VMWare's technical support.
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
How Has This Been Tested?
It was tested in a local lab: