[jira] [Resolved] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-8930. - Resolution: Fixed > Showing blank screen when click 'Next' link in final step of Add Zone wizard. > - > > Key: CLOUDSTACK-8930 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Nitin Kumar Maharana >Priority: Blocker > Fix For: 4.6.0 > > > Issue: > Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' > link in final step of Add Zone wizard. Navigate to 1st step of Add Zone > wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8940) Wrong value is inserted into nics table netmask field when creating a VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952663#comment-14952663 ] ASF GitHub Bot commented on CLOUDSTACK-8940: Github user kansal commented on the pull request: https://github.com/apache/cloudstack/pull/916#issuecomment-147295409 @bhaisaab Sure will check about the back-porting of the issue. Apart from that, the previous values stored incorrectly need to be corrected in the database. I think a simple bash script will do. Your views and will it be part of this PR only? > Wrong value is inserted into nics table netmask field when creating a VM > > > Key: CLOUDSTACK-8940 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8940 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Kshitij Kansal >Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8901) PrepareTemplate job thread hard-coded to max 8 threads
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952611#comment-14952611
]
ASF GitHub Bot commented on CLOUDSTACK-8901:
Github user SudharmaJain commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/880#discussion_r41722125
--- Diff: setup/db/db/schema-452to460.sql ---
@@ -413,3 +413,4 @@ CREATE TABLE `cloud`.`ldap_trust_map` (
UNIQUE KEY `uk_ldap_trust_map__domain_id` (`domain_id`),
CONSTRAINT `fk_ldap_trust_map__domain_id` FOREIGN KEY (`domain_id`)
REFERENCES `domain` (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
+
--- End diff --
Removed the empty line.
> PrepareTemplate job thread hard-coded to max 8 threads
> --
>
> Key: CLOUDSTACK-8901
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8901
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: sudharma jain
>
> The thread pool is hardcoded to use 8 threads,
> com.cloud.template.TemplateManagerImpl.configure(String, Map):
> _preloadExecutor = Executors.newFixedThreadPool(8, new
> NamedThreadFactory("Template-Preloader"));
> Need to make it configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8896) Allocated percentage of storage can go beyond 100%
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952601#comment-14952601
]
ASF GitHub Bot commented on CLOUDSTACK-8896:
Github user karuturi commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/873#discussion_r41721892
--- Diff: server/src/com/cloud/storage/StorageManagerImpl.java ---
@@ -1736,7 +1737,10 @@ public boolean
storagePoolHasEnoughSpace(List volumes, StoragePool pool)
allocatedSizeWithtemplate =
_capacityMgr.getAllocatedPoolCapacity(poolVO, tmpl);
}
}
-if (volumeVO.getState() != Volume.State.Ready) {
+// A ready state volume is already allocated in a pool. so the
asking size is zero for it.
+// In case the volume is moving across pools or is not ready
yet, the asking size has to be computed
+s_logger.debug("pool id for the volume with id: " +
volumeVO.getId() + " is: " + volumeVO.getPoolId());
--- End diff --
as i said before, looking at the earlier logs will give you the context.
what more are you looking for? please suggest.
> Allocated percentage of storage can go beyond 100%
> --
>
> Key: CLOUDSTACK-8896
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8896
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Affects Versions: 4.5.2, 4.6.0
>Reporter: Rajani Karuturi
>Assignee: Rajani Karuturi
>
> This issue occurs when a volume in Ready state is moved across storage pools.
> Let us say there is a data volume, volume0 in Ready state in a cluster scope
> primary storage primary0.
> Now, when an operation is attempted to attach this volume to a vm in another
> cluster, the volume is moved to the new cluster and the asking size is zero
> at this time.
> you can observe logs like below with asking size 0 in the management server
> logs.
> 2015-09-22 08:49:02,754 DEBUG [c.c.s.StorageManagerImpl]
> (Work-Job-Executor-6:ctx-27e0990a job-37/job-38 ctx-985e5ad0)
> (logid:a0a97129) Checking pool: 1 for volume allocation
> [Vol[8|vm=null|DATADISK]], maxSize : 3298534883328, totalAllocatedSize :
> 24096276480, askingSize : 0, allocated disable threshold: 0.85
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8906) /var/log/cloud/ doesn't get logrotated on xenserver
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952375#comment-14952375 ] ASF GitHub Bot commented on CLOUDSTACK-8906: Github user SudharmaJain commented on the pull request: https://github.com/apache/cloudstack/pull/883#issuecomment-147233273 @remibergsma @koushik-das I have made the changes and have removed reimplementation of XenServer 6.0.2 resource. I have added changes to patch file for XenServer 6.0 resource, so that log rotation will work for 6.0 and 6.0.2. PR #861 will not fix this issue. Now both PR #883 and PR #861 need to be merged to fix the issues. > /var/log/cloud/ doesn't get logrotated on xenserver > > > Key: CLOUDSTACK-8906 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8906 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: sudharma jain > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8934) Default routes not configured for rVPC and RVR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952305#comment-14952305 ] ASF GitHub Bot commented on CLOUDSTACK-8934: Github user DaanHoogland commented on the pull request: https://github.com/apache/cloudstack/pull/923#issuecomment-147205805 overall code looks good, not sure if I need to test something special, @wilderrodrigues > Default routes not configured for rVPC and RVR > -- > > Key: CLOUDSTACK-8934 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8934 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues >Priority: Blocker > > User VMs cannot reach the outside world due to missing default routes in > Redundant VPCs and Redundant Isolated Networks. > In order to work it around I had to: > route add default gw 192.168.23.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8934) Default routes not configured for rVPC and RVR
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952303#comment-14952303
]
ASF GitHub Bot commented on CLOUDSTACK-8934:
Github user DaanHoogland commented on a diff in the pull request:
https://github.com/apache/cloudstack/pull/923#discussion_r41711315
--- Diff: systemvm/patches/debian/config/opt/cloud/bin/configure.py ---
@@ -123,24 +129,29 @@ def add_rule(self, cidr):
" -p %s " % rule['protocol'] +
" -m %s " % rule['protocol'] +
" --dport %s -j RETURN" % rnge])
+
+logging.debug("Current ACL IP direction is ==> %s",
self.direction)
if self.direction == 'egress':
-self.fw.append(["filter", "", " -A FW_OUTBOUND -j
FIREWALL_EGRESS_RULES"])
+self.fw.append(["filter", "", " -A FW_OUTBOUND -j
FW_EGRESS_RULES"])
--- End diff --
is this rename because of an ipfw change?
> Default routes not configured for rVPC and RVR
> --
>
> Key: CLOUDSTACK-8934
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8934
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
>Reporter: Wilder Rodrigues
>Assignee: Wilder Rodrigues
>Priority: Blocker
>
> User VMs cannot reach the outside world due to missing default routes in
> Redundant VPCs and Redundant Isolated Networks.
> In order to work it around I had to:
> route add default gw 192.168.23.1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi updated CLOUDSTACK-8930: Priority: Blocker (was: Major) > Showing blank screen when click 'Next' link in final step of Add Zone wizard. > - > > Key: CLOUDSTACK-8930 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Nitin Kumar Maharana >Priority: Blocker > Fix For: 4.6.0 > > > Issue: > Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' > link in final step of Add Zone wizard. Navigate to 1st step of Add Zone > wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952292#comment-14952292 ] ASF subversion and git services commented on CLOUDSTACK-8930: - Commit e64025a2b8d78b5c6fe8f2eff9d203ea6ef953de in cloudstack's branch refs/heads/master from [~milamber] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e64025a ] PR 906 (CLOUDSTACK-8930) and PR 912 combined. Bugs on localization buttons in zone wizard final step and Advanced search popup > Showing blank screen when click 'Next' link in final step of Add Zone wizard. > - > > Key: CLOUDSTACK-8930 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.6.0 > > > Issue: > Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' > link in final step of Add Zone wizard. Navigate to 1st step of Add Zone > wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952294#comment-14952294 ] ASF subversion and git services commented on CLOUDSTACK-8930: - Commit f0cd632d54905b4451771a53d3e4bfbd78626365 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0cd632 ] Merge pull request #915 from milamberspace/PR-906-912-BugZoneWizardAndAdvSearchPopup Pr 906 912 bug zone wizard and adv search popup * pr/915: PR 906 (CLOUDSTACK-8930) and PR 912 combined. Bugs on localization buttons in zone wizard final step and Advanced search popup CLOUDSTACK-8930: Showing blank screen when click 'Next' link in final step of Add Zone wizard. Signed-off-by: Rajani Karuturi > Showing blank screen when click 'Next' link in final step of Add Zone wizard. > - > > Key: CLOUDSTACK-8930 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.6.0 > > > Issue: > Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' > link in final step of Add Zone wizard. Navigate to 1st step of Add Zone > wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952291#comment-14952291 ] ASF subversion and git services commented on CLOUDSTACK-8930: - Commit 2651956cf427614f5c50e89c3405e88319961cdd in cloudstack's branch refs/heads/master from [~nitin.maharana] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2651956 ] CLOUDSTACK-8930: Showing blank screen when click 'Next' link in final step of Add Zone wizard. > Showing blank screen when click 'Next' link in final step of Add Zone wizard. > - > > Key: CLOUDSTACK-8930 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.6.0 > > > Issue: > Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' > link in final step of Add Zone wizard. Navigate to 1st step of Add Zone > wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8930) Showing blank screen when click 'Next' link in final step of Add Zone wizard.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952293#comment-14952293 ] ASF subversion and git services commented on CLOUDSTACK-8930: - Commit f0cd632d54905b4451771a53d3e4bfbd78626365 in cloudstack's branch refs/heads/master from [~rajanik] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f0cd632 ] Merge pull request #915 from milamberspace/PR-906-912-BugZoneWizardAndAdvSearchPopup Pr 906 912 bug zone wizard and adv search popup * pr/915: PR 906 (CLOUDSTACK-8930) and PR 912 combined. Bugs on localization buttons in zone wizard final step and Advanced search popup CLOUDSTACK-8930: Showing blank screen when click 'Next' link in final step of Add Zone wizard. Signed-off-by: Rajani Karuturi > Showing blank screen when click 'Next' link in final step of Add Zone wizard. > - > > Key: CLOUDSTACK-8930 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8930 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Nitin Kumar Maharana > Fix For: 4.6.0 > > > Issue: > Showing blank screen with 'Next' and 'Cancel' are showing when click 'Next' > link in final step of Add Zone wizard. Navigate to 1st step of Add Zone > wizard when click 'Next' link in blank screen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8933) SSVm and CPVM do not survice a reboot from API
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952289#comment-14952289 ] Rajani Karuturi commented on CLOUDSTACK-8933: - [~widodh] can you take a look at this please? its kvm specific and something to the with xml which I am not able to identify > SSVm and CPVM do not survice a reboot from API > -- > > Key: CLOUDSTACK-8933 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8933 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: SystemVM >Affects Versions: 4.6.0 > Environment: KVM Advanced / Basic zone >Reporter: Remi Bergsma >Priority: Blocker > Fix For: 4.6.0 > > Attachments: Console screenshot.png, reboot.4.5.log, reboot.4.6.log > > > These tests fail: > - integration.smoke.test_ssvm.TestSSVMs.test_07_reboot_ssvm > - integration.smoke.test_ssvm.TestSSVMs.test_08_reboot_cpvm > Stopping works, then CloudStack successfully deploys a new one. Rebooting > doesn’t work as it doesn’t complete the boot sequence. Looking at the > agent.log I noticed the systemvm doesn’t get patched so it is probably > waiting for that to happen. > A successful start shows this: > 2015-10-05 21:26:12,748 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Executing: > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n > v-1-VM -p > %template=domP%type=consoleproxy%host=192.168.22.61%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1%disable_rp_filter=true%eth2ip=192.168.23.2%eth2mask=255.255.255.0%gateway=192.168.23.1%eth0ip=169.254.1.20%eth0mask=255.255.0.0%eth1ip=192.168.22.137%eth1mask=255.255.255.0%mgmtcidr=192.168.22.0/24%localgw=192.168.22.1%internaldns1=8.8.4.4%dns1=8.8.8.8 > 2015-10-05 21:26:12,777 DEBUG [kvm.resource.LibvirtComputingResource] > (agentRequest-Handler-4:null) Execution is successful. > The reboot doesn’t do this. When I hit reboot and run this command manually, > it works: > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.pl -n > v-1-VM -p > %template=domP%type=consoleproxy%host=192.168.22.61%port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy1%proxy_vm=1%disable_rp_filter=tru%eth2ip=192.168.23.2%eth2mask=255.255.255.0%gateway=192.168.23.1%eth0ip=169.254.1.20%eth0mask=255.255.0.0%eth1ip=192.168.22.137%eth1mask=255.255.255.0%mgmtcidr=192.168.22.0/24%localgw=192.168.22.1%internaldns1=8.8.4.4%dns1=8.8.8.8 > I basically copy/pasted the patch line from the stop/start and used it when > rebooting. Now everything works. > We need to figure out why it doesn’t patch the system vms on reboot. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8934) Default routes not configured for rVPC and RVR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952280#comment-14952280 ] ASF GitHub Bot commented on CLOUDSTACK-8934: Github user wilderrodrigues commented on the pull request: https://github.com/apache/cloudstack/pull/923#issuecomment-147191452 Ping @remibergsma @karuturi @DaanHoogland @miguelaferreira @bvbharat @wido @borisroman All, the tests were executed successfully! We still have the problems with cleaning the networks, as you can see below. For that there is an issue which I will work on next (https://issues.apache.org/jira/browse/CLOUDSTACK-8935) Please, have a look and let me know if it all looks okay. Cheers, Wilder == Hardware required tests == * Management Server + MySQL running on CentOS 7.1 * One KVM host running on CentOS 7.1 * ACS Agent and Common RPMs built from source Stop existing router, add a PF rule and check we can access the VM ... === TestName: test_isolate_network_FW_PF_default_routes | Status : SUCCESS === ok Test redundant router internals ... === TestName: test_RVR_Network_FW_PF_SSH_default_routes | Status : SUCCESS === ok Create a redundant VPC with two networks with two VMs in each network ... === TestName: test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Status : SUCCESS === ok Create a redundant VPC with two networks with two VMs in each network and check default routes ... === TestName: test_02_redundant_VPC_default_routes | Status : SUCCESS === ok Test iptables default INPUT/FORWARD policy on RouterVM ... === TestName: test_02_routervm_iptables_policies | Status : SUCCESS === ok Test iptables default INPUT/FORWARD policies on VPC router ... === TestName: test_01_single_VPC_iptables_policies | Status : SUCCESS === ok Create a VPC with two networks with one VM in each network and test nics after destroy ... === TestName: test_01_VPC_nics_after_destroy | Status : SUCCESS === ok Create a VPC with two networks with one VM in each network and test default routes ... === TestName: test_02_VPC_default_routes | Status : SUCCESS === ok -- Ran 8 tests in 6855.736s OK == No Hardware required tests == * Management Server + MySQL running on CentOS 7.1 * Two KVM hosts running on CentOS 7.1 * ACS Agent and Common RPMs built from source Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS === ok Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS === ok Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS === ok Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS === ok Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS === ok Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS === ok Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS === ok Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS === ok Test migrate VM ... === TestName: test_08_migrate_vm | Status : SUCCESS === ok Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS === ok Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS === ok Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS === ok Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS === ok Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS === ok Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS === ok Test start router ... === TestName: test_08_start_router | Status : SUCCESS === ok Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS === ok Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS === ok Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS === ok Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS === ok Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS === ok Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS === ok Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS === ok
[jira] [Commented] (CLOUDSTACK-8934) Default routes not configured for rVPC and RVR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952279#comment-14952279 ] ASF GitHub Bot commented on CLOUDSTACK-8934: GitHub user wilderrodrigues opened a pull request: https://github.com/apache/cloudstack/pull/923 CLOUDSTACK-8934 - Default routes not configured for rVPC and RVR This PR fixes the default routes for redundant VPCs and isolated networks. New tests were introduced in order to make sure that the routers are working properly. During the tests, I found out that the Firewall Egress was not working properly when creating the network offering with default allow. The bug has been fixed and tests for redundant and non-redundant isolated networks were added. Test reports will follow in a separate comment. You can merge this pull request into a Git repository by running: $ git pull https://github.com/ekholabs/cloudstack fix/default_routes_CLOUDSTACK-8934 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/923.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 #923 commit 45642b83821ce0ecd6d4cddb76a77a2481e54d9a Author: Wilder Rodrigues Date: 2015-10-08T12:19:26Z CLOUDSTACK-8934 - Add default gateway when the public interface is up again commit 5d1cdc64409caed239f6814a8f73266c8e5eb6fe Author: Wilder Rodrigues Date: 2015-10-09T11:31:32Z CLOUDSTACK-8934 - Adding tests to cover default routes on IsoNest and RVR nets commit b4dc392bfdf4fb93e1652203b7d4027651cca5ac Author: Wilder Rodrigues Date: 2015-10-09T12:32:35Z CLOUDSTACK-8934 - Fix default EGRESS rules for isolated networks - The default is Accept and will be changed based on the configuration of the offering. CLOUDSTACK-8934 - The default egress is set as Deny in the router. - We had to change it on the Java side in order to make the apply it once the default is defined as allowed on the net offering commit cd8c3e97f594639292075d9a704dc7c382a103ca Author: Wilder Rodrigues Date: 2015-10-10T10:02:47Z CLOUDSTACK-8934 - Fix the AclIP class to make it configure the default FW policy > Default routes not configured for rVPC and RVR > -- > > Key: CLOUDSTACK-8934 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8934 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wilder Rodrigues >Assignee: Wilder Rodrigues >Priority: Blocker > > User VMs cannot reach the outside world due to missing default routes in > Redundant VPCs and Redundant Isolated Networks. > In order to work it around I had to: > route add default gw 192.168.23.1 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8848) Ensure power state is up to date when handling missing VMs in pwerReport
[
https://issues.apache.org/jira/browse/CLOUDSTACK-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952272#comment-14952272
]
ASF GitHub Bot commented on CLOUDSTACK-8848:
GitHub user resmo opened a pull request:
https://github.com/apache/cloudstack/pull/922
[4.5] CLOUDSTACK-8848: ensure power state is up to date for missing
PowerState handling
1:1 cherry-picks, see #909
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/resmo/cloudstack fix/4.5-8848
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/922.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 #922
commit 30c704915c882f8ac2ab551aa157d0b7a0bdb47f
Author: Rene Moser
Date: 2015-09-24T19:10:26Z
CLOUDSTACK-8848: ensure power state is up to date when handling missing VMs
in powerReport
There 2 things which has been changed.
* We look on power_state_update_time instead of update_time. Didn't make
sense to me at all to look at update_time.
* Due DB update optimisation, powerState will only be updated if <
MAX_CONSECUTIVE_SAME_STATE_UPDATE_COUNT. That is why we can not rely on these
information unless we make sure these are up to date.
commit 968991e0965d2279ba5f5c9e6496dc1a39dbccac
Author: Daan Hoogland
Date: 2015-10-02T09:42:42Z
CLOUDSTACK-8848: added null pointer guard to new public method
> Ensure power state is up to date when handling missing VMs in pwerReport
>
>
> Key: CLOUDSTACK-8848
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8848
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.5.2, 4.6.0
>Reporter: René Moser
>Assignee: Daan Hoogland
>Priority: Blocker
> Fix For: 4.5.3, 4.6.0
>
>
> In some conditions (race condition), VR gets rebooted after a out of band
> migration was done on vCenter.
> {panel:bgColor=#CE}
> Note, new global setting in 4.5.2 "VR reboot after out of band migration" is
> set to *false* and this looks more like a bug.
> {panel}
> After a VR migration to a host _and_ when the VM power state report gathering
> is running, the VR (and also any user VM as well) will get into the
> "PowerReportMissing".
> If the VM is a VR. it will be powered off and started again on vCenter. That
> is what we see. In can not be reproduced every time a migration was done, but
> it seems the problem is related to "powerReportMissing".
> I grep-ed the source and found this line related
> https://github.com/apache/cloudstack/blob/4.5.2/engine/orchestration/src/com/cloud/vm/VirtualMachineManagerImpl.java#L3616
> and also it seems that the graceful period might be also related,
> https://github.com/apache/cloudstack/blob/4.5.2/engine/orchestration/src/com/cloud/vm/VirtualMachinePowerStateSyncImpl.java#L110
> In case it is a user VM, we see in the logs that the state will be set to
> powered-off, but the VM keeps running. After a while a new VM power state
> report is running and the state for the user VM gets updated to Running
> again. Below the logs
> h2. VR r-342-VM reboot log
> {code:none}
> 2015-09-15 09:37:06,508 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgentCronJob-253:ctx-c4f59216) Run missing VM report. current time:
> 1442302626508
> 2015-09-15 09:37:06,508 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgentCronJob-253:ctx-c4f59216) Detected missing VM. host: 19, vm id:
> 342, power state: PowerReportMissing, last state update: 1442302506000
> 2015-09-15 09:37:06,508 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgentCronJob-253:ctx-c4f59216) vm id: 342 - time since last state
> update(120508ms) has passed graceful period
> 2015-09-15 09:37:06,517 DEBUG [c.c.v.VirtualMachinePowerStateSyncImpl]
> (DirectAgentCronJob-253:ctx-c4f59216) VM state report is updated. host: 19,
> vm id: 342, power state: PowerReportMissing
> 2015-09-15 09:37:06,525 INFO [c.c.v.VirtualMachineManagerImpl]
> (DirectAgentCronJob-253:ctx-c4f59216) VM r-342-VM is at Running and we
> received a power-off report while there is no pending jobs on it
> 2015-09-15 09:37:06,532 DEBUG [c.c.a.t.Request]
> (DirectAgentCronJob-253:ctx-c4f59216) Seq 19-4511199451741686482: Sending {
> Cmd , MgmtId: 345051122106, via: 19(cu01-testpod01-esx03.stxt.media.int),
> Ver: v1, Flags: 100011,
> [{"com.cloud.agent.api.StopCommand":{"isProxy":false,"executeInSequence":false,"checkBeforeCleanup":true,"vmName":"r-342-VM","wait":0}}]
> }
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952251#comment-14952251 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user KrisSterckx commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-147179219 @remibergsma OK done now > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952231#comment-14952231 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-147175350 Thanks @KrisSterckx but please remove the merge commit (using `rebase -i`) > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8832) Update Nuage VSP plugin to work with Nuage VSP release 3.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952223#comment-14952223 ] ASF GitHub Bot commented on CLOUDSTACK-8832: Github user KrisSterckx commented on the pull request: https://github.com/apache/cloudstack/pull/801#issuecomment-147174211 Hi @remibergsma , The rebase is committed. Thanks. (The cloudstack-pull-requests jenkins project is disabled though?) > Update Nuage VSP plugin to work with Nuage VSP release 3.2 > -- > > Key: CLOUDSTACK-8832 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8832 > Project: CloudStack > Issue Type: Improvement > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.6.0 >Reporter: Nick Livens >Assignee: Nick Livens > Attachments: nuageVspMarvinLogs.tar.gz > > > Nuage VSP 3.2 is being released, we want to bring the plugin up to date for > this release -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8825) Setting vm.allocation.algorithm to firstfitleastconsumed makes vm migration impossible from UI
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952215#comment-14952215 ] ASF GitHub Bot commented on CLOUDSTACK-8825: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/787#issuecomment-147172170 @anshul1886 Thanks! Would it be possible to write a Marvin test for this so that we can include in BVT? You already documented the manual steps so that is nice. With a Marvin test we prevent it from breaking again in the future. > Setting vm.allocation.algorithm to firstfitleastconsumed makes vm migration > impossible from UI > -- > > Key: CLOUDSTACK-8825 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8825 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Anshul Gangwar >Assignee: Anshul Gangwar >Priority: Critical > Fix For: 4.6.0 > > > 2015-07-28 15:11:05,690 DEBUG [c.c.a.ApiServlet] > (catalina-exec-20:ctx-1ba307fb) (logid:c70d7c41) ===START=== 10.103.2.50 -- > GET > command=findHostsForMigration&VirtualMachineId=880e71e6-c714-4a65-adc4-dd1e08aae8dd&response=json&sessionkey=XF0%2Fsb%2BhBReDbbWgKx%2FMmujS0R8%3D&_=1438076504170 > > 2015-07-28 15:11:05,751 ERROR [c.c.a.ApiServer] > (catalina-exec-20:ctx-1ba307fb ctx-899f7829) (logid:c70d7c41) unhandled > exception executing api command: [Ljava.lang.String;@39d29ca6 > com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT host_id, > SUM(total_capacity - (used_capacity+reserved_capacity))/SUM(total_capacity) > FROM `cloud`.`op_host_capacity` WHERE cluster_id = ? AND capacity_type = ? > GROUP BY host_id ORDER BY SUM(total_capacity - > (used_capacity+reserved_capacity))/SUM(total_capacity) DESC > at > com.cloud.capacity.dao.CapacityDaoImpl.orderHostsByFreeCapacity(CapacityDaoImpl.java:884) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8728) Testcase to Verify if VRs IP changes if it is destroyed and re-created in Basic Zone
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952214#comment-14952214 ] ASF GitHub Bot commented on CLOUDSTACK-8728: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/684#issuecomment-147172068 @pritisarap12 Please squash the commits, as there are now 2 merge commits and I cannot proceed like this. Make sure it has a single commit. Ping me if you need help with this. > Testcase to Verify if VRs IP changes if it is destroyed and re-created in > Basic Zone > > > Key: CLOUDSTACK-8728 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8728 > Project: CloudStack > Issue Type: Test > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Automation >Affects Versions: 4.2.1 >Reporter: Priti Sarap > Fix For: 4.2.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8812) CentOS 7 - systemd-tmpfiles - Operation not permitted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14952213#comment-14952213 ] ASF GitHub Bot commented on CLOUDSTACK-8812: Github user remibergsma commented on the pull request: https://github.com/apache/cloudstack/pull/888#issuecomment-147171964 @svenvogel Thanks for getting back to me. As far as I know, there is no such thing as a ShapeBlue release. They provide packages which make it easy to install CloudStack. It is confusing though, pinging @bhaisaab to see if we can make it more generic like we discussed before. Please remove the `ExecStart` change, as it doesn't work when I make packages from 4.6 branch: ``` cd packaging ./package.sh -d centos7 ``` The result I then install and then it fails when starting `cloudstack-management`: ``` -- Unit cloudstack-management.service has begun starting up. Oct 10 18:41:09 cs1 systemd[3493]: Failed at step EXEC spawning /usr/sbin/cloudstack-management: No such file or directory -- Subject: Process /usr/sbin/cloudstack-management could not be executed -- Defined-By: systemd ``` I will let you know how to make it one commit. Will do that when I'm back at my laptop. CentOS 7 support is greatly improved in CloudStack 4.6 so this should work. If you want, I can see if I can take it from here and make it work as the `sudo` issue may be there and needs to be resolved. > CentOS 7 - systemd-tmpfiles - Operation not permitted > - > > Key: CLOUDSTACK-8812 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8812 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Install and Setup >Affects Versions: 4.5.2 > Environment: KVM VM / CentOS Linux release 7.1.1503 (Core) >Reporter: Sven Vogel > > installation of the shapeblue upstream 4.5.2 repository. setup of the > database works. when i start the service with systemctl start > cloudstack-management.service i get the following error. > Sep 04 17:14:34 cloudstack01.oscloud.local systemd[1]: Starting CloudStack > Management Server... > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/run/netreport) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/dev/net) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/dev/mapper) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/dev/vfio) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/dev/snd) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/lock) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/lock/subsys) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/lock/lockdev) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/run/setrans) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/lock/lvm) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/lvm) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/run/console) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/run/faillock) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/run/sepermit) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/run/ppp) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/var/lock/ppp) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/user) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: Failed to > create file /var/log/wtmp: Permission denied > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: Failed to > create file /var/log/btmp: Permission denied > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfiles[5519]: > chmod(/run/systemd/ask-password) failed: Operation not permitted > Sep 04 17:14:34 cloudstack01.oscloud.local systemd-tmpfil
