Certainly the behavior is not robust. On 5/29/13 10:35 AM, "Musayev, Ilya" <imusa...@webmd.net> wrote:
>Before I file this as a bug, I would like to understand if this is a bug >or by-design. > >Summary: >Many times, the initial zone deployment may fail because incorrect values >were used during configuration process. The CS management server will go >in cycles over and over again, attempting to use improper values, fail >and retry. If left uninterrupted, this repeat cycle can go on forever. > >Specific issue was witnessed with "ClusteredAgentManager setting public >traffic over vSwitch: null", while technically it should have defaulted >to vSwitch0. >If left uninterrupted, it will create the SSVM VM, fail to find vswitch >null for public traffic, delete storage VM, and repeat this procedure >unlimited times. > >On my attempt to disable Zone first, then pod, the cluster, has not >prevented job execution engine from running. I had to put the primary >storage into maintenance mode. While this approach technically stopped >executions on vSphere vCenter, the SSVM id increased from count of 2, to >count of 33 (once I resolved this issue by defining vSwtich0) - >indicating that job execution still continued. > >By design, when you disable cluster, should job execution stop or pause? >What about Pod and Zone? >
