Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/827
Closing this PR
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so,
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/827
@yvsubhash Sorry I still disagree with it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/827
@ustcweizhou Do you still have some queries on it?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/827
@ustcweizhou By stopping the usage server, we can fix the records and
continue in the next run. If we simply skip we wont come to know abt the
records with errors.
---
If your project is set
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/827
@yvsubhash yes, we will miss some records if we skip the exception, but we
will miss all others records if we stop the usage server. For me, it is
important that usage server will still be ru
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/827
@ustcweizhou In case we continue with usage generation, we may miss out
some of the records which actually resulted in exception and would in turn lead
to wrong usage numbers. stopping after t
Github user ustcweizhou commented on the issue:
https://github.com/apache/cloudstack/pull/827
@yvsubhash Sorry, I disagree with you. The usage server should not stop
even an exception is raised.
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user yvsubhash commented on the issue:
https://github.com/apache/cloudstack/pull/827
@rodrigo93
Exception in this part of code should stop further usage generation.
Catching it here is suppressing the exception. The fix is tested manually by
simulating the scenario
@rh
Github user bvbharatk commented on the issue:
https://github.com/apache/cloudstack/pull/827
### ACS CI BVT Run
**Sumarry:**
Build Number 176
Hypervisor xenserver
NetworkType Advanced
Passed=73
Failed=0
Skipped=3
_Link to logs Folder (search by
Github user bvbharatk commented on the issue:
https://github.com/apache/cloudstack/pull/827
### ACS CI BVT Run
**Sumarry:**
Build Number 123
Hypervisor xenserver
NetworkType Advanced
Passed=73
Failed=0
Skipped=3
_Link to logs Folder (search by
10 matches
Mail list logo
