[GitHub] cloudstack issue #1917: CLOUDSTACK-9756: Configure to ignore the ipassoc fai...
Github user jayapalu commented on the issue: https://github.com/apache/cloudstack/pull/1917 There are two LGTMs and there are not test failures in the test results. So marking tag:mergeready --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2024 ping @DaanHoogland @PaulAngus @rhtyd for review --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #876: CLOUDSTACK-8865: Adding SR doesn't create Stor...
Github user SudharmaJain commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/876#discussion_r109859606
--- Diff:
plugins/storage/volume/cloudbyte/src/org/apache/cloudstack/storage/datastore/lifecycle/ElastistorPrimaryDataStoreLifeCycle.java
---
@@ -359,7 +359,7 @@ public boolean attachCluster(DataStore store,
ClusterScope scope) {
PrimaryDataStoreInfo primarystore = (PrimaryDataStoreInfo) store;
// Check if there is host up in this cluster
-List allHosts =
_resourceMgr.listAllUpAndEnabledHosts(Host.Type.Routing,
primarystore.getClusterId(), primarystore.getPodId(),
primarystore.getDataCenterId());
+List allHosts =
_resourceMgr.listAllUpHosts(Host.Type.Routing, primarystore.getClusterId(),
primarystore.getPodId(), primarystore.getDataCenterId());
--- End diff --
@syed We cannot send commands to the host in maintenance mode. So it is not
possible to add an SR to those host.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack issue #1918: Management Server UI (VM statistics page) CPU Utiliz...
Github user jayakarteek commented on the issue: https://github.com/apache/cloudstack/pull/1918 @nvazquez @rafaelweingartner Done. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user DaanHoogland commented on the issue: https://github.com/apache/cloudstack/pull/2024 trivial enough: LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: F5 compile issue with 4.5.x
Mike, you need to get a newer f5 jar (icontrol) didn't dive into getting the f5 jar yet as I'm not using it. disabling works ;) On Tue, Apr 4, 2017 at 10:22 PM, Tutkowski, Mike wrote: > javac 1.8.0_121 > > By removing F5, though, I just got a successful compile. :) > > On 4/4/17, 2:19 PM, "Rafael Weingärtner" wrote: > > What version of Java 8 (e.g. jdk1.8.0_112)? > I had a similar problem quite a long time ago, the compilation would work > with jdk1.8.0_11 (or JDK 7), but would not work with anything higher. > Did you try using Java JDK 7? > > On Tue, Apr 4, 2017 at 4:14 PM, Tutkowski, Mike > > wrote: > > > I am running with Java 8 because I typically have been working with > 4.10. > > I just needed to go back to 4.5.x for another project I’m working on. > > > > Thanks > > > > On 4/4/17, 2:09 PM, "Rafael Weingärtner" > > wrote: > > > > I feel that I have seen this before. > > What is your JDK version? > > > > On Tue, Apr 4, 2017 at 4:06 PM, Tutkowski, Mike < > > mike.tutkow...@netapp.com> > > wrote: > > > > > Hi, > > > > > > I see the following error now when trying to compile 4.5.x code: > > > > > > [INFO] Compiling 12 source files to /Users/solidfire/Documents/ > > > CloudStack/CloudStack/plugins/network-elements/f5/target/classes > > > [INFO] > - > > > [ERROR] COMPILATION ERROR : > > > [INFO] > - > > > [ERROR] /Users/solidfire/Documents/CloudStack/CloudStack/plugins/ > > > network-elements/f5/src/com/cloud/network/resource/F5BigIpRe > > source.java:[411,26] > > > error: cannot access Stub > > > > > > I’ve not seen this “Stub” problem before. > > > > > > Anyone familiar with what it’s referring to? > > > > > > Thanks! > > > Mike > > > > > > > > > > > -- > > Rafael Weingärtner > > > > > > > > > -- > Rafael Weingärtner > > -- Daan
[GitHub] cloudstack issue #1997: CLOUDSTACK-9208: Assertion Error in VM_POWER_STATE h...
Github user jayapalu commented on the issue: https://github.com/apache/cloudstack/pull/1997 @DaanHoogland In the case of VM_POWER_STATE handler, if PowerOff or PowerReportMissing state is encountered, handlePowerOffReportWithNoPendingJobsOnVM() is called. If the VM is already in stopped state, so in DB the host ID is set to NULL. But in the above function, the sendStop() is still called on the empty hostID. So added condition in the sendStop() itself to check for the host id --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user cloudsadhu commented on the issue: https://github.com/apache/cloudstack/pull/1813 added logic to handle global level full clone setting. full clone parameter are handled differently (as per code its referring in 3 places due to that even if we set the full clone parameter at storage level still deployment is failing because during vm deployment its looking for global level config value event through we set storage level value to true. added logic to update global level ,restart management server and during cleaning resetting back to original values SadhuMAC:test_deploy_vm_root_resize_F94M72 sadhuccp$ cat results.txt Test deploy virtual machine with root resize ... === TestName: test_00_deploy_vm_root_resize | Status : SUCCESS === ok Test proper failure to deploy virtual machine with rootdisksize of 0 ... === TestName: test_01_deploy_vm_root_resize | Status : SUCCESS === ok Test proper failure to deploy virtual machine with rootdisksize less than template size ... === TestName: test_02_deploy_vm_root_resize | Status : SUCCESS === ok -- Ran 3 tests in 763.269s added the --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2024 @karuturi we have 2 LGTMs on this trivial PR, I guess we can proceed and merge it. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1997: CLOUDSTACK-9208: Assertion Error in VM_POWER_STATE h...
Github user DaanHoogland commented on the issue: https://github.com/apache/cloudstack/pull/1997 so that is two situations 1. it is known to be powered off (no sendStop() should be performed at all) 2. it is unknown because their is no report. Wouldn't one first check the host to send the stop command to before sending it? That said, I am +0 on this code, the check is not harming in any way. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #2027: Activate NioTest following changes in CLOUDST...
GitHub user marcaurele opened a pull request: https://github.com/apache/cloudstack/pull/2027 Activate NioTest following changes in CLOUDSTACK-9348 PR #1549 The first PR #1493 re-enabled the NioTest but not the new PR #1549. @rhtyd the test fails locally on my laptop. Is there any special configuration requirements? You can merge this pull request into a Git repository by running: $ git pull https://github.com/exoscale/cloudstack niotest Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/2027.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2027 commit 226e79c8ce0686ba3d5690ed90134934e26b635d Author: Marc-Aurèle Brothier Date: 2017-04-05T10:25:17Z Activate NioTest following changes in CLOUDSTACK-9348 PR #1549 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #874: CLOUDSTACK-8897: baremetal:addHost:make host tag info...
Github user kishankavala commented on the issue: https://github.com/apache/cloudstack/pull/874 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2027: Activate NioTest following changes in CLOUDSTACK-934...
Github user marcaurele commented on the issue: https://github.com/apache/cloudstack/pull/2027 @rhtyd the `NioTest` result is not consistent on my laptop and fails from time to time. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2008: [CLOUDSTACK-9840] Fix datetime format of snapshots e...
Github user olivierlemasle commented on the issue: https://github.com/apache/cloudstack/pull/2008 The Travis tests have finally succeeded. @borisstoyanov Any chance merging this pull request? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....
Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/1950 LGTM for me --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment
+1 this is something we have been working towards for a couple years now. On Apr 5, 2017 2:40 AM, "Daan Hoogland" wrote: > In the Apache foundation an experiment has been going on to host > mirrors of Apache project on github with more write access then just > to the mirror-bot. For those projects committers can merge on github > and put labels on PRs. I want to propose that we join that project and > intend to start a vote on it here, soon. > > questions, thoughts? > > -- > Daan >
[GitHub] cloudstack issue #2008: [CLOUDSTACK-9840] Fix datetime format of snapshots e...
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/2008 @olivierlemasle I think this PR needs at least 2 LGTMs and as agreed Rajani is taking care of mergin PRs. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment
+1 On Wed, Apr 5, 2017 at 8:40 AM, Daan Hoogland wrote: > In the Apache foundation an experiment has been going on to host > mirrors of Apache project on github with more write access then just > to the mirror-bot. For those projects committers can merge on github > and put labels on PRs. I want to propose that we join that project and > intend to start a vote on it here, soon. > > questions, thoughts? > > -- > Daan
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/2024 LGTM. @abhinandanprateek should we retarget this PR to 4.9? Thanks. @karuturi let's merge this before next 4.10 RC --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1950 Thanks @ustcweizhou @blueorangutan package --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1950 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment
+1 looking forward to this. From: Daan Hoogland Sent: 05 April 2017 12:10:19 To: dev Subject: [PROPOSAL] Apache Cloudstack should join the gitbox experiment In the Apache foundation an experiment has been going on to host mirrors of Apache project on github with more write access then just to the mirror-bot. For those projects committers can merge on github and put labels on PRs. I want to propose that we join that project and intend to start a vote on it here, soon. questions, thoughts? -- Daan rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment
+1 in addition to my support for joining the experiment, I would also like us to have the option to assign labels on the PRs. Such labels can be useful for CIs and RMs to determine and merge PRs that are fully tested and blessed by reviewers. Regards. rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue From: Rohit Yadav Sent: 05 April 2017 19:49:01 To: dev Subject: Re: [PROPOSAL] Apache Cloudstack should join the gitbox experiment +1 looking forward to this. From: Daan Hoogland Sent: 05 April 2017 12:10:19 To: dev Subject: [PROPOSAL] Apache Cloudstack should join the gitbox experiment In the Apache foundation an experiment has been going on to host mirrors of Apache project on github with more write access then just to the mirror-bot. For those projects committers can merge on github and put labels on PRs. I want to propose that we join that project and intend to start a vote on it here, soon. questions, thoughts? -- Daan
Re: F5 compile issue with 4.5.x
Mike, it seems issue with your axis dependency version. See and compare the axis and axis-jaxrpc dependency version from master branch. Install the f5 dependency jars from here: https://github.com/rhtyd/cloudstack-nonoss and while building ACS 4.5.x use JDK1.7. Regards. From: Tutkowski, Mike Sent: 05 April 2017 01:36:48 To: dev@cloudstack.apache.org Subject: F5 compile issue with 4.5.x Hi, I see the following error now when trying to compile 4.5.x code: [INFO] Compiling 12 source files to /Users/solidfire/Documents/CloudStack/CloudStack/plugins/network-elements/f5/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /Users/solidfire/Documents/CloudStack/CloudStack/plugins/network-elements/f5/src/com/cloud/network/resource/F5BigIpResource.java:[411,26] error: cannot access Stub I’ve not seen this “Stub” problem before. Anyone familiar with what it’s referring to? Thanks! Mike rohit.ya...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue
[GitHub] cloudstack issue #2025: [4.10-blocker] Fix error in restart network in 4.10....
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/2025 I think the issue caused it due to an additional `.0`, LGTM. This should work. @karuturi let's review and merge this blocker, thanks. @blueorangutan package --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2025: [4.10-blocker] Fix error in restart network in 4.10....
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2025 @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1950 Packaging result: âcentos6 âcentos7 âdebian. JID-618 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2025: [4.10-blocker] Fix error in restart network in 4.10....
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2025 Packaging result: âcentos6 âcentos7 âdebian. JID-619 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1813 @borisstoyanov Let's re-run vmware B.O test for this PR now --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1950 @blueorangutan test ubuntu kvm-ubuntu --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2025: [4.10-blocker] Fix error in restart network in 4.10....
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/2025 @blueorangutan test --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: F5 compile issue with 4.5.x
Thanks, guys! > On Apr 5, 2017, at 8:22 AM, Rohit Yadav wrote: > > Mike, it seems issue with your axis dependency version. See and compare the > axis and axis-jaxrpc dependency version from master branch. Install the f5 > dependency jars from here: https://github.com/rhtyd/cloudstack-nonoss and > while building ACS 4.5.x use JDK1.7. > > > Regards. > > > From: Tutkowski, Mike > Sent: 05 April 2017 01:36:48 > To: dev@cloudstack.apache.org > Subject: F5 compile issue with 4.5.x > > Hi, > > I see the following error now when trying to compile 4.5.x code: > > [INFO] Compiling 12 source files to > /Users/solidfire/Documents/CloudStack/CloudStack/plugins/network-elements/f5/target/classes > [INFO] - > [ERROR] COMPILATION ERROR : > [INFO] - > [ERROR] > /Users/solidfire/Documents/CloudStack/CloudStack/plugins/network-elements/f5/src/com/cloud/network/resource/F5BigIpResource.java:[411,26] > error: cannot access Stub > > I’ve not seen this “Stub” problem before. > > Anyone familiar with what it’s referring to? > > Thanks! > Mike > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > >
[GitHub] cloudstack issue #2025: [4.10-blocker] Fix error in restart network in 4.10....
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/2025 @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1950: [4.10] CLOUDSTACK-9462: Build packages on Ubuntu 14....
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1950 @rhtyd a Trillian-Jenkins test job (ubuntu mgmt + kvm-ubuntu) has been kicked to run smoke tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare
Hi Nux, So I'm still having trouble with the template :) As per the configuration http://dl.openvm.eu/cloudstack/config/centos/centos7-vmware.cfg the `centos` user gets the password set to as `password` but is never added to the sudoers list. When does that happen? Also, From the cloud-init logs it looks like it's not using the DHCP server but the default gateway so things like ssh-key is not being set. Apr 5 15:17:26 syed-test cloud-init: Cloud-init v. 0.7.5 running 'init-local' at Wed, 05 Apr 2017 15:17:26 +. Up 8.99 seconds. Apr 5 15:18:13 syed-test cloud-init: Cloud-init v. 0.7.5 running 'init' at Wed, 05 Apr 2017 15:18:13 +. Up 16.84 seconds. Apr 5 15:18:13 syed-test cloud-init: ci-info: ++Net device info+++ Apr 5 15:18:13 syed-test cloud-init: ci-info: ++--+--+---+---+ Apr 5 15:18:13 syed-test cloud-init: ci-info: | Device | Up | Address| Mask | Hw-Address| Apr 5 15:18:13 syed-test cloud-init: ci-info: ++--+--+---+---+ Apr 5 15:18:13 syed-test cloud-init: ci-info: | lo: | True | 127.0.0.1 | 255.0.0.0 | . | Apr 5 15:18:13 syed-test cloud-init: ci-info: | eth0: | True | 172.31.0.130 | 255.255.254.0 | 06:5a:58:00:01:6a | Apr 5 15:18:13 syed-test cloud-init: ci-info: ++--+--+---+---+ Apr 5 15:18:13 syed-test cloud-init: ci-info: +++Route info+++ Apr 5 15:18:13 syed-test cloud-init: ci-info: +---+-++---+---+---+ Apr 5 15:18:13 syed-test cloud-init: ci-info: | Route | Destination | Gateway |Genmask| Interface | Flags | Apr 5 15:18:13 syed-test cloud-init: ci-info: +---+-++---+---+---+ Apr 5 15:18:13 syed-test cloud-init: ci-info: | 0 | 0.0.0.0 | 172.31.0.1 |0.0.0.0|eth0 | UG | Apr 5 15:18:13 syed-test cloud-init: ci-info: | 1 | 172.31.0.0 | 0.0.0.0 | 255.255.254.0 |eth0 | U | Apr 5 15:18:13 syed-test cloud-init: ci-info: +---+-++---+---+---+ Apr 5 15:19:03 syed-test cloud-init: 2017-04-05 15:19:03,970 - url_helper.py[WARNING]: Calling ' http://172.31.0.1//latest/meta-data/instance-id' failed [50/120s]: unexpected error ['NoneType' object has no attribute 'status_code'] Apr 5 15:19:55 syed-test cloud-init: 2017-04-05 15:19:55,026 - url_helper.py[WARNING]: Calling ' http://172.31.0.1//latest/meta-data/instance-id' failed [101/120s]: unexpected error ['NoneType' object has no attribute 'status_code'] Apr 5 15:20:13 syed-test cloud-init: 2017-04-05 15:20:13,048 - url_helper.py[WARNING]: Calling ' http://172.31.0.1//latest/meta-data/instance-id' failed [119/120s]: unexpected error ['NoneType' object has no attribute 'status_code'] Apr 5 15:20:14 syed-test cloud-init: 2017-04-05 15:20:14,050 - DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata from ['http://172.31.0.1//latest/meta-data/instance-id'] after 120 seconds Apr 5 15:20:14 syed-test cloud-init: 2017-04-05 15:20:14,050 - util.py[WARNING]: No instance datasource found! Likely bad things to come! Looking at DataSourceCloudStack.py it seems like it is looking for leases in "/var/lib/dhclient", "/var/lib/dhcp" however the leases are located in "/var/lib/NetworkManager/" Do you know who maintains the DataSourceCloudStack.py? We fix this by either changing DataSourceCloudStack.py or by adding NM_CONTROLLED=no (and other conf params) in /etc/sysconfig/network-scripts/ifcfg-ethX . Let me know what you think. Thanks, -Syed On Mon, Apr 3, 2017 at 10:15 AM, Syed Ahmed wrote: > I'd love to see the 169.254.169.254 implemented. Maybe something we > can hack on at the CCC in Miami ;) > > On Mon, Apr 3, 2017 at 4:24 AM, Erik Weber wrote: > > On Mon, Apr 3, 2017 at 9:41 AM, Nux! wrote: > >> Syed, > >> > >> AFAIK the standard behaviour that is baked in the password script as > well as in the cloud-init Cloudstack meta source is to try whichever > address provides the DHCP. > >> > >> Can't wait to see config drive implemented so we can get rid of all > these head aches. > > > > Or the 169.254.169.254 address implemented :-) > > > > -- > > Erik >
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1813 @serg38 Got it, any idea when we'll get UI for this feature, I'd love to see it. @blueorangutan package --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1813 @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1813 Packaging result: âcentos6 âcentos7 âdebian. JID-620 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare
So I've opened a PR to fix this on the cloud-init side. https://code.launchpad.net/~syed1/cloud-init/+git/cloud-init/+merge/322024 We need this because CentOS7 has NetworkManager as the default manager for networking On Wed, Apr 5, 2017 at 11:41 AM, Syed Ahmed wrote: > Hi Nux, > > So I'm still having trouble with the template :) > > As per the configuration http://dl.openvm.eu/cloudstack/config/centos/ > centos7-vmware.cfg the `centos` user gets the password set to as > `password` but is never added to the sudoers list. When does that happen? > Also, From the cloud-init logs it looks like it's not using the DHCP server > but the default gateway so things like ssh-key is not being set. > > Apr 5 15:17:26 syed-test cloud-init: Cloud-init v. 0.7.5 running > 'init-local' at Wed, 05 Apr 2017 15:17:26 +. Up 8.99 seconds. > Apr 5 15:18:13 syed-test cloud-init: Cloud-init v. 0.7.5 running 'init' > at Wed, 05 Apr 2017 15:18:13 +. Up 16.84 seconds. > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++Net device info+++ > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++--+--+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | Device | Up | > Address| Mask | Hw-Address| > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++--+--+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | lo: | True | > 127.0.0.1 | 255.0.0.0 | . | > Apr 5 15:18:13 syed-test cloud-init: ci-info: | eth0: | True | > 172.31.0.130 | 255.255.254.0 | 06:5a:58:00:01:6a | > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++--+--+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +++Route info+++ > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +---+-++---+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | Route | Destination | > Gateway |Genmask| Interface | Flags | > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +---+-++---+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | 0 | 0.0.0.0 | > 172.31.0.1 |0.0.0.0|eth0 | UG | > Apr 5 15:18:13 syed-test cloud-init: ci-info: | 1 | 172.31.0.0 | > 0.0.0.0 | 255.255.254.0 |eth0 | U | > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +---+-++---+---+---+ > Apr 5 15:19:03 syed-test cloud-init: 2017-04-05 15:19:03,970 - > url_helper.py[WARNING]: Calling 'http://172.31.0.1//latest/ > meta-data/instance-id' failed [50/120s]: unexpected error ['NoneType' > object has no attribute 'status_code'] > Apr 5 15:19:55 syed-test cloud-init: 2017-04-05 15:19:55,026 - > url_helper.py[WARNING]: Calling 'http://172.31.0.1//latest/ > meta-data/instance-id' failed [101/120s]: unexpected error ['NoneType' > object has no attribute 'status_code'] > Apr 5 15:20:13 syed-test cloud-init: 2017-04-05 15:20:13,048 - > url_helper.py[WARNING]: Calling 'http://172.31.0.1//latest/ > meta-data/instance-id' failed [119/120s]: unexpected error ['NoneType' > object has no attribute 'status_code'] > Apr 5 15:20:14 syed-test cloud-init: 2017-04-05 15:20:14,050 - > DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata > from ['http://172.31.0.1//latest/meta-data/instance-id'] after 120 seconds > Apr 5 15:20:14 syed-test cloud-init: 2017-04-05 15:20:14,050 - > util.py[WARNING]: No instance datasource found! Likely bad things to come! > > Looking at DataSourceCloudStack.py it seems like it is looking for leases > in "/var/lib/dhclient", "/var/lib/dhcp" however the leases are located in > "/var/lib/NetworkManager/" Do you know who maintains the > DataSourceCloudStack.py? We fix this by either changing > DataSourceCloudStack.py or by adding NM_CONTROLLED=no (and other conf > params) in /etc/sysconfig/network-scripts/ifcfg-ethX . Let me know what > you think. > > Thanks, > -Syed > > > On Mon, Apr 3, 2017 at 10:15 AM, Syed Ahmed wrote: > >> I'd love to see the 169.254.169.254 implemented. Maybe something we >> can hack on at the CCC in Miami ;) >> >> On Mon, Apr 3, 2017 at 4:24 AM, Erik Weber wrote: >> > On Mon, Apr 3, 2017 at 9:41 AM, Nux! wrote: >> >> Syed, >> >> >> >> AFAIK the standard behaviour that is baked in the password script as >> well as in the cloud-init Cloudstack meta source is to try whichever >> address provides the DHCP. >> >> >> >> Can't wait to see config drive implemented so we can get rid of all >> these head aches. >> > >> > Or the 169.254.169.254 address implemented :-) >> > >> > -- >> > Erik >> > >
[GitHub] cloudstack issue #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and...
Github user sureshanaparti commented on the issue: https://github.com/apache/cloudstack/pull/1879 @nvazquez Updated the code for the issue reported. Can you please re-test? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1879: CLOUDSTACK-9719: [VMware] VR loses DHCP settings and...
Github user sureshanaparti commented on the issue: https://github.com/apache/cloudstack/pull/1879 @rhtyd Please kick off VMware tests on this PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 and VMWare
Syed, NetworkManager strikes again! ... I'll make sure it disappears from the template. Darn ... The centos user password as set by the kickstart is indeed "password" so the template can be accessed should cloud-init fail. I am not entirely at peace with this as could lead to security problems. The thing is, if cloud-init fails to retrieve the metadata, then it will not continue the setup in which it adds the user to sudoers, setup swap etc etc. That is why you could login with "password" but everything else was broken. Thanks for spotting this. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Syed Ahmed" > To: "dev" > Cc: "Nux!" > Sent: Wednesday, 5 April, 2017 16:41:27 > Subject: Re: Need help in getting CentOS 7 templates to run on Cloudstack 4.9 > and VMWare > Hi Nux, > > So I'm still having trouble with the template :) > > As per the configuration > http://dl.openvm.eu/cloudstack/config/centos/centos7-vmware.cfg the > `centos` user gets the password set to as `password` but is never added to > the sudoers list. When does that happen? Also, From the cloud-init logs it > looks like it's not using the DHCP server but the default gateway so things > like ssh-key is not being set. > > Apr 5 15:17:26 syed-test cloud-init: Cloud-init v. 0.7.5 running > 'init-local' at Wed, 05 Apr 2017 15:17:26 +. Up 8.99 seconds. > Apr 5 15:18:13 syed-test cloud-init: Cloud-init v. 0.7.5 running 'init' at > Wed, 05 Apr 2017 15:18:13 +. Up 16.84 seconds. > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++Net device info+++ > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++--+--+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | Device | Up | > Address| Mask | Hw-Address| > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++--+--+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | lo: | True | > 127.0.0.1 | 255.0.0.0 | . | > Apr 5 15:18:13 syed-test cloud-init: ci-info: | eth0: | True | > 172.31.0.130 | 255.255.254.0 | 06:5a:58:00:01:6a | > Apr 5 15:18:13 syed-test cloud-init: ci-info: > ++--+--+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +++Route info+++ > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +---+-++---+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | Route | Destination | > Gateway |Genmask| Interface | Flags | > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +---+-++---+---+---+ > Apr 5 15:18:13 syed-test cloud-init: ci-info: | 0 | 0.0.0.0 | > 172.31.0.1 |0.0.0.0|eth0 | UG | > Apr 5 15:18:13 syed-test cloud-init: ci-info: | 1 | 172.31.0.0 | > 0.0.0.0 | 255.255.254.0 |eth0 | U | > Apr 5 15:18:13 syed-test cloud-init: ci-info: > +---+-++---+---+---+ > Apr 5 15:19:03 syed-test cloud-init: 2017-04-05 15:19:03,970 - > url_helper.py[WARNING]: Calling ' > http://172.31.0.1//latest/meta-data/instance-id' failed [50/120s]: > unexpected error ['NoneType' object has no attribute 'status_code'] > Apr 5 15:19:55 syed-test cloud-init: 2017-04-05 15:19:55,026 - > url_helper.py[WARNING]: Calling ' > http://172.31.0.1//latest/meta-data/instance-id' failed [101/120s]: > unexpected error ['NoneType' object has no attribute 'status_code'] > Apr 5 15:20:13 syed-test cloud-init: 2017-04-05 15:20:13,048 - > url_helper.py[WARNING]: Calling ' > http://172.31.0.1//latest/meta-data/instance-id' failed [119/120s]: > unexpected error ['NoneType' object has no attribute 'status_code'] > Apr 5 15:20:14 syed-test cloud-init: 2017-04-05 15:20:14,050 - > DataSourceCloudStack.py[CRITICAL]: Giving up on waiting for the metadata > from ['http://172.31.0.1//latest/meta-data/instance-id'] after 120 seconds > Apr 5 15:20:14 syed-test cloud-init: 2017-04-05 15:20:14,050 - > util.py[WARNING]: No instance datasource found! Likely bad things to come! > > Looking at DataSourceCloudStack.py it seems like it is looking for leases > in "/var/lib/dhclient", "/var/lib/dhcp" however the leases are located in > "/var/lib/NetworkManager/" Do you know who maintains the > DataSourceCloudStack.py? We fix this by either changing > DataSourceCloudStack.py or by adding NM_CONTROLLED=no (and other conf > params) in /etc/sysconfig/network-scripts/ifcfg-ethX . Let me know what you > think. > > Thanks, > -Syed > > > On Mon, Apr 3, 2017 at 10:15 AM, Syed Ahmed wrote: > >> I'd love to see the 169.254.169.254 implemented. Maybe something we >> can hack on at the CCC in Miami ;) >> >> On Mon, Apr 3, 2017 at 4:24 AM,
[GitHub] cloudstack pull request #2028: CLOUDSTACK-9853: Add support for Secondary IP...
GitHub user wido opened a pull request: https://github.com/apache/cloudstack/pull/2028 CLOUDSTACK-9853: Add support for Secondary IPv6 Addresses and Subnets This commit adds support for passing IPv6 Addresses and/or Subnets as Secondary IPs. This is groundwork for CLOUDSTACK-9853 where IPv6 Subnets have to be allowed in the Security Groups of Instances to we can add DHCPv6 Prefix Delegation. Use ; instead of : for separating addresses, otherwise it would cause problems with IPv6 Addresses. Signed-off-by: Wido den Hollander You can merge this pull request into a Git repository by running: $ git pull https://github.com/wido/cloudstack ipv6-secips Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/2028.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #2028 commit 05f8e5c9fd9086f1ad9fc643fa25b108acfc3f48 Author: Wido den Hollander Date: 2017-01-31T15:59:28Z CLOUDSTACK-9853: Add support for Secondary IPv6 Addresses and Subnets This commit adds support for passing IPv6 Addresses and/or Subnets as Secondary IPs. This is groundwork for CLOUDSTACK-9853 where IPv6 Subnets have to be allowed in the Security Groups of Instances to we can add DHCPv6 Prefix Delegation. Use ; instead of : for separating addresses, otherwise it would cause problems with IPv6 Addresses. Signed-off-by: Wido den Hollander --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2024: CLOUDSTACK-9857: With this change if agent dies the ...
Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/2024 LGTM --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2018: CLOUDSTACK-9848: Added exit status checking for the ...
Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/2018 Can you explain a bit more why you are changing the iptable rules? As they can break a lot of things by accident. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1864: [Defunct][Experimental]Switch to using JDK 1.8 and S...
Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/1864 Are you still working on this update Rohit? Or is there a new PR for updating the SSVM to Debian 8? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2018: CLOUDSTACK-9848: Added exit status checking for the ...
Github user jayapalu commented on the issue:
https://github.com/apache/cloudstack/pull/2018
@wido
In the patch it can be observed that it is ("-A FIREWALL_%s DROP" % )
running without '-j' and it is not caught. There is duplicate rule due this the
impact is not seen.
So I have added the checking the iptables add command exit status, with
this iptables add command failure are caught. If there is error or exception
then it error will be returned to management server.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
Re: :[VOTE] Apache Cloudstack 4.10.0.0
Thanks for updating RN. Release notes is something which we haven't looked at till now. Any update on the xen 7.1 PR? ~Rajani http://cloudplatform.accelerite.com/ On Mon, Apr 3, 2017 at 6:41 PM, Pierre-Luc Dion wrote: > Look like we need a new systemvm named "systemvm-xenserver-4.10". t also > seams that older VR ex: 4.7.x are still usable if the globalsetting > "minreq.sysvmtemplate.version" is changed after the first boot of > cloudstack-management that upgraded the database. I'll update the release > note acordingly... > > So this 4.10 is looking promising! :-) > > > > > On Apr 1, 2017 16:02, "Pierre-Luc Dion" wrote: > > I'm testing upgrade to 4.10 from latest master. I have the following error > when upgrading from 4.7.2 in management-server.log: > > 2017-04-01 15:58:12,558 DEBUG [c.c.u.d.Upgrade4920to41000] > (localhost-startStop-1:null) (logid:) Updating System Vm template IDs > 2017-04-01 15:58:12,561 DEBUG [c.c.u.d.Upgrade4920to41000] > (localhost-startStop-1:null) (logid:) Updating KVM System Vms > 2017-04-01 15:58:12,561 WARN [c.c.u.d.Upgrade4920to41000] > (localhost-startStop-1:null) (logid:) 4.10.0.0KVM SystemVm template not > found. KVM hypervisor is not used, so not failing upgrade > 2017-04-01 15:58:12,562 DEBUG [c.c.u.d.Upgrade4920to41000] > (localhost-startStop-1:null) (logid:) Updating VMware System Vms > 2017-04-01 15:58:12,563 WARN [c.c.u.d.Upgrade4920to41000] > (localhost-startStop-1:null) (logid:) 4.10.0.0VMware SystemVm template not > found. VMware hypervisor is not used, so not failing upgrade > 2017-04-01 15:58:12,563 DEBUG [c.c.u.d.Upgrade4920to41000] > (localhost-startStop-1:null) (logid:) Updating XenServer System Vms > 2017-04-01 15:58:12,565 ERROR [c.c.u.DatabaseUpgradeChecker] > (localhost-startStop-1:null) (logid:) Unable to upgrade the database > com.cloud.utils.exception.CloudRuntimeException: 4.10.0.0XenServer > SystemVm > template not found. Cannot upgrade system Vms > at com.cloud.upgrade.dao.Upgrade4920to41000.updateSystemVmTempl > ates(Upgrade4920to41000.java:195) > at com.cloud.upgrade.dao.Upgrade4920to41000.performDataMigratio > n(Upgrade4920to41000.java:64) > at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpg > radeChecker.java:426) > at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgra > deChecker.java:507) > at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif > eCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) > at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif > eCycle.start(CloudStackExtendedLifeCycle.java:55) > at org.springframework.context.support.DefaultLifecycleProcesso > r.doStart(DefaultLifecycleProcessor.java:173) > at org.springframework.context.support.DefaultLifecycleProcesso > r.access$200(DefaultLifecycleProcessor.java:51) > at org.springframework.context.support.DefaultLifecycleProcesso > r$LifecycleGroup.start(DefaultLifecycleProcessor.java:346) > at org.springframework.context.support.DefaultLifecycleProcesso > r.startBeans(DefaultLifecycleProcessor.java:149) > at org.springframework.context.support.DefaultLifecycleProcesso > r.onRefresh(DefaultLifecycleProcessor.java:112) > at org.springframework.context.support.AbstractApplicationConte > xt.finishRefresh(AbstractApplicationContext.java:879) > at org.springframework.context.support.AbstractApplicationConte > xt.refresh(AbstractApplicationContext.java:545) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet.withModule(DefaultModuleDefinitionSet.java:233) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117) > at org.apache.cloudstack.spring.module.model.impl.DefaultModule > DefinitionSet.load(DefaultModuleDefinitionSet.java:79) > at org.apache.cloudstack.spring.module.factory.ModuleBasedConte > xtFactory.loadModules(ModuleBasedContextFactory.java:37) > at org.apache.cloudstack.spring.module.factory.CloudStackSpring > Context.init(CloudStackSpringContext.java:71) > at org.apache.cloudstack.spring.module.factory.CloudStackSpring > Context.(CloudStackSpringContext.java:58) > at org.apache.cloudstack.spring.module.factory.CloudStackSpring > Context.(CloudStackSpringContext.java:62) > at org.apache.cloudstack.spring.module.web.CloudStackContextLoaderListene > r. > contextInitialized(CloudStackContextLoaderListener.java:52) > at org.apache.catalina.core.StandardContext.listenerStart(Stand > ardContext.java:5068) > at org.a
Re: :[VOTE] Apache Cloudstack 4.10.0.0
A quick update on RC2: These are the current list of blockers. https://github.com/apache/cloudstack/pull/2022 https://github.com/apache/cloudstack/pull/2025 https://issues.apache.org/jira/browse/CLOUDSTACK-9849 https://github.com/apache/cloudstack/pull/1582 I am planning to close all the PRs by weekend. The blockers which Mike reported is still open and needs a fix. If everything is resolved, we can plan for RC2 on Monday. ~Rajani http://cloudplatform.accelerite.com/ On Thu, Apr 6, 2017 at 10:50 AM, Rajani Karuturi wrote: > Thanks for updating RN. Release notes is something which we haven't looked > at till now. > Any update on the xen 7.1 PR? > > ~Rajani > http://cloudplatform.accelerite.com/ > > On Mon, Apr 3, 2017 at 6:41 PM, Pierre-Luc Dion > wrote: > >> Look like we need a new systemvm named "systemvm-xenserver-4.10". t also >> seams that older VR ex: 4.7.x are still usable if the globalsetting >> "minreq.sysvmtemplate.version" is changed after the first boot of >> cloudstack-management that upgraded the database. I'll update the release >> note acordingly... >> >> So this 4.10 is looking promising! :-) >> >> >> >> >> On Apr 1, 2017 16:02, "Pierre-Luc Dion" wrote: >> >> I'm testing upgrade to 4.10 from latest master. I have the following error >> when upgrading from 4.7.2 in management-server.log: >> >> 2017-04-01 15:58:12,558 DEBUG [c.c.u.d.Upgrade4920to41000] >> (localhost-startStop-1:null) (logid:) Updating System Vm template IDs >> 2017-04-01 15:58:12,561 DEBUG [c.c.u.d.Upgrade4920to41000] >> (localhost-startStop-1:null) (logid:) Updating KVM System Vms >> 2017-04-01 15:58:12,561 WARN [c.c.u.d.Upgrade4920to41000] >> (localhost-startStop-1:null) (logid:) 4.10.0.0KVM SystemVm template not >> found. KVM hypervisor is not used, so not failing upgrade >> 2017-04-01 15:58:12,562 DEBUG [c.c.u.d.Upgrade4920to41000] >> (localhost-startStop-1:null) (logid:) Updating VMware System Vms >> 2017-04-01 15:58:12,563 WARN [c.c.u.d.Upgrade4920to41000] >> (localhost-startStop-1:null) (logid:) 4.10.0.0VMware SystemVm template not >> found. VMware hypervisor is not used, so not failing upgrade >> 2017-04-01 15:58:12,563 DEBUG [c.c.u.d.Upgrade4920to41000] >> (localhost-startStop-1:null) (logid:) Updating XenServer System Vms >> 2017-04-01 15:58:12,565 ERROR [c.c.u.DatabaseUpgradeChecker] >> (localhost-startStop-1:null) (logid:) Unable to upgrade the database >> com.cloud.utils.exception.CloudRuntimeException: 4.10.0.0XenServer >> SystemVm >> template not found. Cannot upgrade system Vms >> at com.cloud.upgrade.dao.Upgrade4920to41000.updateSystemVmTempl >> ates(Upgrade4920to41000.java:195) >> at com.cloud.upgrade.dao.Upgrade4920to41000.performDataMigratio >> n(Upgrade4920to41000.java:64) >> at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpg >> radeChecker.java:426) >> at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgra >> deChecker.java:507) >> at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif >> eCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65) >> at org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLif >> eCycle.start(CloudStackExtendedLifeCycle.java:55) >> at org.springframework.context.support.DefaultLifecycleProcesso >> r.doStart(DefaultLifecycleProcessor.java:173) >> at org.springframework.context.support.DefaultLifecycleProcesso >> r.access$200(DefaultLifecycleProcessor.java:51) >> at org.springframework.context.support.DefaultLifecycleProcesso >> r$LifecycleGroup.start(DefaultLifecycleProcessor.java:346) >> at org.springframework.context.support.DefaultLifecycleProcesso >> r.startBeans(DefaultLifecycleProcessor.java:149) >> at org.springframework.context.support.DefaultLifecycleProcesso >> r.onRefresh(DefaultLifecycleProcessor.java:112) >> at org.springframework.context.support.AbstractApplicationConte >> xt.finishRefresh(AbstractApplicationContext.java:879) >> at org.springframework.context.support.AbstractApplicationConte >> xt.refresh(AbstractApplicationContext.java:545) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet$2.with(DefaultModuleDefinitionSet.java:122) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet.withModule(DefaultModuleDefinitionSet.java:245) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet.withModule(DefaultModuleDefinitionSet.java:250) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet.withModule(DefaultModuleDefinitionSet.java:233) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117) >> at org.apache.cloudstack.spring.module.model.impl.DefaultModule >> DefinitionSet.load(DefaultModuleDefinitionSet.java:79) >> at org.apache.cloudstack.spring.module.factory.ModuleBasedConte >> xtFac
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user borisstoyanov commented on the issue: https://github.com/apache/cloudstack/pull/1813 @blueorangutan test centos7 vmware-55u3 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1813: CLOUDSTACK-9604: Root disk resize support for VMware...
Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1813 @borisstoyanov a Trillian-Jenkins test job (centos7 mgmt + vmware-55u3) has been kicked to run smoke tests --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #1908: CLOUDSTACK-9317: Fixed disable static nat on ...
Github user jayapalu commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1908#discussion_r110082657
--- Diff:
plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java
---
@@ -625,15 +627,20 @@ protected ExecutionResult
cleanupNetworkElementCommand(final IpAssocCommand cmd)
// there is only one ip in this public vlan and removing
it, so
// remove the nic
-if (ipsCount == 1 && !ip.isAdd()) {
-removeVif = true;
+if (lastIp != null && lastIp.equalsIgnoreCase("true") &&
!ip.isAdd()) {
--- End diff --
In CitrixresourceBase StringUtils is used from the
com.cloud.utils.StringUtils. So using StringUtils from java.lang will be
ambiguous.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack pull request #1908: CLOUDSTACK-9317: Fixed disable static nat on ...
Github user jayapalu commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/1908#discussion_r110082664
--- Diff:
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java
---
@@ -1764,9 +1765,12 @@ protected ExecutionResult
cleanupNetworkElementCommand(final IpAssocCommand cmd)
}
nicNum =
broadcastUriAllocatedToVM.get(ip.getBroadcastUri());
-if (numOfIps == 1 && !ip.isAdd()) {
-vifHotUnPlug(conn, routerName, ip.getVifMacAddress());
-networkUsage(routerIp, "deleteVif", "eth" + nicNum);
+if (lastIp != null && lastIp.equalsIgnoreCase("true") &&
!ip.isAdd()) {
--- End diff --
In CitrixresourceBase StringUtils is used from the
com.cloud.utils.StringUtils. So using StringUtils from java.lang will be
ambiguous.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] cloudstack issue #1889: CLOUDSTACK-9718: Revamp the dropdown showing lists o...
Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/1889 @rashmidixit travis is failing. Can you rebase with master and force push? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #2022: CLOUDSTACK-9591: Fix systemvmtemplate to not include...
Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/2022 @rhtyd can you check on the failures if they are related? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1944: CLOUDSTACK-9783: Improve metrics view performance
Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/1944 merging now --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #1944: CLOUDSTACK-9783: Improve metrics view perform...
Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/1944 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1282: CLOUDSTACK-9200: Fixed failed to delete snapshot if ...
Github user karuturi commented on the issue: https://github.com/apache/cloudstack/pull/1282 @swill @rhtyd can you review? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack issue #1880: CLOUDSTACK-9720: [VMware] template_spool_ref table i...
Github user sureshanaparti commented on the issue: https://github.com/apache/cloudstack/pull/1880 The above tests failure are not related to this PR. These are failing most for the other PRs. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] cloudstack pull request #1880: CLOUDSTACK-9720: [VMware] template_spool_ref ...
Github user asfgit closed the pull request at: https://github.com/apache/cloudstack/pull/1880 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
