Ah, understood. I'll take a closer look at the logs and make sure that I
didn't accidentally miss those lines when I pulled together the logs for this
email chain.
Thanks,
David Mabry
On 1/30/18, 8:34 AM, "Wei ZHOU" wrote:
Hi David,
I encountered the UnsupportAnswer once before,
Following the protocol defined in [1], this is the notice email regarding
the removal of 4.10.0.0-RC* branches from Apache CloudStack official
repository. The Jira ticket for the branches removal is
https://issues.apache.org/jira/browse/CLOUDSTACK-10258. The branches that
will be removed are the fo
Hi David,
I encountered the UnsupportAnswer once before, when I made some changes in
the kvm plugin.
Normally there should be some network configurations in the agent.log but I
do not see it.
-Wei
2018-01-30 15:00 GMT+01:00 David Mabry :
> Hi Wei,
>
> I detached the iso and received the same
Hi Wei,
I detached the iso and received the same error. Just out of curiosity, what
leads you to believe it is something in the vxlan code? I guess at this point,
attaching a remote debugger to the agent in question might be the best way to
get to the bottom of what is going on.
Thanks in ad
The answer should be caused by an exception in the cloudstack agent.
I tried to migrate a vm in our testing env, it is working.
there are some different between our env and yours.
(1) vlan VS vxlan
(2) no ISO VS attached ISO
(3) both of us use ceph and centos7.
I suspect it is caused by codes on
