The current status is as follows:
The bug board has been cleared.
The reviews needed in 4 have been committed.
We are going to be testing over the weekend, particularly the update cases.
We're hoping the release candidate will be cut by Sunday night.
Will keep everyone posted.
--Alex
[
https://issues.apache.org/jira/browse/CLOUDSTACK-273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su closed CLOUDSTACK-273.
Resolution: Fixed
fixed in 6daf9a94f258fe15472568b2cabf2193e0858096 on 4.0 branch
[
https://issues.apache.org/jira/browse/CLOUDSTACK-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang updated CLOUDSTACK-272:
--
Fix Version/s: 4.1.0
> Delete failure message for network with a VM is not informative
[
https://issues.apache.org/jira/browse/CLOUDSTACK-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chandan Purushothama closed CLOUDSTACK-264.
---
Unable to reproduce this bug on the latest CloudStack Build
Chandan Purushothama created CLOUDSTACK-273:
---
Summary: 2.2.14 to 4.0 Upgrade: XenServer Failed to connect to the
management server after Upgrade due to Null Pointer Exception
Key: CLOUDSTACK-273
URL: htt
[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su closed CLOUDSTACK-267.
Resolution: Fixed
fixed in c8afd816965786441e4b6f855b141d7515f15f6a
> Migratio
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470841#comment-13470841
]
edison su commented on CLOUDSTACK-248:
--
I'll close this bug, please test the late
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su closed CLOUDSTACK-248.
Resolution: Fixed
> After upgrading from CS-3.0.2 to ASF 4.0 the KVM Host ends up in discon
[
https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470836#comment-13470836
]
edison su commented on CLOUDSTACK-263:
--
Regarding to agent.properties upgrade iss
[
https://issues.apache.org/jira/browse/CLOUDSTACK-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su closed CLOUDSTACK-210.
Resolution: Fixed
Fix Version/s: (was: 4.1.0)
4.0.0
fixed by 521b
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7461/#review12204
---
Ship it!
Ship It!
- edison su
On Oct. 5, 2012, 11:18 p.m., Marcus
Hi all,
I've posted a new build (4.0.0.beta6) here:
http://people.apache.org/~chipchilders/cloudstack/4.0/
This code was taken from the 4.0 branch, commit
384c03e42578f17432a483d5828aad64175d9c49.
Please test the build using our release test procedure documented
here:
https://cwiki.apache.org/
David Noland created CLOUDSTACK-272:
---
Summary: Delete failure message for network with a VM is not
informative
Key: CLOUDSTACK-272
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-272
Project:
[
https://issues.apache.org/jira/browse/CLOUDSTACK-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470817#comment-13470817
]
edison su commented on CLOUDSTACK-210:
--
Ok, if we decide to use stock qemu snapsh
We looked at history of this bug, seems there is no need to maintain the
backward compatibility.
Wido added paths.script=/usr/lib64/cloud/common into environment.properties,
which means mgt server or agent should look at scripts from cloud/common
instead of agent.
> -Original Message-
[
https://issues.apache.org/jira/browse/CLOUDSTACK-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers closed CLOUDSTACK-266.
> On initial start of the management server within devcloud:
> java.io.IOException: Ca
[
https://issues.apache.org/jira/browse/CLOUDSTACK-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers resolved CLOUDSTACK-266.
--
Resolution: Invalid
This was my local environment.
> On initial st
[
https://issues.apache.org/jira/browse/CLOUDSTACK-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang resolved CLOUDSTACK-209.
---
Resolution: Fixed
The thread is very messy but the history looks like this.
Wido already
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7459/#review12202
---
Ship it!
Ship It!
- edison su
On Oct. 5, 2012, 10:27 p.m., Marcus
I just closed 259 (and agree that 260 is a dupe). Nice find Edison. Thanks!
On Fri, Oct 5, 2012 at 6:49 PM, Chip Childers wrote:
> Update: Edison put instructions to resolve in the bug. This is a
> devcloud issue, not a code issue.
>
> I'll validate and close both before cutting the next relea
[
https://issues.apache.org/jira/browse/CLOUDSTACK-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chip Childers closed CLOUDSTACK-259.
Closing - This was the correct solution. Nice find Edison.
> NoClassDefFo
Rohit,
I know what happened now on this. Thanks for alerting me to the missing
reviews. I had my bug filter built before the Ready For Review status was
introduced into the Jira workflow so I've missed several of the bugs you've
submitted reviews for. Hence, I didn't spend the time to track
[
https://issues.apache.org/jira/browse/CLOUDSTACK-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang closed CLOUDSTACK-263.
-
Resolution: Invalid
We don't need this if we fix 248 and 209 properly.
> Doc
Your Service Offering (specifically Compute Offering) needs to be
marked "HA". That will cause cloudstack to restart VM's automatically
when they go down or the server they are running on goes down.
See page 116 of the Administration Guide.
You can change the Service Offering of an existing VM. P
Okay. :)
Just a note that consensus building through discussion may be a more
productive way to get things like this resolved. Voting tends to be useful
when the discussion is over and there are clear alternatives that everyone
understands.
Consensus building is our primary tool, voting is just a
[
https://issues.apache.org/jira/browse/CLOUDSTACK-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Trippaers resolved CLOUDSTACK-271.
---
Resolution: Fixed
Confirmed.
Repeated the steps and no errors this time.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470781#comment-13470781
]
Marcus Sorensen commented on CLOUDSTACK-210:
I looked through the code, an
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7461/
---
Review request for cloudstack.
Description
---
Adjusts the check for qemu-i
Hey Ilya,
This is a known issue and it is related to the switch to maven. If you can,
please start using the maven build.
Otherwise use the 4.0 branch, there the ant build is still working.
Cheers,
Hugo
Verstuurd vanaf mijn iPad
Op 5 okt. 2012 om 16:02 heeft "Musayev, Ilya" het volgende
ge
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7099/
---
(Updated Oct. 5, 2012, 11:07 p.m.)
Review request for cloudstack.
Changes
Hey Marcus,
Just checked on RedHat 6.3, --pidfile is present there as well.
Cheers,
Hugo
Verstuurd vanaf mijn iPad
Op 5 okt. 2012 om 15:44 heeft "Marcus Sorensen" het
volgende geschreven:
> I'm going to be bold and submit a patch for this in anticipation that
> "--pidfile" will be found val
Hi All,
I'm launching a new project "CloudSand" which will allow cloud community to
download free OS templates.
The temp homepage will be http://www.cloudsand.com/content
Looking for anyone who is willing to contribute, this is a free project to aid
the CS community.
Thanks
ilya
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@citrix.com]
> Sent: Friday, October 05, 2012 2:21 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [VOTE] how to upgrade CloudStack from 3.0.x to 4.0
>
> We're voting/discussing on better ways to upgrade ACS from 3.0
Would you know how to resolve this issue:
[root@cloud04t-ops-08 4.0.0]# mvn -P deps -rf :cloud-deps
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Apache CloudStack Dependencies 4.1.0-SNAPSHOT
[INFO] --
[
https://issues.apache.org/jira/browse/CLOUDSTACK-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang resolved CLOUDSTACK-264.
---
Resolution: Fixed
> Upgrade from CS-2.2.14 to ASF 4.0 fails in the cloud-setup-encryp
[
https://issues.apache.org/jira/browse/CLOUDSTACK-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su closed CLOUDSTACK-260.
Resolution: Duplicate
The same as bug CLOUDSTACK-259
> NoClassDefFoundError: o
[
https://issues.apache.org/jira/browse/CLOUDSTACK-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edison su resolved CLOUDSTACK-259.
--
Resolution: Fixed
test procedure is updated.
> NoClassDefFoundError - The
Update: Edison put instructions to resolve in the bug. This is a
devcloud issue, not a code issue.
I'll validate and close both before cutting the next release.
- chip
Sent from my iPhone.
On Oct 5, 2012, at 6:24 PM, Alex Huang wrote:
> Chip,
>
> Any luck with testing these two bugs? Thanks.
Thanks for testing!
Edison just told me it's because devCloud is not clean up. So on his deploy it
works when it's the first run. Second run he sees the problems. He's working
on it.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday,
[
https://issues.apache.org/jira/browse/CLOUDSTACK-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang reassigned CLOUDSTACK-264:
-
Assignee: Kelven Yang (was: Rohit Yadav)
> Upgrade from CS-2.2.14 to ASF 4.0 fai
Edison mentioned on IRC that he thought he knew the issue. I didn't
get the details.
I've tried clearing my local maven cache, cutting a new release from
HEAD of 4.0, and various other things. The issue happens every time.
- chip
Sent from my iPhone.
On Oct 5, 2012, at 6:24 PM, Alex Huang wrot
I'm going to be bold and submit a patch for this in anticipation that
"--pidfile" will be found valid for RHEL and Fedora. It can be
modified if anyone objects.
https://reviews.apache.org/r/7460/
On Fri, Oct 5, 2012 at 3:35 PM, Marcus Sorensen wrote:
> I don't have access to RHEL, but I checked
[
https://issues.apache.org/jira/browse/CLOUDSTACK-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470749#comment-13470749
]
edison su commented on CLOUDSTACK-259:
--
It's due to old environment source code d
[
https://issues.apache.org/jira/browse/CLOUDSTACK-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang resolved CLOUDSTACK-253.
---
Resolution: Fixed
Should be working now even with the latest from Jessica.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang resolved CLOUDSTACK-269.
---
Resolution: Fixed
Should be working now even with the latest from Jessica.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7460/
---
Review request for cloudstack.
Description
---
init script uses 'daemon -p'
I don't have access to RHEL, but I checked the initscripts source rpms
for Fedora 15-18Alpha, and they all have "--pidfile" as an option for
the 'daemon' function in /etc/init.d/functions.
On Thu, Oct 4, 2012 at 10:28 PM, Rohit Yadav wrote:
>
> On 05-Oct-2012, at 2:29 AM, Marcus Sorensen wrote:
[
https://issues.apache.org/jira/browse/CLOUDSTACK-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang reassigned CLOUDSTACK-259:
-
Assignee: edison su
Edison says he now sees this issue. Will investigate.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470733#comment-13470733
]
Marcus Sorensen commented on CLOUDSTACK-267:
See https://reviews.apache.or
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7459/
---
Review request for cloudstack.
Description
---
When a host has maintenance
Chip,
Any luck with testing these two bugs? Thanks.
--Alex
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Friday, October 05, 2012 9:51 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Chip Childers (chip.child...@sungard.com)
> Subject: bugs 259 and 26
[
https://issues.apache.org/jira/browse/CLOUDSTACK-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470723#comment-13470723
]
Hugo Trippaers commented on CLOUDSTACK-264:
---
We changes the names around, so
[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470718#comment-13470718
]
Marcus Sorensen edited comment on CLOUDSTACK-267 at 10/5/12 10:14 PM:
--
[
https://issues.apache.org/jira/browse/CLOUDSTACK-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470720#comment-13470720
]
Alena Prokharchyk commented on CLOUDSTACK-271:
--
The NPE problem is fixed
[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470718#comment-13470718
]
Marcus Sorensen commented on CLOUDSTACK-267:
Ok, the main cause of this se
[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Huang updated CLOUDSTACK-267:
--
Fix Version/s: 4.1.0
> Migration of VM in KVM host is not happening becausec" Unable to
[
https://issues.apache.org/jira/browse/CLOUDSTACK-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Trippaers resolved CLOUDSTACK-268.
---
Resolution: Fixed
Fix Version/s: 4.0.0
Fix committed to master and 4.0
Hi Hugo,
Sorry, wasn't aware of Nicira case when put the fix. Both UI and API has
to be fixed - don't accept vnet parameter in both create/update
physicalNetwork when isolation type is not VLAN. The check should be done
on the services layer before checkGuestVnetsConflicts() method is even
called.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7168/#review12200
---
The problem was fixed with d5b86d8149454f9cc174cd6a29d3fe2603a7dd93 i
[
https://issues.apache.org/jira/browse/CLOUDSTACK-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-84.
-
Resolution: Fixed
Fixed with e1dc0024ea5d869dd9945b920ba85dd2a24a51c1
Hey Alena,
I just ran into a problem where the fix you pushed on for CLOUDSTACK-226
(commit 11fe086adab8e790018343252ed08aac9a27b1c6) breaks a typical deployment
scenario for Nicira based networks. A Nicira NVP user does not need vlans so
should use the vlan range item during the setup of the p
Hugo Trippaers created CLOUDSTACK-271:
-
Summary: updatePhysicalNetwork dies with an NPE when the vlan
range is empty
Key: CLOUDSTACK-271
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-271
P
Hugo Trippaers created CLOUDSTACK-270:
-
Summary: Ui should not ask for a vlan range if the physical
network isolation type is not VLAN
Key: CLOUDSTACK-270
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-
[
https://issues.apache.org/jira/browse/CLOUDSTACK-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470679#comment-13470679
]
Marcus Sorensen commented on CLOUDSTACK-267:
My hunch hasn't immediately p
We're voting/discussing on better ways to upgrade ACS from 3.0.x to 4.0.
Yes, there is one commit by Edison and one by David. Both have them have
different ways to upgrade.
+1 to Edison's commit as it is backward compatible at the cost of user to
reinstall a package.
-1 to David's commit as it
This VOTE thread seems a little bit ill conceived. For something like this,
consensus building through discussion might've been a better approach. As
it stands, we seem to have generated about three or more separate things
people are now voting on within the same thread. (Which seems to indicate
th
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Friday, October 05, 2012 12:17 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] how to upgrade CloudStack from 3.0.x to 4.0
>
>
>
> On 10/05/2012 07:58 PM, Edison Su wrote:
> > Refer to bu
For the fix:
https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;a=commitdiff;h=f3a9a835d32ceeecaefac70fb9b77272e914f18c
I don't have any opinion about backward compatibility; but if we don't want it,
is there any point in handling upgrade use cases?
Also, use same logic for Debs
David Nalley created CLOUDSTACK-269:
---
Summary: Admin guide doesn't build
Key: CLOUDSTACK-269
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-269
Project: CloudStack
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CLOUDSTACK-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Nalley reopened CLOUDSTACK-253:
-
This is still broken
Validation failed:
installation-steps-overview.xml:94: validity er
*Columbo voice*
One more thing! Alex, as RM, you should probably wrap this thread up with
something like:
I am aborting this round.
I will start round two once the outstanding issues have been addressed.
Thank you for participating!
On Fri, Oct 5, 2012 at 9:49 PM, Noah Slater wrote:
> T
Thanks Bret, you covered all the points I had floating in my head! Heh.
The only additional thing I would say is: release VOTES are expensive.
Now, this is just my personal experience. But a VOTE is a public call for
everyone and anyone to go download this source artefact, and run through
this wi
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470629#comment-13470629
]
David Nalley commented on CLOUDSTACK-248:
-
Rohit - see my explanation from my
[
https://issues.apache.org/jira/browse/CLOUDSTACK-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470627#comment-13470627
]
David Nalley commented on CLOUDSTACK-209:
-
I think this is now resolved by com
Can someone from the docs team please look at the build for docs-4.0?
http://jenkins.cloudstack.org/job/docs-4.0/
Beginning work on en-US
installation-steps-overview.xml:94: validity error : Syntax of value
for attribute linkend of xref is not valid
installation-steps-overview.xml:94: validity er
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470611#comment-13470611
]
Rohit Yadav commented on CLOUDSTACK-248:
We're symlinking because the preix/in
Wido,
I think I figured it out. Please double check debian/changelog in
master and 4.0 branches for me though.
-chip
On Fri, Oct 5, 2012 at 11:50 AM, Chip Childers
wrote:
> Wido,
>
> When we cut a 4.0.0 release build to vote on next, what exactly needs
> to change in the debian/changelog file
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470598#comment-13470598
]
David Nalley commented on CLOUDSTACK-248:
-
This problem is caused by the symli
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rohit Yadav reassigned CLOUDSTACK-248:
--
Assignee: David Nalley (was: Rohit Yadav)
Thanks David for taking up https://issue
[
https://issues.apache.org/jira/browse/CLOUDSTACK-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470590#comment-13470590
]
Rohit Yadav commented on CLOUDSTACK-264:
I checked, we're bundling jasypt wit
[
https://issues.apache.org/jira/browse/CLOUDSTACK-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470587#comment-13470587
]
Rohit Yadav commented on CLOUDSTACK-266:
I think for devcloud, dom0 should be
[
https://issues.apache.org/jira/browse/CLOUDSTACK-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Nalley reopened CLOUDSTACK-209:
-
Assignee: David Nalley (was: Abhinav Roy)
I'll take this bug.
>
[
https://issues.apache.org/jira/browse/CLOUDSTACK-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470585#comment-13470585
]
Rohit Yadav commented on CLOUDSTACK-260:
This could be a JDK version or classp
[
https://issues.apache.org/jira/browse/CLOUDSTACK-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470581#comment-13470581
]
Rohit Yadav commented on CLOUDSTACK-259:
Could you try with rampart vaersion 1
[
https://issues.apache.org/jira/browse/CLOUDSTACK-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470580#comment-13470580
]
frank zhang commented on CLOUDSTACK-268:
Thanks Hugo. I think your fix is righ
+1 David. That would be great!
I too dislike the ugly hack.
Thanks.
From: David Nalley [da...@gnsa.us]
Sent: Saturday, October 06, 2012 12:41 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: [VOTE] how to upgrade CloudStack from 3.0.x to 4.0
On Fri
On 10/05/2012 07:58 PM, Edison Su wrote:
Refer to bug CLOUDSTACK-248, the root cause is :
we change cloud-agent-scripts to cloud-scripts, and change the installation
path from /usr/lib64/cloud/agent to /usr/lib64/cloud/common.
But in the source code, there are some other places still use
/usr
On Fri, Oct 5, 2012 at 3:13 PM, Chip Childers wrote:
> On Fri, Oct 5, 2012 at 2:49 PM, David Nalley wrote:
>> On Fri, Oct 5, 2012 at 2:36 PM, wrote:
>>> Updated Branches:
>>> refs/heads/4.0 8ba6c8b17 -> f7ebb76f5
>>>
>>>
>>> CLOUDSTACK-121: Fixed "Incorrect username/domainId login causes
>>>
On Fri, Oct 5, 2012 at 2:49 PM, David Nalley wrote:
> On Fri, Oct 5, 2012 at 2:36 PM, wrote:
>> Updated Branches:
>> refs/heads/4.0 8ba6c8b17 -> f7ebb76f5
>>
>>
>> CLOUDSTACK-121: Fixed "Incorrect username/domainId login causes
>> NullPointerException "
>>
>>
>> Project: http://git-wip-us.apa
On Fri, Oct 5, 2012 at 3:06 PM, Edison Su wrote:
>
>
>> -Original Message-
>> From: Edison Su [mailto:edison...@citrix.com]
>> Sent: Friday, October 05, 2012 11:20 AM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: [VOTE] how to upgrade CloudStack from 3.0.x to 4.0
>>
>>
>>
>> >
On Fri, Oct 5, 2012 at 3:07 PM, David Nalley wrote:
> On Fri, Oct 5, 2012 at 3:00 PM, Rohit Yadav wrote:
>> The Provides: in cloud.spec has not much effect for our case, refer this if
>> you're interested:
>> http://en.opensuse.org/openSUSE:Package_dependencies#Renaming_a_package
>> The review/
On Fri, Oct 5, 2012 at 3:00 PM, Rohit Yadav wrote:
> The Provides: in cloud.spec has not much effect for our case, refer this if
> you're interested:
> http://en.opensuse.org/openSUSE:Package_dependencies#Renaming_a_package
> The review/patch I submitted has no useful effect, so need for testing
> -Original Message-
> From: Edison Su [mailto:edison...@citrix.com]
> Sent: Friday, October 05, 2012 11:20 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [VOTE] how to upgrade CloudStack from 3.0.x to 4.0
>
>
>
> > -Original Message-
> > From: David Nalley [mailto
[
https://issues.apache.org/jira/browse/CLOUDSTACK-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470567#comment-13470567
]
edison su commented on CLOUDSTACK-248:
--
Add a new fix: bf1295e7976624f80c9ca0cb42
> On Oct. 5, 2012, 6:36 p.m., Alena Prokharchyk wrote:
> > Ship It!
Fixed with f7ebb76f57a0c88c8b379aacb1a4e3fd653a325f. Added WARN statement
myself.
- Alena
---
This is an automatically generated e-mail. To reply, visit:
https://revie
> On Sept. 14, 2012, 11:43 p.m., Alena Prokharchyk wrote:
> > 1)long dcId = dest.getDataCenter().getId();
> > List pods =
> > _podDao.listByDataCenterIdVMTypeAndState(dcId, VirtualMachine.Type.User,
> > VirtualMachine.State.Running);
> >
The Provides: in cloud.spec has not much effect for our case, refer this if
you're interested:
http://en.opensuse.org/openSUSE:Package_dependencies#Renaming_a_package
The review/patch I submitted has no useful effect, so need for testing.
+1 to put force install step in the upgrade section of in
> On Sept. 28, 2012, 6:18 a.m., Rohit Yadav wrote:
> > Fixed as per comments, waiting for review/commit.
Rohit, the updated diff still has Debug level for "Authentication failure: No
user with name" error message. It should be WARN
- Alena
---
> On Sept. 24, 2012, 6:12 p.m., Alex Huang wrote:
> > Does this need to go into 4.0?
>
> Rohit Yadav wrote:
> Yes, as per fix version on
> https://issues.apache.org/jira/browse/CLOUDSTACK-84
> But, whatever you advise.
This fix will break the following case:
* have removed account. Th
[
https://issues.apache.org/jira/browse/CLOUDSTACK-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470558#comment-13470558
]
Hugo Trippaers commented on CLOUDSTACK-268:
---
The only reference to this scri
1 - 100 of 205 matches
Mail list logo
