Connection timed out only after CopyCommand - SSVM to ESXI

2019-09-09 Thread cristian.c
Hello, I'm experiencing a very strange issue, when I try to deploy the first VM, and the CopyCommand is executed I get : Connection timed out on SSVM side, but only after this task is executed, If I restart the secondary storage and ping,telnet,ssh on esxi everything works fine.

Re: 4.13 rbd snapshot delete failed

2019-09-09 Thread Gabriel Beims Bräscher
Thanks for the feedback Andrija and Andrei. I have opened issue #3590 for the snapshot rollback issue raised by Andrija. I will be investigating both issues: - RBD snapshot Revert #3590 ( https://github.com/apache/cloudstack/issues/3590) - RBD snapshot deletion #3586 (

Re: User Data does not work

2019-09-09 Thread Fariborz Navidan
I mean before restarting network. I have deleted and re-created VR but it returns empty response when VM requests latest user-data On Mon, Sep 9, 2019 at 12:12 PM Riepl, Gregor (SWISS TXT) < gregor.ri...@swisstxt.ch> wrote: > > > When I pass base64 encoded user data to deployvirtualmachine Api,

Re: 4.13 rbd snapshot delete failed

2019-09-09 Thread Andrei Mikhailovsky
A quick feedback from my side. I've never had a properly working delete snapshot with ceph. Every week or so I have to manually delete all ceph snapshots. However, the NFS secondary storage snapshots are deleted just fine. I've been using CloudStack for 5+ years and it was always the case. I am

Re: Creating Windows Server 2019 templates with cloudbase init

2019-09-09 Thread simon.voelker
Hi, we are using cloudplatform 4.11 which is based on cloudstack 4.10. Regards Simon Völker Fraunhofer-Gesellschaft e.V. Schloss Birlinghoven 53754 Sankt Augustin Telefon: +49 2241 14-2311 E-mail: simon.voel...@zv.fraunhofer.de Am 06.09.2019 um 15:34

Re: User Data does not work

2019-09-09 Thread Riepl, Gregor (SWISS TXT)
> When I pass base64 encoded user data to deployvirtualmachine Api, VR > returns empty script upon calling http://VR_IP/latest/user-data from > within > the VM. ACS version is 4.12.0.0. It was working before. I've tried > restarting network. What do you mean exactly, when you say "It was working