cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jayapal Uradi <>
Subject Re: :[VOTE] Apache Cloudstack
Date Mon, 06 Mar 2017 11:22:45 GMT
Created the PR.


On Mar 6, 2017, at 3:58 PM, Rajani Karuturi <<>>

Thanks Wei Zhow. Will ping Jayapal.

~ Rajani

On March 6, 2017 at 3:25 PM, Wei ZHOU (<>)
about ticket:

this seems to be caused by commit 175c8d83b8a628566a4c443db0de587874718c8c

Author: Jayapal <<>>
AuthorDate: Mon Feb 20 18:29:14 2017 +0530
Commit: Jayapal <<>>
CommitDate: Mon Feb 20 18:34:13 2017 +0530

CLOUDSTACK-8871: fixed issue with the xenserver 6.2 ipset nethash
scripts/vm/hypervisor/xenserver/vmops | 25 +++++++++++++++++++------
1 files changed, 19 insertions(+), 6 deletions(-)

Jayapal, could you please have a look ?

2017-03-04 2:41 GMT+01:00 Rajani Karuturi <<>>:
Thanks for the update mike.

@wido, weizhou
Can you take a look at the issue please?

Sent from phone.

On 4 Mar 2017 3:25 a.m., "Tutkowski, Mike" <<>>
-1 (binding)

Per my previous e-mails concerning this issue, here is a ticket I

We should get someone from the networking side of things to investigate.


On 3/3/17, 1:28 AM, "Rohit Yadav" <<>>

-1 (binding)

All, I've found an upgrade blocker. Pre 4.6 users are required to
4.6 systemvmtemplate to proceed with the upgrade otherwise upgrade fails,
and from 4.9 upgrade to 4.10 does no check/enforcement that 4.10 based
systemvmtemplate has been seeded/registered, nor the minimum required
systemvmtemplate version is changed from 4.6.0 to 4.10.0.

After we have merged the strongswan/java8 PR, I had updated the
upgrade docs on how to upgrade the systemvmtemplate here:

Using the above, I've tried to fix these issues here, please review
and merge for RC2:

above fix, the
aim is that users only seed the 4.10 systemvmtemplate before upgrade and
post-upgrade the upgrade paths fix the entries, global setting etc.


From: Tutkowski, Mike <<>>
Sent: 02 March 2017 22:39:08
Subject: Re: :[VOTE] Apache Cloudstack

I rolled back to my master branch at da66b06e7d562393da2e4b52206943
and it works.

It appears something that went into after that commit has broken
It looks like this SHA is about two weeks old and that 43 commits have
into master since it.

On 3/2/17, 7:06 AM, "Tutkowski, Mike" <<>>

According to where the code fails, though, it appears to be a
networking problem. If I set a breakpoint before the failure and change a
variable to say that security groups are not being used, then the VM

I think this is a recently introduced problem because I have
another branch based off of a slightly older version of master and it
fine here.
On Mar 2, 2017, at 6:51 AM, Pierre-Luc Dion <<>>
wrote: > wrote: in a Basic
VMs NFS null?!, Exception: xenbase. xenbase. java:266) xenbase. xenbase. java:266)
(Network-Scavenger-1:ctx- checkResponse( 457) xenbase. xenbase. java:266) checkResponse(
457) xenbase. xenbase. java:266) checkResponse( 457) xenbase. xenbase. java:266)
VM orchestrateStart( orchestrateStart( java:266) dataCenterId::
dispatch( java:266) orchestrateStart( orchestrateStart( artifacts the org/repos/dist/dev/cloudstack/

This e-mail may contain privileged and confidential information which is the property of Accelerite,
a Persistent Systems business. It is intended only for the use of the individual or entity
to which it is addressed. If you are not the intended recipient, you are not authorized to
read, retain, copy, print, distribute or use this message. If you have received this communication
in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent
Systems business does not accept any liability for virus infected mails.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message