Re: failed to start CS 4.5

Issue resolved. After CS 4.3.2 was removed (yum erase cloudstack-*) i removed all /usr/share/cloudstack* directories - that solve issue with CS start. There was symlink loop /usr/share/cloudstack-bridge/webapps/webapps/webapps Upload the complete log that will help us to debug and tell reas

Build failed in Jenkins: build-master-slowbuild #1097

See -- [...truncated 298 lines...] [INFO] --- cobertura-maven-plugin:2.6:cobertura (default-cli) @ checkstyle --- [INFO]

Replace systemvm template 4.3.0 with recent one during ACS upgrade

Hi guys, I'm wondering, since I'm upgrading ACS 4.3.0 with original systemvm (from ~ 24.05.2014), to ACS 4.3.2 - am I required to also register new systemVM template (i.e. from UI like when you upgrade from 4.3 to 4.4..) - or should I just upgrade ACS and ACS would somehow update systemVM template

Build failed in Jenkins: build-master-slowbuild #1098

See -- [...truncated 4 lines...] Fetching changes from the remote Git repository > /usr/bin/git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=4

Re: [HELP] VR sometimes fail to start

Tried the proposed solution - but it still don't work - BTW my qemu is 0.12.x - from CentOS 6.4... When I manually start the script with all parameters, it simply hangs, no output at all, until ctrl + c BTW this is with now upgraded ACS to 4.3.2... :( On 12 March 2015 at 09:24, Andrija Panic w

Re: Replace systemvm template 4.3.0 with recent one during ACS upgrade

It should pull the highest/last entry with the name 4.3 when redeploying the routers, but I'm not sure if it will detect that the router needs upgrade without a minor version change. I imagine it would fetch the highest entry, see that the template id doesn't exist, and install it, but you may want

Re: [HELP] VR sometimes fail to start

People are mostly using upgraded 'virt' repos. On Sat, Mar 14, 2015 at 8:58 AM, Marcus wrote: > Oh, this is an unsupported version. should be using libvirt 0.9.4+ and > Qemu 1.0+ per the install docs. > > On Sat, Mar 14, 2015 at 8:56 AM, Andrija Panic > wrote: >> Tried the proposed solution - b

Re: [HELP] VR sometimes fail to start

Oh, this is an unsupported version. should be using libvirt 0.9.4+ and Qemu 1.0+ per the install docs. On Sat, Mar 14, 2015 at 8:56 AM, Andrija Panic wrote: > Tried the proposed solution - but it still don't work - BTW my qemu is > 0.12.x - from CentOS 6.4... > > When I manually start the script

Re: [HELP] VR sometimes fail to start

Marcus - QEMU is 0.12.x (CentOS 6.4) but libvirt is compiled 1.2.3 On 14 March 2015 at 16:58, Marcus wrote: > Oh, this is an unsupported version. should be using libvirt 0.9.4+ and > Qemu 1.0+ per the install docs. > > On Sat, Mar 14, 2015 at 8:56 AM, Andrija Panic > wrote: > > Tried the propo

Re: [HELP] VR sometimes fail to start

Yeah, I don't remember all of the discussion around the minimum version and why, but each libvirt and qemu has such different behavior (not all good), that we decided to target a minimum regardless of what was supplied by the distros. It's just too hard to support them all with their differing beha

Build failed in Jenkins: build-master-slowbuild #1099

See -- [...truncated 4 lines...] Fetching changes from the remote Git repository > /usr/bin/git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/cloudstack.git # timeout=4

Re: [HELP] VR sometimes fail to start

Yes I understadn that - more of a problem, qemu-img from CentOS 6.5 doesnt work snapshots (redhat removed -S flag, etc.), then we need RBD support (for CEPH), which RH does not support in normal RHEL/CentOS, etc. Next cloud deployement - dump the the RHEL/CentOS, and go with Ubuntu 14.04, which d

Re: [HELP] VR sometimes fail to start

I think I located the problem, sort of: it seems like ACS agent is deleting route to 168.254.0.0 - so after the patchviasocket - agent can not connect to private interface on VM (169.254.x.x) if I try to provision VPC - it waits, and waits, and waits... until I add route manually on the particual

Re: [HELP] VR sometimes fail to start

Args so this was the reason definitively: bash -c ip route - does not work, and then CS agent deletes 169.254.0.0 route completely... why - have no damn clue... I made simple cron, creating route, sleep 30sec, then create route again... - so at least VR creation will be prolonged for max

Build failed in Jenkins: build-master-slowbuild #1100

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on cloudstack-buildslave-centos6-cac (cloudstack-buildslave-centos6) in workspace

ACS 4.3.2 shapeblue/upstream - remote IP not show behide VPC

Hi guys, refreshing old subject with a more details: I just upgrade to ACS 4.3.2 (shapeblue upstream repo) and systemvm also to 4.3.2 (shapeblue with GHOST patch) I still have same problems as with ACS 4.3.0 (comunity repo, comunity systemvm template) PROBLEM: When I do Port Forwarding, or Stat

Build failed in Jenkins: build-master-slowbuild #1101

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on cloudstack-buildslave-centos6-cac (cloudstack-buildslave-centos6) in workspace

Build failed in Jenkins: build-master-slowbuild #1102

See -- Started by timer [EnvInject] - Loading node environment variables. Building remotely on cloudstack-buildslave-centos6-cac (cloudstack-buildslave-centos6) in workspace

Build failed in Jenkins: build-master-slowbuild #1103

See -- [...truncated 5146 lines...] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.03 sec - in com.cloud.network.NetworkModelTest Running com.cloud.network.router.NetworkHe