JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1739835693
@blueorangutan package
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1671859990
@blueorangutan package
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1635811868
The errors shown do not seem related to this PR:
tests `test_01_migrate_VM_and_root_volume` and
`test_02_migrate_VM_with_two_data_disks` had this exception:
```
Exception
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1634209643
@DaanHoogland the errors shown in the xen env do not seam related to this
PR, could we retry with kvm?
--
This is an automated message from the Apache Git Service.
To respond to
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1623566059
@DaanHoogland the errors shown in the marvin logs do not seem to be related
to the changes in my PR. All the ones I checked had "HTTP connection refused"
errors.
--
This is an
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1589135572
@blueorangutan package
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1568781634
> > Sounds interesting - as long as we keep the original behaviour a default
(backward compatibility), I think this would be an interesting feature. It does
add complexity (as with
JoaoJandre commented on PR #7489:
URL: https://github.com/apache/cloudstack/pull/7489#issuecomment-1538269766
> @JoaoJandre could a global setting and its use in the deployment planner
be enough to make the deployment and related lifecycles are strictly or
non-strictly allowed the by
