Considering adding centos 7 and rhel 7 while at it.
Erik
17. juli 2014 00:32 skrev Marcus shadow...@gmail.com følgende:
Yes, thats it. I have no idea how these mappings are created, but we need
to ensure that both upgrades and new installs work
On Wed, Jul 16, 2014 at 3:25 PM, Amogh Vasekar
On Wed, Jul 16, 2014 at 10:57 PM, Alena Prokharchyk
alena.prokharc...@citrix.com wrote:
822b38761f1655ef3d5d3648985a197f5c2c1262
is in
--
Daan
Marcus, Amogh, WHat is the work to do and the ETA? As I read your
mail, it seems we are not going to revert but I have no idea on what a
forward fix would be. Just adding mappings to KVMGuestOsMapper?
@Marcus: is this regression? As in do I agree with you making this a
blocker. You seem to imply
Yes, it's a regression. The impact is that upgraders to 4.4 may have
existing VMs that don't boot when rebooted, or templates that won't work,
because the virtual hardware is changed and not what was expected.
On Thu, Jul 17, 2014 at 1:56 AM, Daan Hoogland daan.hoogl...@gmail.com
wrote:
On Thu, Jul 3, 2014 at 1:41 AM, Marcus shadow...@gmail.com wrote:
I tested this release with
cherry-picking 2ec7359b4eb501b0d9e80ed87af7a54938e9d505 from 4.4-forward.
I have cherry-picked and pushed. I will address the last remaining
issue by editting the pom.xml from build_asf.sh and roll out
Daan, during 4.4 testing, I found the following regression bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-7118
Unable to expunge vms in error state
There is a workaround for it - I¹ve mentioned it in the bug - yet ideally
I would prefer the fix to be cherry-picked from 4.4-forward:
I have another big issue to report with 4.4 in testing these artifacts. I
register a CentOS 6.5 template, and launch VMs for it on KVM, and the
disks/nics are not virtio.
It looks like it is due to the following commit, which changes how the KVM
agent determines if a template is PV enabled. The
Hi,
It is probably due to missing mapping in guest_os_hypervisor table. I had
created default entries for KVM using :
http://bit.ly/1rrML8n
I can add the missing mapping to it.
Thanks,
Amogh
On 7/16/14 2:08 PM, Marcus shadow...@gmail.com wrote:
I have another big issue to report with 4.4 in
Tomasz,
As I understand the issue this is what happens:
The user stops the vm from the UI
The MS sends the stop command to the machine
The machine stops and takes a long time for it
The MS reschedules the stop
Then machine stops
the user starts the machine
the MS get by stopping the machine
Did
Hello,
The user does not receive confirmation of the operation.
From the point of view of user input it looks like the machine itself
stopped.
As you can see in the logs, the ACS explicitly sends stop command, as if
they press the Stop button from the GUI, so it is aware of the action from
the
Our beloved VP pointed out that there has not come a vote conclusion yet:
The 4.4.0 vote has resulted in a rejection of the present release
candidate due to -1 of Marcus and no active voting since.
there are three issues pending from this vote thread:
- CLOUDSTACK-6036 (Tomasz)
- unable to add a
Hello,
We are waiting for the patch with longingly.
Error associated with self-closing of machines causes very serious
complications, both from the technical (users need to wait for 10 minutes
and check if the machine is not closed automatically) as well as the
business side (this problem does
Hugo
My understanding is only binding votes are counted. Non-binding votes are
informational
-Original Message-
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Wednesday, July 02, 2014 11:50 PM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Apache
Pierre-Luc,
I think the old proces was for the citrix guys to build and upload a
version. This is not what I would prefer. We can do a build on the
commit-id or tag in jenkins.bac.o and preserve the target. in there or
copy them to a mirror.
Any thoughts, anybody?
On Fri, Jul 4, 2014 at 3:05 PM,
In principle, yes. You descibed earlier that the -SNAPSHOT that is
your problem is in 6.2.0-SNAPSHOT, the version for the xapi jar, not a
4.4.0-SNAPSHOT detailing cloudstacks version. The code for setting
this version hasn't changed so I suspect that 4.3.0 has in the top
level pom 4.3.0-SNAPSHOT.
Does 4.4.0 will have new System VM templates? if so what will be URL's for
those new system VM ?
I'll update Release notes because for now the URL I used for RN of 4.4.0 is
from jenkins (
Ove, you are talking of the xapi version(?), strange I didn't catch
that one. I did a test compile and then redid my dist creation. I'll
look into this.
If it didn't compile it is not nitpicking!
Daan
On Thu, Jul 3, 2014 at 6:06 AM, Ove Ewerlid ove.ewer...@oracle.com wrote:
-1
The top level
Thanks for clarifying, Hugo!
On Thursday, July 3, 2014, Hugo Trippaers h...@trippaers.nl wrote:
Hey Mike,
That is technically not the way this vote works. Release votes a a “Lazy
Majority” vote. This means that the vote requires at least 3 binding +1
votes and more +1 votes than -1 votes.
Ove, any target specific? mvn clean test works.
On Thu, Jul 3, 2014 at 6:06 AM, Ove Ewerlid ove.ewer...@oracle.com wrote:
-1
The top level pom.xml still contains a -SNAPSHOT suffix.
https://github.com/apache/cloudstack/blob/4.4-RC20140702T2107/pom.xml
line 63.
Removing the -SNAPSHOT
On 07/03/2014 10:16 PM, Daan Hoogland wrote:
Ove, any target specific? mvn clean test works.
No target specifics AFAIK. Below is a short script that repeats the issue.
For the example run below a Fedora 20 system was used, the same error is
seen on OEL65 (Oracle variant of RHEL65).
This
Hey Mike,
That is technically not the way this vote works. Release votes a a “Lazy
Majority” vote. This means that the vote requires at least 3 binding +1 votes
and more +1 votes than -1 votes. For the exact working see paragraphs 3.4.4
and 3.2.2 of the Apache CloudStack bylaws.
Cheers,
Hi All,
I've created a 4.4.0 release, with the following artifacts up for a vote:
Git Branch and Commit SH:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.4-RC20140702T2107
Commit: 379387961bd05d1f84fe2e9a1997e9ecdceef91a
List of changes:
-1 because CLOUDSTACK-6036
2014-07-02 22:18 GMT+02:00 Daan Hoogland daan.hoogl...@gmail.com:
Hi All,
I've created a 4.4.0 release, with the following artifacts up for a vote:
Git Branch and Commit SH:
-1
I'm unable to add a KVM host. It seems to be related to changes in the
SshCmdHelper. The mgmt server issues an ssh check to see of the host has
kvm modules installed, which it shows it does, but there is a null pointer
in the SshCmdHelper and it doesn't interpret the result correctly. I saw
We have at least one binding -1, so this VOTE won't pass.
We should continue to test on this RC, though, as Marcus mentioned, in an
effort to reduce RC spin.
We also shouldn't spin up a new RC until next week as many in the U.S. are
on a long weekend starting tomorrow.
On Wednesday, July 2,
On Wed, Jul 2, 2014 at 8:13 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
We have at least one binding -1, so this VOTE won't pass.
You can't veto a release. The vote could still pass, though I agree
this one is unlikely to.
--David
Maybe you could clarify that for me, David. I thought if we had even one -1
binding VOTE that the VOTE failed (and therefore the release candidate
would not become the formal release). What is the distinction between
vetoing such a VOTE and the release itself?
Thanks
On Wed, Jul 2, 2014 at 9:06
-1
The top level pom.xml still contains a -SNAPSHOT suffix.
https://github.com/apache/cloudstack/blob/4.4-RC20140702T2107/pom.xml
line 63.
Removing the -SNAPSHOT suffix allows compilation.
/Ove (Nitpicking)
On 07/02/2014 10:18 PM, Daan Hoogland wrote:
Hi All,
I've created a 4.4.0
28 matches
Mail list logo
