Hi Suresh,
I was able to reproduce the error with "Unable to add the external cluster"
when you create the zone, for some reasons the "vSwitch" labels are not saved
for all the traffic type interface/s (in wizard). This is why adding a
cluster, fails.
If you close the wizard and you
Hi Cristian,
Have you noticed the same issue as this:
https://github.com/apache/cloudstack/issues/5732 (this issue is already fixed,
and will be available in 4.16.1). If not, you can log a ticket. Thanks.
Regards,
Suresh
On 19/01/22, 12:48 PM, "Suresh Anaparti" wrote:
Hi Cristian,
Hi Cristian,
Thanks for the update. Can you log a ticket (with the UI problem you noticed)
here: https://github.com/apache/cloudstack/issues.
Regards,
Suresh
On 19/01/22, 12:40 PM, "cristian.c@istream.today"
wrote:
Hi Suresh,
I think you can ignore this, I removed the zone from
Hi Suresh,
I think you can ignore this, I removed the zone from UI and added again and
works fine... btw, at the step where you can add multiple physical networks,
if I add more than 1 there is no way to click on "next button" is not working,
tired multiple times. ( I had to add after I
Hi Cristian,
It seems server discoverer couldn't detect the hosts on the cluster in VMware
DC. Can you check the management port group in the hosts is same as in the
global setting 'vmware.management.portgroup', and traffic label configured in
the zone is in sync with the virtual switch on the
Hi Suresh,
I just tested via API, same error, but something is strange in the log:
2022-01-18 08:44:21,900 INFO [c.c.h.v.u.VmwareContext]
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) New
VmwareContext object, current outstanding count: 14
2022-01-18
Hi Cristian,
I'm not sure if this is a bug. Have you tried with api/cmk?
Can you share the complete log of zone creation. If possible, please create a
ticket with details here: https://github.com/apache/cloudstack/issues.
Regards,
Suresh
On 18/01/22, 2:41 PM, "cristian.c@istream.today"
