[jira] [Commented] (CLOUDSTACK-6354) In com.cloud.utils.crypt.EncryptionSecretKeyChecker the key file paths are hard coded
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965053#comment-13965053 ] ASF subversion and git services commented on CLOUDSTACK-6354: - Commit 1d0b14673da2b877112a4030c17496e26cf3f531 in cloudstack's branch refs/heads/master from [~damoder.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=1d0b146 ] CLOUDSTACK-6354 : removing the hard coding of key path in EncryptionSecretKeyChecker In com.cloud.utils.crypt.EncryptionSecretKeyChecker the key file paths are hard coded - Key: CLOUDSTACK-6354 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6354 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Reporter: Damodar Reddy T Assignee: Damodar Reddy T Fix For: Future In com.cloud.utils.crypt.EncryptionSecretKeyChecker the key file paths are hard coded to /etc/cloudstack/management/key which will cause issue if key generation path gets changes during installation time. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in prog
Kishan Kavala created CLOUDSTACK-6371: - Summary: KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kishan Kavala Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_idhypervisor_type version s3_id --+ 750 1 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 751 1 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULLNULL NULLKVM 2.2 NULL 752 1 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULLNULL NULLKVM 2.2 NULL 755 1 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 756 1 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL --+ 5 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6372) [UI]Incorrect Field name while adding Primary Storage (*label.path)
Sailaja Mada created CLOUDSTACK-6372: Summary: [UI]Incorrect Field name while adding Primary Storage (*label.path) Key: CLOUDSTACK-6372 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6372 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Minor Attachments: addPSsnap.png Steps: 1. Install and Configure Management Server 2. Tried to add Primary Storage while configuring the Zone Observation: Noticed incorrect Field name while adding Primary Storage (*label.path) (attached snap) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6372) [UI]Incorrect Field name while adding Primary Storage (*label.path)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sailaja Mada updated CLOUDSTACK-6372: - Attachment: addPSsnap.png [UI]Incorrect Field name while adding Primary Storage (*label.path) --- Key: CLOUDSTACK-6372 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6372 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.4.0 Reporter: Sailaja Mada Priority: Minor Attachments: addPSsnap.png Steps: 1. Install and Configure Management Server 2. Tried to add Primary Storage while configuring the Zone Observation: Noticed incorrect Field name while adding Primary Storage (*label.path) (attached snap) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6373) listHost API response is not listing all the details of vgpuType.
Sanjay Tripathi created CLOUDSTACK-6373: --- Summary: listHost API response is not listing all the details of vgpuType. Key: CLOUDSTACK-6373 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6373 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 As of now, listHost API is only giving the vgputype name and remaining capacity apart from other information. As a fix, this api should also return all the vgpuType related information like video ram, max resoluton, max no. of display etc. which would be useful for admin/user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6366) add vgpuTypes details in vgpu_types table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-6366. - Resolution: Fixed add vgpuTypes details in vgpu_types table -- Key: CLOUDSTACK-6366 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6366 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 Add all the parameters related to vgpuTypes (like videoRam, maxHeads, maxResolution etc.) in vgpu_types table. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6373) listHost API response is not listing all the details of vgpuType.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965130#comment-13965130 ] ASF subversion and git services commented on CLOUDSTACK-6373: - Commit 5e9b25bad07ec08968abbd17c80ba1baafc618ec in cloudstack's branch refs/heads/4.4 from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5e9b25b ] CLOUDSTACK-6373: listHost API response is not listing all the details of vgpuType. listHost API response is not listing all the details of vgpuType. - Key: CLOUDSTACK-6373 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6373 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 As of now, listHost API is only giving the vgputype name and remaining capacity apart from other information. As a fix, this api should also return all the vgpuType related information like video ram, max resoluton, max no. of display etc. which would be useful for admin/user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6373) listHost API response is not listing all the details of vgpuType.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965131#comment-13965131 ] ASF subversion and git services commented on CLOUDSTACK-6373: - Commit 6a725c679563459963cbfd7eb933aab9894e2991 in cloudstack's branch refs/heads/master from [~sanjay.tripathi] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6a725c6 ] CLOUDSTACK-6373: listHost API response is not listing all the details of vgpuType. listHost API response is not listing all the details of vgpuType. - Key: CLOUDSTACK-6373 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6373 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 As of now, listHost API is only giving the vgputype name and remaining capacity apart from other information. As a fix, this api should also return all the vgpuType related information like video ram, max resoluton, max no. of display etc. which would be useful for admin/user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6316) [Automation]: Marvin Fixes and new Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965149#comment-13965149 ] ASF subversion and git services commented on CLOUDSTACK-6316: - Commit f866bb21e6fe8a754db1986d9fe3fd5e31db4228 in cloudstack's branch refs/heads/marvin from SrikanteswaraRao Talluri [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f866bb2 ] CLOUDSTACK-6316: Fixed component and smoke test failures-third pass [Automation]: Marvin Fixes and new Enhancements --- Key: CLOUDSTACK-6316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla 1. Earlier, i added a facility called DeleteDataCenter to clean up a datacenter, it has some issues for deleting, fixed them. This change is under deployDataCenter.py 2. Earlier Added a new facility, where we can deploy multiple zones and run regression simultaneously on all zones with multiple hypervisors, 2.1 So, user creates the data center with multiple zones and hypervisors. 2.2 Provides switches like zone and hypervisor to marvinPlugin and all tests are run against that zone. With this patch, added hypervisor switch to nose\marvinplugin. 3. Fixed an issue in one of the test suite under maint, it is using wait_for_vm function, which is not available. 4. Added time taken for async job, post some stress scenarios, we want to collect logs and analyze the time taken for various commands, their jobid and time taken, added time taken facility. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6374) LB rules added while router reqiuires upgrade should be removed from lb vm map
Kishan Kavala created CLOUDSTACK-6374: - Summary: LB rules added while router reqiuires upgrade should be removed from lb vm map Key: CLOUDSTACK-6374 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6374 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kishan Kavala Create LB from UI send 2 API commands. 1. Create LB rule - This succeeds since it only creates DB entry without sending any backend commands 2. Assign Vm to LB - This will fail But the entries in LbVm map are not removed. So after router upgrade, LbVm rules are applied on the router -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6375) 4.3 system vm template job failing in jenkins
Harikrishna Patnala created CLOUDSTACK-6375: --- Summary: 4.3 system vm template job failing in jenkins Key: CLOUDSTACK-6375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6375 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Abhinandan Prateek Fix For: 4.3.0 4.3 system vm template job failing; looks like build falling after the getting updated openssl 1.0.1e-2+deb7u6. http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm64/140/console (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 24061 files and directories currently installed.) Preparing to replace libssl1.0.0:amd64 1.0.1e-2 (using .../libssl1.0.0_1.0.1e-2+deb7u6_amd64.deb) ... Unpacking replacement libssl1.0.0:amd64 ... Selecting previously unselected package libc-dev-bin. Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package linux-libc-dev:amd64. Unpacking linux-libc-dev:amd64 (from .../linux-libc-dev_3.2.54-2_amd64.deb) ... Selecting previously unselected package libc6-dev:amd64. Unpacking libc6-dev:amd64 (from .../libc6-dev_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package uuid-dev. Unpacking uuid-dev (from .../uuid-dev_2.20.1-5.3_amd64.deb) ... Selecting previously unselected package libapr1-dev. Unpacking libapr1-dev (from .../libapr1-dev_1.4.6-3+deb7u1_amd64.deb) ... Selecting previously unselected package zlib1g-dev:amd64. Unpacking zlib1g-dev:amd64 (from .../zlib1g-dev_1%3a1.2.7.dfsg-13_amd64.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.1e-2+deb7u6_amd64.deb) ... Selecting previously unselected package libtcnative-1. Unpacking libtcnative-1 (from .../libtcnative-1_1.1.24-1_amd64.deb) ... Processing triggers for man-db ... Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u6) ... Checking for services that may need to be restarted...done. Checking init scripts... [?1049h[1;24r[4l[?25l(B[m[37m[40m[1;24r[H[2J[1;1H[1m[37m[44m [2;1H [3;1H [4;1H [5;1H [6;1H [7;1H [8;1H [9;1H [10;1H [11;1H [12;1H [13;1H [14;1H [15;1H [16;1H [17;1H [18;1H [19;1H [20;1H [21;1H [22;1H [23;1H [24;1H [24;79H [4h [4l[1;1H(B[m[37m[44mPackage configuration[4;2H(0[30m[47mlqu(B[m(B[30m[47m [31mConfiguring libssl1.0.0:amd64[30m (0[30m[47mtqk[5;2Hx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m [6;2H(B[m(0[30m[47mx(B[m(B[30m[47m This release of OpenSSL fixes some security issues. Services will not (0[30m[47mx(B[m(B[1m[37m[40m [7;2H(B[m(0[30m[47mx(B[m(B[30m[47m use these fixes until they are restarted. Please note that restarting (0[30m[47mx(B[m(B[1m[37m[40m [8;2H(B[m(0[30m[47mx(B[m(B[30m[47m the SSH server (sshd) should not affect any existing connections. (0[30m[47mx(B[m(B[1m[37m[40m [9;2H(B[m(0[30m[47mx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m
[jira] [Commented] (CLOUDSTACK-6375) 4.3 system vm template job failing in jenkins
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965153#comment-13965153 ] ASF subversion and git services commented on CLOUDSTACK-6375: - Commit cb970cb8cd1fa649d7a46d3d792a550d0f4b7202 in cloudstack's branch refs/heads/4.3 from [~aprateek] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=cb970cb ] CLOUDSTACK-6375: suppress the prompt while installing libssl 4.3 system vm template job failing in jenkins - Key: CLOUDSTACK-6375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6375 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Abhinandan Prateek Fix For: 4.3.0 4.3 system vm template job failing; looks like build falling after the getting updated openssl 1.0.1e-2+deb7u6. http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm64/140/console (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 24061 files and directories currently installed.) Preparing to replace libssl1.0.0:amd64 1.0.1e-2 (using .../libssl1.0.0_1.0.1e-2+deb7u6_amd64.deb) ... Unpacking replacement libssl1.0.0:amd64 ... Selecting previously unselected package libc-dev-bin. Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package linux-libc-dev:amd64. Unpacking linux-libc-dev:amd64 (from .../linux-libc-dev_3.2.54-2_amd64.deb) ... Selecting previously unselected package libc6-dev:amd64. Unpacking libc6-dev:amd64 (from .../libc6-dev_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package uuid-dev. Unpacking uuid-dev (from .../uuid-dev_2.20.1-5.3_amd64.deb) ... Selecting previously unselected package libapr1-dev. Unpacking libapr1-dev (from .../libapr1-dev_1.4.6-3+deb7u1_amd64.deb) ... Selecting previously unselected package zlib1g-dev:amd64. Unpacking zlib1g-dev:amd64 (from .../zlib1g-dev_1%3a1.2.7.dfsg-13_amd64.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.1e-2+deb7u6_amd64.deb) ... Selecting previously unselected package libtcnative-1. Unpacking libtcnative-1 (from .../libtcnative-1_1.1.24-1_amd64.deb) ... Processing triggers for man-db ... Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u6) ... Checking for services that may need to be restarted...done. Checking init scripts... [?1049h[1;24r[4l[?25l(B[m[37m[40m[1;24r[H[2J[1;1H[1m[37m[44m [2;1H [3;1H [4;1H [5;1H [6;1H [7;1H [8;1H [9;1H [10;1H [11;1H [12;1H [13;1H [14;1H [15;1H [16;1H [17;1H [18;1H [19;1H [20;1H [21;1H [22;1H [23;1H [24;1H [24;79H [4h [4l[1;1H(B[m[37m[44mPackage configuration[4;2H(0[30m[47mlqu(B[m(B[30m[47m [31mConfiguring libssl1.0.0:amd64[30m (0[30m[47mtqk[5;2Hx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m
[jira] [Created] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the V
Kishan Kavala created CLOUDSTACK-6376: - Summary: listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Kishan Kavala listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6374) LB rules added while router reqiuires upgrade should be removed from lb vm map
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6374: -- Fix Version/s: 4.5.0 4.4.0 LB rules added while router reqiuires upgrade should be removed from lb vm map -- Key: CLOUDSTACK-6374 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6374 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Create LB from UI send 2 API commands. 1. Create LB rule - This succeeds since it only creates DB entry without sending any backend commands 2. Assign Vm to LB - This will fail But the entries in LbVm map are not removed. So after router upgrade, LbVm rules are applied on the router -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6376: -- Fix Version/s: 4.5.0 4.4.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC --- Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the V
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6376: -- Affects Version/s: 4.3.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC --- Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala reassigned CLOUDSTACK-6376: - Assignee: Kishan Kavala listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC --- Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6374) LB rules added while router reqiuires upgrade should be removed from lb vm map
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6374: -- Affects Version/s: 4.3.0 LB rules added while router reqiuires upgrade should be removed from lb vm map -- Key: CLOUDSTACK-6374 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6374 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Create LB from UI send 2 API commands. 1. Create LB rule - This succeeds since it only creates DB entry without sending any backend commands 2. Assign Vm to LB - This will fail But the entries in LbVm map are not removed. So after router upgrade, LbVm rules are applied on the router -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in prog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6371: -- Affects Version/s: 4.3.0 KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. - Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_id hypervisor_type version s3_id --+ 7501 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 7511 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULL NULLNULLKVM 2.2 NULL 7521 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULL NULLNULLKVM 2.2 NULL 7551 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 7561 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL --+ 5 rows in set (0.00 sec) -- This message was sent by
[jira] [Updated] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in prog
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala updated CLOUDSTACK-6371: -- Fix Version/s: 4.5.0 4.4.0 KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. - Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_id hypervisor_type version s3_id --+ 7501 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 7511 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULL NULLNULLKVM 2.2 NULL 7521 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULL NULLNULLKVM 2.2 NULL 7551 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 7561 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL --+ 5 rows in set (0.00 sec) -- This
[jira] [Assigned] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in pro
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala reassigned CLOUDSTACK-6371: - Assignee: Kishan Kavala KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. - Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_id hypervisor_type version s3_id --+ 7501 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 7511 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULL NULLNULLKVM 2.2 NULL 7521 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULL NULLNULLKVM 2.2 NULL 7551 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 7561 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL --+ 5 rows in set (0.00
[jira] [Resolved] (CLOUDSTACK-6373) listHost API response is not listing all the details of vgpuType.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-6373. - Resolution: Fixed listHost API response is not listing all the details of vgpuType. - Key: CLOUDSTACK-6373 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6373 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Environment: MS 4.4 XS 620SP1 Reporter: Sanjay Tripathi Assignee: Sanjay Tripathi Fix For: 4.4.0 As of now, listHost API is only giving the vgputype name and remaining capacity apart from other information. As a fix, this api should also return all the vgpuType related information like video ram, max resoluton, max no. of display etc. which would be useful for admin/user. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965190#comment-13965190 ] ASF subversion and git services commented on CLOUDSTACK-6376: - Commit 26746feb39da6483059be7b33a2d5cd41f042c78 in cloudstack's branch refs/heads/master from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=26746fe ] CLOUDSTACK-6376: Return empty list when network tier has no ACL list associated. listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC --- Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in pr
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965188#comment-13965188 ] ASF subversion and git services commented on CLOUDSTACK-6371: - Commit 85072cb6b9c33cb14b6d211935a1d2a557b02f69 in cloudstack's branch refs/heads/master from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=85072cb ] CLOUDSTACK-6371: Set snapshot size in copycommand answer during snapshot backup KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. - Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_id hypervisor_type version s3_id --+ 7501 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 7511 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULL NULLNULLKVM 2.2 NULL 7521 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULL NULLNULLKVM 2.2 NULL 7551 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 7561 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL
[jira] [Commented] (CLOUDSTACK-6374) LB rules added while router reqiuires upgrade should be removed from lb vm map
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965189#comment-13965189 ] ASF subversion and git services commented on CLOUDSTACK-6374: - Commit 16ab5ce76c68c2a6c813daec9cd2c90d4c5eb8c6 in cloudstack's branch refs/heads/master from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=16ab5ce ] CLOUDSTACK-6374: Remove entries from lb vm map when lb rule apply fails LB rules added while router reqiuires upgrade should be removed from lb vm map -- Key: CLOUDSTACK-6374 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6374 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Create LB from UI send 2 API commands. 1. Create LB rule - This succeeds since it only creates DB entry without sending any backend commands 2. Assign Vm to LB - This will fail But the entries in LbVm map are not removed. So after router upgrade, LbVm rules are applied on the router -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6374) LB rules added while router reqiuires upgrade should be removed from lb vm map
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-6374. --- Resolution: Fixed LB rules added while router reqiuires upgrade should be removed from lb vm map -- Key: CLOUDSTACK-6374 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6374 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Create LB from UI send 2 API commands. 1. Create LB rule - This succeeds since it only creates DB entry without sending any backend commands 2. Assign Vm to LB - This will fail But the entries in LbVm map are not removed. So after router upgrade, LbVm rules are applied on the router -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965194#comment-13965194 ] ASF subversion and git services commented on CLOUDSTACK-6376: - Commit 6094e007978df664b9312ca2d45989614090ba87 in cloudstack's branch refs/heads/4.4 from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6094e00 ] CLOUDSTACK-6376: Return empty list when network tier has no ACL list associated. listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC --- Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6374) LB rules added while router reqiuires upgrade should be removed from lb vm map
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965193#comment-13965193 ] ASF subversion and git services commented on CLOUDSTACK-6374: - Commit 635b69676af21545ab4bdb8aa37a4fae5c4f8fe2 in cloudstack's branch refs/heads/4.4 from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=635b696 ] CLOUDSTACK-6374: Remove entries from lb vm map when lb rule apply fails LB rules added while router reqiuires upgrade should be removed from lb vm map -- Key: CLOUDSTACK-6374 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6374 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Fix For: 4.4.0, 4.5.0 Create LB from UI send 2 API commands. 1. Create LB rule - This succeeds since it only creates DB entry without sending any backend commands 2. Assign Vm to LB - This will fail But the entries in LbVm map are not removed. So after router upgrade, LbVm rules are applied on the router -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6376) listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-6376. --- Resolution: Fixed listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC --- Key: CLOUDSTACK-6376 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6376 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 listnetworkacls api when called with a networkid of a network which was created without selecting any acl list, returns all acl rules from default acl lists of the VPC. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in pr
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965192#comment-13965192 ] ASF subversion and git services commented on CLOUDSTACK-6371: - Commit 295fa84d4d3bb100055d7124bb0d0d68491328fc in cloudstack's branch refs/heads/4.4 from [~kishan] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=295fa84 ] CLOUDSTACK-6371: Set snapshot size in copycommand answer during snapshot backup KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. - Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_id hypervisor_type version s3_id --+ 7501 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 7511 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULL NULLNULLKVM 2.2 NULL 7521 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULL NULLNULLKVM 2.2 NULL 7551 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 7561 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL
[jira] [Resolved] (CLOUDSTACK-6371) KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in pro
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-6371. --- Resolution: Fixed KVM - secondary_storage count for account does not get incremted when snapshots are created. Count increases to the virtual size of snapshot when snapshot is in progress and then resets to 0 when snapshot is done. - Key: CLOUDSTACK-6371 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6371 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Affects Versions: 4.3.0 Reporter: Kishan Kavala Assignee: Kishan Kavala Fix For: 4.4.0, 4.5.0 Steps to reproduce the problem: Set - Advanced zone set up with KVM (Rhel 6.3) hosts. Create an account. Deploy few Vms. Take snapshots of ROOT volumes of few of the Vms. Check the resource_count for secondary_storage for this account. It is always set to 0. Notice that this value gets set to the virtual size of the the Volume when snapshot is in Progress. Once snapshot is done , it gets updated to 0. mysql select * from resource_count where account_id=4; id account_id domain_id typecount 53 4 NULLuser_vm 12 54 4 NULLpublic_ip 13 55 4 NULLvolume 12 56 4 NULLsnapshot5 57 4 NULLtemplate0 58 4 NULLproject 0 59 4 NULLnetwork 1 60 4 NULLvpc 0 61 4 NULLcpu 12 62 4 NULLmemory 1536 63 4 NULLprimary_storage 103079215104 64 4 NULLsecondary_storage 0 12 rows in set (0.00 sec) mysql select * from snapshots where account_id=4; --+ id data_center_id account_id domain_id volume_id disk_offering_idstatus pathnameuuidsnapshot_type type_descriptionsizecreated removed backup_snap_id swift_idsechost_id prev_snap_id hypervisor_type version s3_id --+ 7501 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140113223219 0696a291-7fe6-47d6-b4d4-0d489d7ddb3e0 MANUAL 8589934592 2014-01-13 22:32:19 NULLNULLNULLNULLNULLKVM 2.2 NULL 7511 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113224709 3ba19873-8a90-49f5-8a5c-58d0c980fc2b0 MANUAL 8589934592 2014-01-13 22:47:09 NULLNULLNULL NULLNULLKVM 2.2 NULL 7521 4 1 41 12 BackedUpNULL testnew_ROOT-41_20140113225245 d73d8c26-4f2a-4ead-801c-8e8cee42ab700 MANUAL 8589934592 2014-01-13 22:52:45 NULLNULLNULL NULLNULLKVM 2.2 NULL 7551 4 1 38 16 BackedUpNULL TestVM-tiny-host-1ps-0-2_ROOT-38_20140114020510 80672e8b-4a45-4070-9686-c68aee9c217d0 MANUAL 8589934592 2014-01-14 02:05:10 NULLNULLNULLNULLNULLKVM 2.2 NULL 7561 4 1 40 16 BackedUpNULL TestVM-tiny-host-1ps-0-4_ROOT-40_20140116234727 db0300ec-9558-40eb-8244-a8fbef7ad9b40 MANUAL 8589934592 2014-01-16 23:47:27 NULLNULLNULLNULLNULLKVM 2.2 NULL --+ 5 rows in set (0.00 sec) --
[jira] [Commented] (CLOUDSTACK-5674) [Automation]: Enhancements to accommodate multiple regression runs on a single CS server
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965288#comment-13965288 ] ASF subversion and git services commented on CLOUDSTACK-5674: - Commit ef9471692d485c6d4ae65fa334bca03cc18a3ca5 in cloudstack's branch refs/heads/marvin from [~gpshilamkar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ef94716 ] CLOUDSTACK-5674: Remove assigning accountname which was useless [Automation]: Enhancements to accommodate multiple regression runs on a single CS server Key: CLOUDSTACK-5674 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5674 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla 1. Currently, we will not be able to run multiple regression runs on a given CS server either sequentially\parallelly reason being few hard codings done at various places. 2. So, the idea is to run complete regression\automation test suites at one stretch on a given setup post deployDC. We deploy multiple zones with different hypervisor type in each zone. 3. Tests should cut down time and run across multiple zones with different hypervisor type in each zone, post deployment 3. The fixes and new changes should incorporate to take care to run suites parallelly if we wanted or sequentially for various test suites like vmware,xen,kvm etc on single CS machine without disturbing\redeploying and installing the new CS instance. Phase1: We will make framework\marvin changes. Phase2: Incorporate test module changes for these. Adding this ticket to track these changes. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-4665) ceph:delete volume fails with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965381#comment-13965381
]
ASF subversion and git services commented on CLOUDSTACK-4665:
-
Commit 4e9810dd51a465a6b413e3b439c950a9116ed90d in cloudstack's branch
refs/heads/4.4 from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=4e9810d ]
CLOUDSTACK-4665: Depend on rados-java 0.1.4
This fixes the ArrayIndexOutOfBounds exception during the
removal of a RBD based volume
ceph:delete volume fails with ArrayIndexOutOfBoundsException
Key: CLOUDSTACK-4665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Wido den Hollander
Fix For: 4.5.0
delete volume failed with exception and this leads to agent disconnect on
host side sometimes
steps:
1.create diskoffering based on RBD based storage
2.create data disk and attach to instance
3.detach the data disk and delete the data volume
Actual result:
delete volume failed with exception.
and volume state is in expunge state.
Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7ed5043e), no
need to delete from object in store ref table
Management log:
55,085 DEBUG [agent.transport.Request] (AgentManager-Handler-10:null) Seq
4-1926960794: Processing: { Ans: , MgmtId: 7175246184473, via: 4, Ver: v1,
Flags: 10, [{com.cloud.agent.api.Answer:{result:false,details:empty
String,wait:0}}] }
2013-09-13 23:08:55,086 DEBUG [agent.transport.Request]
(StatsCollector-3:null) Seq 4-1926960794: Received: { Ans: , MgmtId:
7175246184473, via: 4, Ver: v1, Flags: 10, { Answer } }
2013-09-13 23:08:55,086 DEBUG [agent.manager.AgentManagerImpl]
(StatsCollector-3:null) Details from executing class
com.cloud.agent.api.GetHostStatsCommand: empty String
2013-09-13 23:08:55,087 WARN [cloud.resource.ResourceManagerImpl]
(StatsCollector-3:null) Unable to obtain host 4 statistics.
2013-09-13 23:08:55,087 WARN [cloud.server.StatsCollector]
(StatsCollector-3:null) Received invalid host stats for host: 4
2013-09-13 23:08:58,598 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,619 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===END=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,809 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Processing Seq 2-13479: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-09-13 23:08:58,818 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Sending Seq 2-13479: { Ans: ,
MgmtId: 7175246184473, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-09-13 23:09:01,031 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===START=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,071 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===END=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,269 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,278 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,804 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) Ping from 1
2013-09-13 23:09:04,308 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.252.192.100 -- GET
command=deleteVolumeid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074598164
[jira] [Commented] (CLOUDSTACK-4665) ceph:delete volume fails with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965384#comment-13965384
]
ASF subversion and git services commented on CLOUDSTACK-4665:
-
Commit 63595203819b89ab6536c9b2eff4aed41270033d in cloudstack's branch
refs/heads/4.3-forward from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6359520 ]
CLOUDSTACK-4665: Depend on rados-java 0.1.4
This fixes the ArrayIndexOutOfBounds exception during the
removal of a RBD based volume
ceph:delete volume fails with ArrayIndexOutOfBoundsException
Key: CLOUDSTACK-4665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Wido den Hollander
Fix For: 4.5.0
delete volume failed with exception and this leads to agent disconnect on
host side sometimes
steps:
1.create diskoffering based on RBD based storage
2.create data disk and attach to instance
3.detach the data disk and delete the data volume
Actual result:
delete volume failed with exception.
and volume state is in expunge state.
Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7ed5043e), no
need to delete from object in store ref table
Management log:
55,085 DEBUG [agent.transport.Request] (AgentManager-Handler-10:null) Seq
4-1926960794: Processing: { Ans: , MgmtId: 7175246184473, via: 4, Ver: v1,
Flags: 10, [{com.cloud.agent.api.Answer:{result:false,details:empty
String,wait:0}}] }
2013-09-13 23:08:55,086 DEBUG [agent.transport.Request]
(StatsCollector-3:null) Seq 4-1926960794: Received: { Ans: , MgmtId:
7175246184473, via: 4, Ver: v1, Flags: 10, { Answer } }
2013-09-13 23:08:55,086 DEBUG [agent.manager.AgentManagerImpl]
(StatsCollector-3:null) Details from executing class
com.cloud.agent.api.GetHostStatsCommand: empty String
2013-09-13 23:08:55,087 WARN [cloud.resource.ResourceManagerImpl]
(StatsCollector-3:null) Unable to obtain host 4 statistics.
2013-09-13 23:08:55,087 WARN [cloud.server.StatsCollector]
(StatsCollector-3:null) Received invalid host stats for host: 4
2013-09-13 23:08:58,598 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,619 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===END=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,809 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Processing Seq 2-13479: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-09-13 23:08:58,818 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Sending Seq 2-13479: { Ans: ,
MgmtId: 7175246184473, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-09-13 23:09:01,031 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===START=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,071 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===END=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,269 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,278 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,804 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) Ping from 1
2013-09-13 23:09:04,308 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START=== 10.252.192.100 -- GET
[jira] [Commented] (CLOUDSTACK-4665) ceph:delete volume fails with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965383#comment-13965383
]
ASF subversion and git services commented on CLOUDSTACK-4665:
-
Commit 75792bf08e86bfb9bb9c23c86d275f6fe5d4346b in cloudstack's branch
refs/heads/4.4 from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75792bf ]
CLOUDSTACK-4665: Check if a snapshot is protected before trying to unprotect
Otherwise a RBDException will be thrown with the message that the snapshot
isn't protected.
Conflicts:
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java
ceph:delete volume fails with ArrayIndexOutOfBoundsException
Key: CLOUDSTACK-4665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Wido den Hollander
Fix For: 4.5.0
delete volume failed with exception and this leads to agent disconnect on
host side sometimes
steps:
1.create diskoffering based on RBD based storage
2.create data disk and attach to instance
3.detach the data disk and delete the data volume
Actual result:
delete volume failed with exception.
and volume state is in expunge state.
Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7ed5043e), no
need to delete from object in store ref table
Management log:
55,085 DEBUG [agent.transport.Request] (AgentManager-Handler-10:null) Seq
4-1926960794: Processing: { Ans: , MgmtId: 7175246184473, via: 4, Ver: v1,
Flags: 10, [{com.cloud.agent.api.Answer:{result:false,details:empty
String,wait:0}}] }
2013-09-13 23:08:55,086 DEBUG [agent.transport.Request]
(StatsCollector-3:null) Seq 4-1926960794: Received: { Ans: , MgmtId:
7175246184473, via: 4, Ver: v1, Flags: 10, { Answer } }
2013-09-13 23:08:55,086 DEBUG [agent.manager.AgentManagerImpl]
(StatsCollector-3:null) Details from executing class
com.cloud.agent.api.GetHostStatsCommand: empty String
2013-09-13 23:08:55,087 WARN [cloud.resource.ResourceManagerImpl]
(StatsCollector-3:null) Unable to obtain host 4 statistics.
2013-09-13 23:08:55,087 WARN [cloud.server.StatsCollector]
(StatsCollector-3:null) Received invalid host stats for host: 4
2013-09-13 23:08:58,598 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,619 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===END=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,809 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Processing Seq 2-13479: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-09-13 23:08:58,818 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Sending Seq 2-13479: { Ans: ,
MgmtId: 7175246184473, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-09-13 23:09:01,031 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===START=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,071 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===END=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,269 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,278 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,804 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-15:null) Ping from 1
2013-09-13 23:09:04,308 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null)
===START===
[jira] [Commented] (CLOUDSTACK-4665) ceph:delete volume fails with ArrayIndexOutOfBoundsException
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965385#comment-13965385
]
ASF subversion and git services commented on CLOUDSTACK-4665:
-
Commit aa9f29bd3f8d753fe2b6ccdba1f9a3718f54ca57 in cloudstack's branch
refs/heads/4.3-forward from [~widodh]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=aa9f29b ]
CLOUDSTACK-4665: Check if a snapshot is protected before trying to unprotect
Otherwise a RBDException will be thrown with the message that the snapshot
isn't protected.
modified:
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java
Conflicts:
plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/storage/LibvirtStorageAdaptor.java
ceph:delete volume fails with ArrayIndexOutOfBoundsException
Key: CLOUDSTACK-4665
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4665
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Wido den Hollander
Fix For: 4.5.0
delete volume failed with exception and this leads to agent disconnect on
host side sometimes
steps:
1.create diskoffering based on RBD based storage
2.create data disk and attach to instance
3.detach the data disk and delete the data volume
Actual result:
delete volume failed with exception.
and volume state is in expunge state.
Unsupported data object (VOLUME,
org.apache.cloudstack.storage.datastore.PrimaryDataStoreImpl@7ed5043e), no
need to delete from object in store ref table
Management log:
55,085 DEBUG [agent.transport.Request] (AgentManager-Handler-10:null) Seq
4-1926960794: Processing: { Ans: , MgmtId: 7175246184473, via: 4, Ver: v1,
Flags: 10, [{com.cloud.agent.api.Answer:{result:false,details:empty
String,wait:0}}] }
2013-09-13 23:08:55,086 DEBUG [agent.transport.Request]
(StatsCollector-3:null) Seq 4-1926960794: Received: { Ans: , MgmtId:
7175246184473, via: 4, Ver: v1, Flags: 10, { Answer } }
2013-09-13 23:08:55,086 DEBUG [agent.manager.AgentManagerImpl]
(StatsCollector-3:null) Details from executing class
com.cloud.agent.api.GetHostStatsCommand: empty String
2013-09-13 23:08:55,087 WARN [cloud.resource.ResourceManagerImpl]
(StatsCollector-3:null) Unable to obtain host 4 statistics.
2013-09-13 23:08:55,087 WARN [cloud.server.StatsCollector]
(StatsCollector-3:null) Received invalid host stats for host: 4
2013-09-13 23:08:58,598 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===START=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,619 DEBUG [cloud.api.ApiServlet] (catalina-exec-20:null)
===END=== 10.252.192.100 -- GET
command=listVolumesresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DlistAll=truepage=1pagesize=20_=1379074592467
2013-09-13 23:08:58,809 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Processing Seq 2-13479: { Cmd ,
MgmtId: -1, via: 2, Ver: v1, Flags: 11,
[{com.cloud.agent.api.ConsoleProxyLoadReportCommand:{_proxyVmId:2,_loadInfo:{\n
\connections\: []\n},wait:0}}] }
2013-09-13 23:08:58,818 DEBUG [agent.manager.AgentManagerImpl]
(AgentManager-Handler-2:null) SeqA 2-13479: Sending Seq 2-13479: { Ans: ,
MgmtId: 7175246184473, via: 2, Ver: v1, Flags: 100010,
[{com.cloud.agent.api.AgentControlAnswer:{result:true,wait:0}}] }
2013-09-13 23:09:01,031 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===START=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,071 DEBUG [cloud.api.ApiServlet] (catalina-exec-15:null)
===END=== 10.252.192.100 -- GET
command=listVolumesid=78601d43-4649-40bd-b6aa-86e46e427020response=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3D_=1379074594899
2013-09-13 23:09:01,269 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===START=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,278 DEBUG [cloud.api.ApiServlet] (catalina-exec-5:null)
===END=== 10.252.192.100 -- GET
command=listTagsresponse=jsonsessionkey=DjciUSGRnKCBl6Oban7oUhZ9O2o%3DresourceId=78601d43-4649-40bd-b6aa-86e46e427020resourceType=VolumelistAll=true_=1379074595115
2013-09-13 23:09:01,804 DEBUG [agent.manager.AgentManagerImpl]
[jira] [Updated] (CLOUDSTACK-6377) List templates returns destroyed temples when copying the same template after deleting.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-6377: - Affects Version/s: (was: 4.2.1) 4.2.0 List templates returns destroyed temples when copying the same template after deleting. --- Key: CLOUDSTACK-6377 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6377 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.0 Reporter: Bharat Kumar Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6377) List templates returns destroyed temples when copying the same template after deleting.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharat Kumar updated CLOUDSTACK-6377: - Description: steps to reproduce. 1.) copy template from zone A to zone B 2.) delete template form zone B 3.) copy template to zone B again. expected. the list template api should list the template as not destroyed Actual behaviour. Template in zone B is shown as destroyed( even after successful copy). when calling the list templates API. List templates returns destroyed temples when copying the same template after deleting. --- Key: CLOUDSTACK-6377 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6377 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.0 Reporter: Bharat Kumar Fix For: 4.2.1 steps to reproduce. 1.) copy template from zone A to zone B 2.) delete template form zone B 3.) copy template to zone B again. expected. the list template api should list the template as not destroyed Actual behaviour. Template in zone B is shown as destroyed( even after successful copy). when calling the list templates API. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6377) List templates returns destroyed temples when copying the same template after deleting.
Bharat Kumar created CLOUDSTACK-6377: Summary: List templates returns destroyed temples when copying the same template after deleting. Key: CLOUDSTACK-6377 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6377 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: API, Management Server Affects Versions: 4.2.1 Reporter: Bharat Kumar Fix For: 4.2.1 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965421#comment-13965421 ] Sudha Ponnaganti commented on CLOUDSTACK-3535: -- Paul can you confirm that this is actually happening No HA actions are performed when a KVM host goes offline Key: CLOUDSTACK-3535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.1.0, 4.1.1, 4.2.0 Environment: KVM (CentOS 6.3) with CloudStack 4.1 Reporter: Paul Angus Assignee: edison su Priority: Blocker Fix For: 4.2.0 Attachments: KVM-HA-4.1.1.2013-08-09-v1.patch, extract-management-server.log.2013-08-09, management-server.log.Agent If a KVM host 'goes down', CloudStack does not perform HA for instances which are marked as HA enabled on that host (including system VMs) CloudStack does not show the host as disconnected. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965421#comment-13965421 ] Sudha Ponnaganti edited comment on CLOUDSTACK-3535 at 4/10/14 3:04 PM: --- Paul can you confirm that this is actually working for you was (Author: sudhap): Paul can you confirm that this is actually happening for you No HA actions are performed when a KVM host goes offline Key: CLOUDSTACK-3535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.1.0, 4.1.1, 4.2.0 Environment: KVM (CentOS 6.3) with CloudStack 4.1 Reporter: Paul Angus Assignee: edison su Priority: Blocker Fix For: 4.2.0 Attachments: KVM-HA-4.1.1.2013-08-09-v1.patch, extract-management-server.log.2013-08-09, management-server.log.Agent If a KVM host 'goes down', CloudStack does not perform HA for instances which are marked as HA enabled on that host (including system VMs) CloudStack does not show the host as disconnected. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-3535) No HA actions are performed when a KVM host goes offline
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965421#comment-13965421 ] Sudha Ponnaganti edited comment on CLOUDSTACK-3535 at 4/10/14 3:04 PM: --- Paul can you confirm that this is actually happening for you was (Author: sudhap): Paul can you confirm that this is actually happening No HA actions are performed when a KVM host goes offline Key: CLOUDSTACK-3535 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3535 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller, KVM, Management Server Affects Versions: 4.1.0, 4.1.1, 4.2.0 Environment: KVM (CentOS 6.3) with CloudStack 4.1 Reporter: Paul Angus Assignee: edison su Priority: Blocker Fix For: 4.2.0 Attachments: KVM-HA-4.1.1.2013-08-09-v1.patch, extract-management-server.log.2013-08-09, management-server.log.Agent If a KVM host 'goes down', CloudStack does not perform HA for instances which are marked as HA enabled on that host (including system VMs) CloudStack does not show the host as disconnected. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6378) SSL: Fail to find the generated keystore.
Michael Phillips created CLOUDSTACK-6378: Summary: SSL: Fail to find the generated keystore. Key: CLOUDSTACK-6378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6378 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.1, 4.3.0 Environment: Confirmed this is an issue on centos 6.5 and ubuntu 12.04 on both versions of Cloudstack 4.2.1 and 4.3.0 Reporter: Michael Phillips Priority: Minor The logs on versions 4.2.1 and 4.3.0 get filled with the following error: WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find the generated keystore. Loading fail-safe one to continue. In 4.2.1, the fix was to rename cloudmanagementserver.keystore, to cloud.keystore then restart cloudstack. In 4.3.0, the system by default does not create the file named cloudmanagementserver.keystore. You now have to create the keystore file by running sudo keytool -genkey -keystore, then name the file cloud.keystore. This error is reproducible, and confirmed by other users. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6191) Volume provisioning type option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965446#comment-13965446 ] ASF subversion and git services commented on CLOUDSTACK-6191: - Commit 11f5bdd78de4121331b07995800f6e9e7c22f2c0 in cloudstack's branch refs/heads/master from [~mlsorensen] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=11f5bdd ] CLOUDSTACK-6191 Add support for specifying volume provisioning type (thin, sparse, fat) in disk/compute offerings. Submitted-by: Yoshikazu Nojima m...@ynojima.net Reviewed-by: Marcus Sorensen, Mike Tutowski Volume provisioning type option --- Key: CLOUDSTACK-6191 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Priority: Minor Fix For: Future Thin provisioning of a volume saves consumption of a storage, and fat provisioning minimizes IOPS performance overhead. This feature implements a global setting to provide users an option to select how to provision volumes. Design doc: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6047) Make Virtual Router to aggregate execution of commands
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sheng Yang resolved CLOUDSTACK-6047. Resolution: Fixed Make Virtual Router to aggregate execution of commands -- Key: CLOUDSTACK-6047 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6047 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller, Virtual Router Reporter: Sheng Yang Assignee: Sheng Yang Priority: Blocker Fix For: 4.4.0 Currently VR has an scalability issue during the large deployment. Everytime when VR need to be re-create or reboot, CloudStack would send lots of programming commands to it. VR would treat them as individual commands then execute them. In large deployment, it would take tens of minutes or even hours to complete all the necessary updates, like setup DHCP and programming firewall. For example, in the past, everytime we setup DHCP in VR, we need to restart dnsmasq service for every programming, which is very time consuming. Though we've introduced a way to reload without restart dnsmasq, but the same issue existed with apache2 and other services as well. And every SSH to VR would also time consuming. The new approach of reprogramming VR, would help greatly on this issue, and hopefully great reduce the VR programming time. It would introduce a mechanism to aggregate the commands to be executed, and do it in one batch inside VR. And restart the related services(if necesary) only after the whole batch is completed. The configuration would be transfer to VR in one piece as well, eliminate any unnecessary ssh. We would expect in such scenario, most configuration would only be text update and involve no more time consuming operations. We would leave every possible time consuming operation to the end of execution of aggregated commands. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6378) SSL: Fail to find the generated keystore.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965457#comment-13965457 ] Sheng Yang commented on CLOUDSTACK-6378: We traced back the issue to: commit de448ec4792eda5b47d79b26e9cb8ce96a2b22f4 Author: Wei Zhou w.z...@leaseweb.com Date: Thu Nov 7 11:09:06 2013 +0100 CLOUDSTACK-5042: change cloud.keystore to cloudmanagementserver.keystore and install it This commit only modify the keystore name, but remain the real place to use the keystore unchangd. It would make cloudstack fail to found the keystore when cloud.keystore not existed, thus involve in fail-safe keystore kick in. We're working on fix it. SSL: Fail to find the generated keystore. - Key: CLOUDSTACK-6378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6378 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.1, 4.3.0 Environment: Confirmed this is an issue on centos 6.5 and ubuntu 12.04 on both versions of Cloudstack 4.2.1 and 4.3.0 Reporter: Michael Phillips Priority: Minor The logs on versions 4.2.1 and 4.3.0 get filled with the following error: WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find the generated keystore. Loading fail-safe one to continue. In 4.2.1, the fix was to rename cloudmanagementserver.keystore, to cloud.keystore then restart cloudstack. In 4.3.0, the system by default does not create the file named cloudmanagementserver.keystore. You now have to create the keystore file by running sudo keytool -genkey -keystore, then name the file cloud.keystore. This error is reproducible, and confirmed by other users. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (CLOUDSTACK-6378) SSL: Fail to find the generated keystore.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965457#comment-13965457 ] Sheng Yang edited comment on CLOUDSTACK-6378 at 4/10/14 3:37 PM: - We traced back the issue to: commit de448ec4792eda5b47d79b26e9cb8ce96a2b22f4 Author: Wei Zhou w.z...@leaseweb.com Date: Thu Nov 7 11:09:06 2013 +0100 CLOUDSTACK-5042: change cloud.keystore to cloudmanagementserver.keystore and install it This commit only modify the keystore name, but remain the real place to use the keystore unchanged(Link.java). It would make cloudstack fail to found the keystore when cloud.keystore not existed, thus involve in fail-safe keystore kick in. We're working on fix it. was (Author: yasker): We traced back the issue to: commit de448ec4792eda5b47d79b26e9cb8ce96a2b22f4 Author: Wei Zhou w.z...@leaseweb.com Date: Thu Nov 7 11:09:06 2013 +0100 CLOUDSTACK-5042: change cloud.keystore to cloudmanagementserver.keystore and install it This commit only modify the keystore name, but remain the real place to use the keystore unchangd. It would make cloudstack fail to found the keystore when cloud.keystore not existed, thus involve in fail-safe keystore kick in. We're working on fix it. SSL: Fail to find the generated keystore. - Key: CLOUDSTACK-6378 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6378 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.2.1, 4.3.0 Environment: Confirmed this is an issue on centos 6.5 and ubuntu 12.04 on both versions of Cloudstack 4.2.1 and 4.3.0 Reporter: Michael Phillips Priority: Minor The logs on versions 4.2.1 and 4.3.0 get filled with the following error: WARN [c.c.u.n.Link] (AgentManager-Selector:null) SSL: Fail to find the generated keystore. Loading fail-safe one to continue. In 4.2.1, the fix was to rename cloudmanagementserver.keystore, to cloud.keystore then restart cloudstack. In 4.3.0, the system by default does not create the file named cloudmanagementserver.keystore. You now have to create the keystore file by running sudo keytool -genkey -keystore, then name the file cloud.keystore. This error is reproducible, and confirmed by other users. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6191) Volume provisioning type option
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoshikazu Nojima resolved CLOUDSTACK-6191. -- Resolution: Fixed Fix Version/s: (was: Future) 4.5.0 Volume provisioning type option --- Key: CLOUDSTACK-6191 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6191 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Priority: Minor Fix For: 4.5.0 Thin provisioning of a volume saves consumption of a storage, and fat provisioning minimizes IOPS performance overhead. This feature implements a global setting to provide users an option to select how to provision volumes. Design doc: https://cwiki.apache.org/confluence/display/CLOUDSTACK/Volume+provisioning+type+option -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-6379) UI:MS: Unable to create a user type Admin under a domain; No API being fired
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Parth Jagirdar updated CLOUDSTACK-6379: --- Attachment: domain admin.jpg UI:MS: Unable to create a user type Admin under a domain; No API being fired Key: CLOUDSTACK-6379 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6379 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.4.0 Environment: 4.4 Reporter: Parth Jagirdar Priority: Critical Fix For: 4.4.0 Attachments: domain admin.jpg Create a domain, then create a user under it of type Admin. Observe no API being fired upon clicking OK. Also observe Reference Error: rootDomainId not defined. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6379) UI:MS: Unable to create a user type Admin under a domain; No API being fired
Parth Jagirdar created CLOUDSTACK-6379: -- Summary: UI:MS: Unable to create a user type Admin under a domain; No API being fired Key: CLOUDSTACK-6379 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6379 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, UI Affects Versions: 4.4.0 Environment: 4.4 Reporter: Parth Jagirdar Priority: Critical Fix For: 4.4.0 Attachments: domain admin.jpg Create a domain, then create a user under it of type Admin. Observe no API being fired upon clicking OK. Also observe Reference Error: rootDomainId not defined. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6375) 4.3 system vm template job failing in jenkins
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965686#comment-13965686 ] ASF subversion and git services commented on CLOUDSTACK-6375: - Commit a8cabf8748a195931d82e9b5807748119c14d31f in cloudstack's branch refs/heads/4.3 from [~frank.zhang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a8cabf8 ] CLOUDSTACK-6375: suppress the prompt while installing openssl 4.3 system vm template job failing in jenkins - Key: CLOUDSTACK-6375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6375 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Abhinandan Prateek Fix For: 4.3.0 4.3 system vm template job failing; looks like build falling after the getting updated openssl 1.0.1e-2+deb7u6. http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm64/140/console (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 24061 files and directories currently installed.) Preparing to replace libssl1.0.0:amd64 1.0.1e-2 (using .../libssl1.0.0_1.0.1e-2+deb7u6_amd64.deb) ... Unpacking replacement libssl1.0.0:amd64 ... Selecting previously unselected package libc-dev-bin. Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package linux-libc-dev:amd64. Unpacking linux-libc-dev:amd64 (from .../linux-libc-dev_3.2.54-2_amd64.deb) ... Selecting previously unselected package libc6-dev:amd64. Unpacking libc6-dev:amd64 (from .../libc6-dev_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package uuid-dev. Unpacking uuid-dev (from .../uuid-dev_2.20.1-5.3_amd64.deb) ... Selecting previously unselected package libapr1-dev. Unpacking libapr1-dev (from .../libapr1-dev_1.4.6-3+deb7u1_amd64.deb) ... Selecting previously unselected package zlib1g-dev:amd64. Unpacking zlib1g-dev:amd64 (from .../zlib1g-dev_1%3a1.2.7.dfsg-13_amd64.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.1e-2+deb7u6_amd64.deb) ... Selecting previously unselected package libtcnative-1. Unpacking libtcnative-1 (from .../libtcnative-1_1.1.24-1_amd64.deb) ... Processing triggers for man-db ... Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u6) ... Checking for services that may need to be restarted...done. Checking init scripts... [?1049h[1;24r[4l[?25l(B[m[37m[40m[1;24r[H[2J[1;1H[1m[37m[44m [2;1H [3;1H [4;1H [5;1H [6;1H [7;1H [8;1H [9;1H [10;1H [11;1H [12;1H [13;1H [14;1H [15;1H [16;1H [17;1H [18;1H [19;1H [20;1H [21;1H [22;1H [23;1H [24;1H [24;79H [4h [4l[1;1H(B[m[37m[44mPackage configuration[4;2H(0[30m[47mlqu(B[m(B[30m[47m [31mConfiguring libssl1.0.0:amd64[30m (0[30m[47mtqk[5;2Hx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m
[jira] [Commented] (CLOUDSTACK-6375) 4.3 system vm template job failing in jenkins
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965784#comment-13965784 ] ASF subversion and git services commented on CLOUDSTACK-6375: - Commit 0965fdb9f8f3cad8629761884eab16b2503cca1a in cloudstack's branch refs/heads/4.3 from [~frank.zhang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0965fdb ] CLOUDSTACK-6375: suppress the prompt while installing libssl 4.3 system vm template job failing in jenkins - Key: CLOUDSTACK-6375 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6375 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: SystemVM Affects Versions: 4.3.0 Reporter: Harikrishna Patnala Assignee: Abhinandan Prateek Fix For: 4.3.0 4.3 system vm template job failing; looks like build falling after the getting updated openssl 1.0.1e-2+deb7u6. http://jenkins.buildacloud.org/view/4.3/job/cloudstack-4.3-systemvm64/140/console (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 24061 files and directories currently installed.) Preparing to replace libssl1.0.0:amd64 1.0.1e-2 (using .../libssl1.0.0_1.0.1e-2+deb7u6_amd64.deb) ... Unpacking replacement libssl1.0.0:amd64 ... Selecting previously unselected package libc-dev-bin. Unpacking libc-dev-bin (from .../libc-dev-bin_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package linux-libc-dev:amd64. Unpacking linux-libc-dev:amd64 (from .../linux-libc-dev_3.2.54-2_amd64.deb) ... Selecting previously unselected package libc6-dev:amd64. Unpacking libc6-dev:amd64 (from .../libc6-dev_2.13-38+deb7u1_amd64.deb) ... Selecting previously unselected package uuid-dev. Unpacking uuid-dev (from .../uuid-dev_2.20.1-5.3_amd64.deb) ... Selecting previously unselected package libapr1-dev. Unpacking libapr1-dev (from .../libapr1-dev_1.4.6-3+deb7u1_amd64.deb) ... Selecting previously unselected package zlib1g-dev:amd64. Unpacking zlib1g-dev:amd64 (from .../zlib1g-dev_1%3a1.2.7.dfsg-13_amd64.deb) ... Selecting previously unselected package libssl-dev. Unpacking libssl-dev (from .../libssl-dev_1.0.1e-2+deb7u6_amd64.deb) ... Selecting previously unselected package libtcnative-1. Unpacking libtcnative-1 (from .../libtcnative-1_1.1.24-1_amd64.deb) ... Processing triggers for man-db ... Setting up libssl1.0.0:amd64 (1.0.1e-2+deb7u6) ... Checking for services that may need to be restarted...done. Checking init scripts... [?1049h[1;24r[4l[?25l(B[m[37m[40m[1;24r[H[2J[1;1H[1m[37m[44m [2;1H [3;1H [4;1H [5;1H [6;1H [7;1H [8;1H [9;1H [10;1H [11;1H [12;1H [13;1H [14;1H [15;1H [16;1H [17;1H [18;1H [19;1H [20;1H [21;1H [22;1H [23;1H [24;1H [24;79H [4h [4l[1;1H(B[m[37m[44mPackage configuration[4;2H(0[30m[47mlqu(B[m(B[30m[47m [31mConfiguring libssl1.0.0:amd64[30m (0[30m[47mtqk[5;2Hx(B[m(B[30m[47m (0[30m[47mx(B[m(B[1m[37m[40m
[jira] [Updated] (CLOUDSTACK-6369) Qcow2's cluster_size option support
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yoshikazu Nojima updated CLOUDSTACK-6369: - Description: To improve the qcow2 performance, it is important to tune parameters of qemu-img create command. preallocation=metadata option, which I am working on in CLOUDSTACK-6191 improves randam IOPS well, but the qcow2 image created with preallocation=metadata option cannot be used for a differential image. This cluster_size option improves IOPS of a differential qcow2 image which is created with preallocation=off. was: To improve the qcow2 performance, it is important to tune parameters of qemu-img create command. preallocation=metadata option, which I am working on in CLOUDSTACK-6191 improves randam IOPS well, but the qcow2 image created with preallocation=metadata option cannot be used as a differential image. This cluster_size option improves IOPS of a differential qcow2 image which is created with preallocation=off. Qcow2's cluster_size option support --- Key: CLOUDSTACK-6369 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6369 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Components: KVM Reporter: Yoshikazu Nojima Assignee: Yoshikazu Nojima Priority: Minor Fix For: Future To improve the qcow2 performance, it is important to tune parameters of qemu-img create command. preallocation=metadata option, which I am working on in CLOUDSTACK-6191 improves randam IOPS well, but the qcow2 image created with preallocation=metadata option cannot be used for a differential image. This cluster_size option improves IOPS of a differential qcow2 image which is created with preallocation=off. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6380) UI: hosts page add new action Disable Host, Enable Host
Jessica Wang created CLOUDSTACK-6380: Summary: UI: hosts page add new action Disable Host, Enable Host Key: CLOUDSTACK-6380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6380 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6380) UI: hosts page add new action Disable Host, Enable Host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965825#comment-13965825 ] Jessica Wang commented on CLOUDSTACK-6380: -- http://bugs-ccp.citrix.com/browse/CS-17969 UI: hosts page add new action Disable Host, Enable Host - Key: CLOUDSTACK-6380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6380 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6380) UI: hosts page add new action Disable Host, Enable Host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965842#comment-13965842 ] ASF subversion and git services commented on CLOUDSTACK-6380: - Commit afcf6d041d9ee5ae0d6c266b7b83d6d52de58884 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=afcf6d0 ] CLOUDSTACK-6380: UI hosts page add new action Disable Host, Enable Host. UI: hosts page add new action Disable Host, Enable Host - Key: CLOUDSTACK-6380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6380 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6380) UI: hosts page add new action Disable Host, Enable Host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965840#comment-13965840 ] ASF subversion and git services commented on CLOUDSTACK-6380: - Commit fc8e79c17b3486b29b72cb2c51d66a606628f0f4 in cloudstack's branch refs/heads/4.4 from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=fc8e79c ] CLOUDSTACK-6380: UI hosts page add new action Disable Host, Enable Host. UI: hosts page add new action Disable Host, Enable Host - Key: CLOUDSTACK-6380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6380 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-6380) UI: hosts page add new action Disable Host, Enable Host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang closed CLOUDSTACK-6380. UI: hosts page add new action Disable Host, Enable Host - Key: CLOUDSTACK-6380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6380 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (CLOUDSTACK-6380) UI: hosts page add new action Disable Host, Enable Host
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang resolved CLOUDSTACK-6380. -- Resolution: Fixed UI: hosts page add new action Disable Host, Enable Host - Key: CLOUDSTACK-6380 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6380 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-6316) [Automation]: Marvin Fixes and new Enhancements
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13965847#comment-13965847 ] ASF subversion and git services commented on CLOUDSTACK-6316: - Commit 94fc4bf6bd110f4ec88bb874e6f2bfb0ff9bc6f6 in cloudstack's branch refs/heads/marvin from SrikanteswaraRao Talluri [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=94fc4bf ] CLOUDSTACK-6316: fixes for bvt failures [Automation]: Marvin Fixes and new Enhancements --- Key: CLOUDSTACK-6316 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6316 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation, marvin Reporter: Santhosh Kumar Edukulla Assignee: Santhosh Kumar Edukulla 1. Earlier, i added a facility called DeleteDataCenter to clean up a datacenter, it has some issues for deleting, fixed them. This change is under deployDataCenter.py 2. Earlier Added a new facility, where we can deploy multiple zones and run regression simultaneously on all zones with multiple hypervisors, 2.1 So, user creates the data center with multiple zones and hypervisors. 2.2 Provides switches like zone and hypervisor to marvinPlugin and all tests are run against that zone. With this patch, added hypervisor switch to nose\marvinplugin. 3. Fixed an issue in one of the test suite under maint, it is using wait_for_vm function, which is not available. 4. Added time taken for async job, post some stress scenarios, we want to collect logs and analyze the time taken for various commands, their jobid and time taken, added time taken facility. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (CLOUDSTACK-6381) IAM -IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed.
Sangeetha Hariharan created CLOUDSTACK-6381: --- Summary: IAM -IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed. Key: CLOUDSTACK-6381 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6381 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: Build from 4.4. Reporter: Sangeetha Hariharan Priority: Critical Fix For: 4.4.0 IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed. Set up: Pre Reqs: Admin - Creates object Domain Admin for d1 - D1 - Creates object - d1 Domain Admin for d1 - D1/D11 User account for d1 - D1/D111 - Creates object - d111a Domain Admin for d1 - D1/D12 Domain Admin for d2 - D2 - Creates object -d2 User Account in domain D1 - userD1-1 - Creates object -d1a User Account in domain D1 - userD1-2 - Creates object - d1b User Account in domain D1/D11 - userD1-a - Creates object - d11a User Account in domain D1/D11 - userD1-a - Creates object - d11b User Account in domain D1/D12- userD1-b - Creates object - d12a User Account in domain D1/D12 - userD-a - Creates object - d12b As domain admin - D1 , i tried to listVistualMachines passing listAll=true parameter (no isrecurssive parameter). Expected result: only all the Vms that belong to this domain should be listed , which should be 3 Vms , d1,d1a and d1b. But I see 8 Vms being returned , which also includes the Vms in the domain, d12 and d111. GET http://10.223.49.6/client/api?command=listVirtualMachineslistAll=trueapiKey=Hv0VKnmBjXhyRMKZ7ixI51gG-iqHqRVTp1xCCLU2-gTnZwhuUNWsa4zZLYZWWLD5lEhvwe05tJKJVa9NeS5REwsignature=cDqQMD6qlKeiz2g40pSOYqJKqoE%3D \n\n ?xml version=1.0 encoding=UTF-8?listvirtualmachinesresponse cloud-stack-version=4.4.0-SNAPSHOTcount8/countvirtualmachineid22193996-12f9-46ff-91cd-3d409f7f8c60/idnamed11a/namedisplaynamed11a/displaynameaccounttestD11A-TestVMList-3385RP/accountdomainid0a0f7c09-2f1a-4939-94ce-88388e197949/domainiddomainD11-UFBXGQ/domaincreated2014-04-10T09:01:37-0400/createdstateRunning/statehaenablefalse/haenablezoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenametemplateide65cdfa0-c019-11e3-907f-4adf980f9414/templateidtemplatenameCentOS 5.3(64-bit) no GUI (Simulator)/templatenametemplatedisplaytextCentOS 5.3(64-bit) no GUI (Simulator)/templatedisplaytextpasswordenabledfalse/passwordenabledserviceofferingid49dee9f8-a49a-414d-b8b2-b0d59b5981f0/serviceofferingidserviceofferingnameSmall Instance/serviceofferingnamecpunumber1/cpunumbercpuspeed100/cpuspeedmemory128/memorycpuused10%/cpuusednetworkkbsread10190848/networkkbsreadnetworkkbswrite5095424/networkkbswriteguestoside5eba5c4-c019-11e3-907f-4adf980f9414/guestosidrootdeviceid0/rootdeviceidrootdevicetypeROOT/rootdevicetypenicida1c079e5-ae0f-4470-b0ed-26895fbcf14d/idnetworkidf1cf7cfb-c354-47c4-854e-af329c54d77e/networkidnetworknametestD11A-TestVMList-3385RP-network/networknamenetmask255.255.255.0/netmaskgateway10.1.1.1/gatewayipaddress10.1.1.217/ipaddressisolationurivlan://1071/isolationuribroadcasturivlan://1071/broadcasturitraffictypeGuest/traffictypetypeIsolated/typeisdefaulttrue/isdefaultmacaddress02:00:06:7b:00:01/macaddress/nichypervisorSimulator/hypervisorisdynamicallyscalablefalse/isdynamicallyscalableostypeid11/ostypeid/virtualmachinevirtualmachineid660a829f-5265-44c3-aa92-957d8bbec8e2/idnamed1a/namedisplaynamed1b/displaynameaccounttestD1B-TestVMList-CB23CT/accountdomainiddc4bf103-27bf-4292-99aa-dc91fa23ee04/domainiddomainD1-NN5QWT/domaincreated2014-04-10T09:01:32-0400/createdstateRunning/statehaenablefalse/haenablezoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenametemplateide65cdfa0-c019-11e3-907f-4adf980f9414/templateidtemplatenameCentOS 5.3(64-bit) no GUI (Simulator)/templatenametemplatedisplaytextCentOS 5.3(64-bit) no GUI (Simulator)/templatedisplaytextpasswordenabledfalse/passwordenabledserviceofferingid49dee9f8-a49a-414d-b8b2-b0d59b5981f0/serviceofferingidserviceofferingnameSmall
[jira] [Updated] (CLOUDSTACK-6381) IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sangeetha Hariharan updated CLOUDSTACK-6381: Summary: IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed. (was: IAM -IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed.) IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed. Key: CLOUDSTACK-6381 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6381 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.4.0 Environment: Build from 4.4. Reporter: Sangeetha Hariharan Priority: Critical Fix For: 4.4.0 IAM - DomainAdmin - When listVirtualMachines is used with listall=true (with out passing isrecursive falg) , all Vms from the subdomain are also listed. Set up: Pre Reqs: Admin - Creates object Domain Admin for d1 - D1 - Creates object - d1 Domain Admin for d1 - D1/D11 User account for d1 - D1/D111 - Creates object - d111a Domain Admin for d1 - D1/D12 Domain Admin for d2 - D2 - Creates object -d2 User Account in domain D1 - userD1-1 - Creates object -d1a User Account in domain D1 - userD1-2 - Creates object - d1b User Account in domain D1/D11 - userD1-a - Creates object - d11a User Account in domain D1/D11 - userD1-a - Creates object - d11b User Account in domain D1/D12- userD1-b - Creates object - d12a User Account in domain D1/D12 - userD-a - Creates object - d12b As domain admin - D1 , i tried to listVistualMachines passing listAll=true parameter (no isrecurssive parameter). Expected result: only all the Vms that belong to this domain should be listed , which should be 3 Vms , d1,d1a and d1b. But I see 8 Vms being returned , which also includes the Vms in the domain, d12 and d111. GET http://10.223.49.6/client/api?command=listVirtualMachineslistAll=trueapiKey=Hv0VKnmBjXhyRMKZ7ixI51gG-iqHqRVTp1xCCLU2-gTnZwhuUNWsa4zZLYZWWLD5lEhvwe05tJKJVa9NeS5REwsignature=cDqQMD6qlKeiz2g40pSOYqJKqoE%3D \n\n ?xml version=1.0 encoding=UTF-8?listvirtualmachinesresponse cloud-stack-version=4.4.0-SNAPSHOTcount8/countvirtualmachineid22193996-12f9-46ff-91cd-3d409f7f8c60/idnamed11a/namedisplaynamed11a/displaynameaccounttestD11A-TestVMList-3385RP/accountdomainid0a0f7c09-2f1a-4939-94ce-88388e197949/domainiddomainD11-UFBXGQ/domaincreated2014-04-10T09:01:37-0400/createdstateRunning/statehaenablefalse/haenablezoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenametemplateide65cdfa0-c019-11e3-907f-4adf980f9414/templateidtemplatenameCentOS 5.3(64-bit) no GUI (Simulator)/templatenametemplatedisplaytextCentOS 5.3(64-bit) no GUI (Simulator)/templatedisplaytextpasswordenabledfalse/passwordenabledserviceofferingid49dee9f8-a49a-414d-b8b2-b0d59b5981f0/serviceofferingidserviceofferingnameSmall Instance/serviceofferingnamecpunumber1/cpunumbercpuspeed100/cpuspeedmemory128/memorycpuused10%/cpuusednetworkkbsread10190848/networkkbsreadnetworkkbswrite5095424/networkkbswriteguestoside5eba5c4-c019-11e3-907f-4adf980f9414/guestosidrootdeviceid0/rootdeviceidrootdevicetypeROOT/rootdevicetypenicida1c079e5-ae0f-4470-b0ed-26895fbcf14d/idnetworkidf1cf7cfb-c354-47c4-854e-af329c54d77e/networkidnetworknametestD11A-TestVMList-3385RP-network/networknamenetmask255.255.255.0/netmaskgateway10.1.1.1/gatewayipaddress10.1.1.217/ipaddressisolationurivlan://1071/isolationuribroadcasturivlan://1071/broadcasturitraffictypeGuest/traffictypetypeIsolated/typeisdefaulttrue/isdefaultmacaddress02:00:06:7b:00:01/macaddress/nichypervisorSimulator/hypervisorisdynamicallyscalablefalse/isdynamicallyscalableostypeid11/ostypeid/virtualmachinevirtualmachineid660a829f-5265-44c3-aa92-957d8bbec8e2/idnamed1a/namedisplaynamed1b/displaynameaccounttestD1B-TestVMList-CB23CT/accountdomainiddc4bf103-27bf-4292-99aa-dc91fa23ee04/domainiddomainD1-NN5QWT/domaincreated2014-04-10T09:01:32-0400/createdstateRunning/statehaenablefalse/haenablezoneid75d61334-ff70-49c3-99ed-3af702cd51d7/zoneidzonenameBLR1/zonenametemplateide65cdfa0-c019-11e3-907f-4adf980f9414/templateidtemplatenameCentOS 5.3(64-bit) no GUI (Simulator)/templatenametemplatedisplaytextCentOS 5.3(64-bit) no GUI
[jira] [Updated] (CLOUDSTACK-5907) KVM/CLVM volumes are shown as Ovm hypervisor
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tanner Danzey updated CLOUDSTACK-5907: -- Attachment: storage2.png storage1.png Please reopen, this bug is present in 4.3.0 that was released recently with KVM hypervisors RBD primary storage. KVM/CLVM volumes are shown as Ovm hypervisor Key: CLOUDSTACK-5907 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5907 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, KVM, Oracle VM (OVM), Storage Controller, UI Affects Versions: 4.2.1, 4.3.0 Environment: KVM, CLVM Reporter: Nux Labels: clvm, kvm, ovm, storage Attachments: storage1.png, storage2.png It looks like ACS is showing KVM volumes on CLVM primary storage as being for Oracle hypervisor. http://i.imgur.com/E4InCV2.png The API shows the same so it's not a UI glitch. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-5785) VM display name cell not updated upon detaching volume from VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Suich reassigned CLOUDSTACK-5785: --- Assignee: Chris Suich VM display name cell not updated upon detaching volume from VM -- Key: CLOUDSTACK-5785 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5785 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Mac OS X 10.8.3 Chrome 31.0.1650.63 Reporter: Mike Tutkowski Assignee: Chris Suich Fix For: 4.4.0 Attachments: Detach Volume.png In the Storage tab of the GUI, I detached a volume from a VM. The process was successful; however, the GUI did not update properly. After the detach has completed, the VM display name cell in the appropriate row should be empty, but I noticed it still contained the name of the VM the volume was attached to. I have included a screen shot. One point of note is that the GUI seems to update just fine when attaching a volume to a VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5785) VM display name cell not updated upon detaching volume from VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966144#comment-13966144 ] ASF subversion and git services commented on CLOUDSTACK-5785: - Commit 68ec715d85092e0a66e7228d1c76ced069fb69c3 in cloudstack's branch refs/heads/4.4 from [~csuich2] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=68ec715 ] CLOUDSTACK-5785: VM display name cell not updated upon detaching volume from VM VM display name cell not updated upon detaching volume from VM -- Key: CLOUDSTACK-5785 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5785 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Mac OS X 10.8.3 Chrome 31.0.1650.63 Reporter: Mike Tutkowski Assignee: Chris Suich Fix For: 4.4.0 Attachments: Detach Volume.png In the Storage tab of the GUI, I detached a volume from a VM. The process was successful; however, the GUI did not update properly. After the detach has completed, the VM display name cell in the appropriate row should be empty, but I noticed it still contained the name of the VM the volume was attached to. I have included a screen shot. One point of note is that the GUI seems to update just fine when attaching a volume to a VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (CLOUDSTACK-5785) VM display name cell not updated upon detaching volume from VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966145#comment-13966145 ] ASF subversion and git services commented on CLOUDSTACK-5785: - Commit ea29adb7b96d31a07f6528c79f57847a43175966 in cloudstack's branch refs/heads/master from [~csuich2] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ea29adb ] CLOUDSTACK-5785: VM display name cell not updated upon detaching volume from VM VM display name cell not updated upon detaching volume from VM -- Key: CLOUDSTACK-5785 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5785 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Mac OS X 10.8.3 Chrome 31.0.1650.63 Reporter: Mike Tutkowski Assignee: Chris Suich Fix For: 4.4.0 Attachments: Detach Volume.png In the Storage tab of the GUI, I detached a volume from a VM. The process was successful; however, the GUI did not update properly. After the detach has completed, the VM display name cell in the appropriate row should be empty, but I noticed it still contained the name of the VM the volume was attached to. I have included a screen shot. One point of note is that the GUI seems to update just fine when attaching a volume to a VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (CLOUDSTACK-5785) VM display name cell not updated upon detaching volume from VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Suich updated CLOUDSTACK-5785: Status: Reviewable (was: In Progress) VM display name cell not updated upon detaching volume from VM -- Key: CLOUDSTACK-5785 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5785 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Mac OS X 10.8.3 Chrome 31.0.1650.63 Reporter: Mike Tutkowski Assignee: Chris Suich Fix For: 4.4.0 Attachments: Detach Volume.png In the Storage tab of the GUI, I detached a volume from a VM. The process was successful; however, the GUI did not update properly. After the detach has completed, the VM display name cell in the appropriate row should be empty, but I noticed it still contained the name of the VM the volume was attached to. I have included a screen shot. One point of note is that the GUI seems to update just fine when attaching a volume to a VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (CLOUDSTACK-5785) VM display name cell not updated upon detaching volume from VM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Suich reassigned CLOUDSTACK-5785: --- Assignee: Mike Tutkowski (was: Chris Suich) Hey Mike, this issue should be fixed. Can you verify it for me. VM display name cell not updated upon detaching volume from VM -- Key: CLOUDSTACK-5785 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5785 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: UI Affects Versions: 4.3.0 Environment: Mac OS X 10.8.3 Chrome 31.0.1650.63 Reporter: Mike Tutkowski Assignee: Mike Tutkowski Fix For: 4.4.0 Attachments: Detach Volume.png In the Storage tab of the GUI, I detached a volume from a VM. The process was successful; however, the GUI did not update properly. After the detach has completed, the VM display name cell in the appropriate row should be empty, but I noticed it still contained the name of the VM the volume was attached to. I have included a screen shot. One point of note is that the GUI seems to update just fine when attaching a volume to a VM. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (CLOUDSTACK-4217) ceph:addprimary storage is failed with exception(documentation is not clear)
[
https://issues.apache.org/jira/browse/CLOUDSTACK-4217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wido den Hollander closed CLOUDSTACK-4217.
--
Resolution: Fixed
I'm going to close this one since I think it's documented well right now.
The UI might need a little bit of extra work, but I think that what's in there
now is sufficient.
ceph:addprimary storage is failed with exception(documentation is not clear)
Key: CLOUDSTACK-4217
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4217
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc, Management Server
Affects Versions: 4.2.0
Reporter: sadhu suresh
Assignee: Wido den Hollander
Priority: Minor
Steps:
1.created and configured the ceph cluster.
2. Install cloudstack agent on ubuntu13.4 and add it in the cloud-stack's
kVM cluster
3. Install librdos package on kvm host and also install ceph-common pakage
4. able to create the image from kvm host using qemu-img command
root@Rack1Pod1Host21:/etc/ceph# qemu-img create -f rbd rbd:data/foo 1G
Formatting 'rbd:data/foo', fmt=rbd size=1073741824 cluster_size=0
5.try to create a primay storage by selecting the rbd as protocol and
provinding cpeh cluster details
Actual result:
Addprimary storage failed with delete storagepool failed error and log
shows intially createstoragepool command successful and fail to access the
storage pool.
Agent.log:
:{_command:{hostType:Routing,hostId:7,wait:0},result:true,wait:0}}]
}
2013-08-09 22:13:16,905 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Processing command:
com.cloud.agent.api.GetHostStatsCommand
2013-08-09 22:13:16,905 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Executing: /bin/bash -c idle=$(top -b -n 1|grep
Cpu\(s\):|cut -d% -f4|cut -d, -f2);echo $idle
2013-08-09 22:13:17,069 DEBUG [kvm.resource.LibvirtComputingResource]
(agentRequest-Handler-3:null) Execution is successful.
2013-08-09 22:13:17,070 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-3:null) Seq 7-1066205442: { Ans: , MgmtId:
7296881000534, via: 7, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:false,details:empty
String,wait:0}}] }
2013-08-09 22:13:52,969 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:null) Request:Seq 7-1066205443: { Cmd , MgmtId:
7296881000534, via: 7, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.CreateStoragePoolCommand:{add:true,pool:{id:19,uuid:2cd21530-1fb9-3aff-95bc-ba3b3b3f2b12,host:10.147.41.3,path:data,userInfo:ceph:QVFCVjdBRlNzTG1aRUJBQW1HaXZBay9CVjFpTXZjYVJIUWZpWGc9PQ==,port:6789,type:RBD},localPath:/mnt//ed2dce31-1512-366e-84a8-a296cc5768f0,wait:0}}]
}
2013-08-09 22:13:52,969 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:null) Processing command:
com.cloud.agent.api.CreateStoragePoolCommand
2013-08-09 22:13:52,969 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-4:null) Seq 7-1066205443: { Ans: , MgmtId:
7296881000534, via: 7, Ver: v1, Flags: 10,
[{com.cloud.agent.api.Answer:{result:true,details:success,wait:0}}]
}
2013-08-09 22:13:53,019 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-5:null) Request:Seq 7-1066205444: { Cmd , MgmtId:
7296881000534, via: 7, Ver: v1, Flags: 100011,
[{com.cloud.agent.api.ModifyStoragePoolCommand:{add:true,pool:{id:19,uuid:2cd21530-1fb9-3aff-95bc-ba3b3b3f2b12,host:10.147.41.3,path:data,userInfo:ceph:QVFCVjdBRlNzTG1aRUJBQW1HaXZBay9CVjFpTXZjYVJIUWZpWGc9PQ==,port:6789,type:RBD},localPath:/mnt//ed2dce31-1512-366e-84a8-a296cc5768f0,wait:0}}]
}
2013-08-09 22:13:53,020 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-5:null) Processing command:
com.cloud.agent.api.ModifyStoragePoolCommand
2013-08-09 22:13:53,022 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-5:null) createStoragePool didn't find existing running
pool: org.libvirt.LibvirtException: Storage pool not found: no storage pool
with matching uuid ,�^U0^_�:����;;?+^R, need to create it
2013-08-09 22:13:53,022 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-5:null) Didn't find an existing storage pool
2cd21530-1fb9-3aff-95bc-ba3b3b3f2b12 by UUID, checking for pools with
duplicate paths
2013-08-09 22:13:53,025 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-5:null) Checking path of existing pool
99e0dae1-1ac8-46fa-a23e-20938b543c25 against pool we want to create
2013-08-09 22:13:53,029 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-5:null) Attempting to create storage pool
2cd21530-1fb9-3aff-95bc-ba3b3b3f2b12
2013-08-09 22:13:53,029 DEBUG [kvm.storage.LibvirtStorageAdaptor]
(agentRequest-Handler-5:null)
[jira] [Updated] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada updated CLOUDSTACK-6382:
-
Fix Version/s: 4.4.0
System VM's failing to start with XenServer 6.2.5
-
Key: CLOUDSTACK-6382
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6382
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Blocker
Fix For: 4.4.0
Steps:
Build : 4.4
Configure Adv zone with XenServer 6.2.5
Observation:
System VM’s are failing to start with below exception and there are lot of
SR’s that got added to XenServer .
2014-04-10 16:09:42,622 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-4:job-4/job-22 ctx-4609aa64) Seq 1-8947526559678332946:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-10), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/1/1/,origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
Template
(XenServer),imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.102.192.101/Sailaja/gpuss1,_role:Image}},name:routing-1,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
Template
(XenServer),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:0a336642-b7d7-3262-ae46-8f06ccdf8c30,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/gpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/gpups1/?ROLE=PrimarySTOREUUID=0a336642-b7d7-3262-ae46-8f06ccdf8c30}},name:routing-1,hypervisorType:XenServer}},executeInSequence:false,options:{},wait:10800}}]
}
2014-04-10 16:09:42,624 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) template 1 is already in
store:1, type:Primary
2014-04-10 16:09:42,627 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Found template routing-1 in
storage pool 1 with VMTemplateStoragePool id: 2
2014-04-10 16:09:42,630 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-13:ctx-d982de4d) Seq 1-8947526559678332946: Executing request
2014-04-10 16:09:42,654 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Acquire lock on
VMTemplateStoragePool 2 with timeout 3600 seconds
2014-04-10 16:09:42,657 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is not done uuid:
b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Apr 10 21:30:06 IST 2014
finished: Thu Jan 01 05:30:00 IST 1970
status: pending
residentOn: com.xensource.xenapi.Host@514ac968
progress: 0.0
type: none/
result:
errorInfo: []
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-04-10 16:09:42,660 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is not done uuid:
b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Apr 10 21:30:06 IST 2014
finished: Thu Jan 01 05:30:00 IST 1970
status: pending
residentOn: com.xensource.xenapi.Host@514ac968
progress: 0.0
type: none/
result:
errorInfo: []
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is done success
2014-04-10 16:09:43,676 DEBUG [c.c.h.x.r.XenServerStorageProcessor]
(DirectAgent-13:ctx-d982de4d) Failed to destroy pbd
2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is done success
2014-04-10 16:09:43,676 DEBUG [c.c.h.x.r.XenServerStorageProcessor]
(DirectAgent-13:ctx-d982de4d) Failed to
[jira] [Created] (CLOUDSTACK-6382) System VM's failing to start with XenServer 6.2.5
Sailaja Mada created CLOUDSTACK-6382:
Summary: System VM's failing to start with XenServer 6.2.5
Key: CLOUDSTACK-6382
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6382
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: XenServer
Affects Versions: 4.4.0
Reporter: Sailaja Mada
Priority: Blocker
Steps:
Build : 4.4
Configure Adv zone with XenServer 6.2.5
Observation:
System VM’s are failing to start with below exception and there are lot of SR’s
that got added to XenServer .
2014-04-10 16:09:42,622 DEBUG [c.c.a.t.Request]
(Work-Job-Executor-4:job-4/job-22 ctx-4609aa64) Seq 1-8947526559678332946:
Executing: { Cmd , MgmtId: 55355881446856, via: 1(cldstk-R720-10), Ver: v1,
Flags: 100011,
[{org.apache.cloudstack.storage.command.CopyCommand:{srcTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{path:template/tmpl/1/1/,origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
Template
(XenServer),imageDataStore:{com.cloud.agent.api.to.NfsTO:{_url:nfs://10.102.192.101/Sailaja/gpuss1,_role:Image}},name:routing-1,hypervisorType:XenServer}},destTO:{org.apache.cloudstack.storage.to.TemplateObjectTO:{origUrl:http://download.cloud.com/templates/4.3/systemvm64template-2014-01-14-master-xen.vhd.bz2,uuid:dc8561e0-c097-11e3-8b80-32588ba65dc8,id:1,format:VHD,accountId:1,checksum:74b92f031cc5c2089ee89efb81344dcf,hvm:false,displayText:SystemVM
Template
(XenServer),imageDataStore:{org.apache.cloudstack.storage.to.PrimaryDataStoreTO:{uuid:0a336642-b7d7-3262-ae46-8f06ccdf8c30,id:1,poolType:NetworkFilesystem,host:10.102.192.101,path:/Sailaja/gpups1,port:2049,url:NetworkFilesystem://10.102.192.101/Sailaja/gpups1/?ROLE=PrimarySTOREUUID=0a336642-b7d7-3262-ae46-8f06ccdf8c30}},name:routing-1,hypervisorType:XenServer}},executeInSequence:false,options:{},wait:10800}}]
}
2014-04-10 16:09:42,624 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) template 1 is already in
store:1, type:Primary
2014-04-10 16:09:42,627 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Found template routing-1 in
storage pool 1 with VMTemplateStoragePool id: 2
2014-04-10 16:09:42,630 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-13:ctx-d982de4d) Seq 1-8947526559678332946: Executing request
2014-04-10 16:09:42,654 DEBUG [o.a.c.s.v.VolumeServiceImpl]
(Work-Job-Executor-3:job-3/job-21 ctx-2fcd2f5f) Acquire lock on
VMTemplateStoragePool 2 with timeout 3600 seconds
2014-04-10 16:09:42,657 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is not done uuid:
b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Apr 10 21:30:06 IST 2014
finished: Thu Jan 01 05:30:00 IST 1970
status: pending
residentOn: com.xensource.xenapi.Host@514ac968
progress: 0.0
type: none/
result:
errorInfo: []
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-04-10 16:09:42,660 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is not done uuid:
b27d0997-2490-816a-b762-91cdf1ddc047
nameLabel: Async.host.call_plugin
nameDescription:
allowedOperations: []
currentOperations: {}
created: Thu Apr 10 21:30:06 IST 2014
finished: Thu Jan 01 05:30:00 IST 1970
status: pending
residentOn: com.xensource.xenapi.Host@514ac968
progress: 0.0
type: none/
result:
errorInfo: []
otherConfig: {}
subtaskOf: com.xensource.xenapi.Task@aaf13f6f
subtasks: []
2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is done success
2014-04-10 16:09:43,676 DEBUG [c.c.h.x.r.XenServerStorageProcessor]
(DirectAgent-13:ctx-d982de4d) Failed to destroy pbd
2014-04-10 16:09:42,916 DEBUG [c.c.h.x.r.XenServer620Resource]
(DirectAgent-13:ctx-d982de4d) Task is done success
2014-04-10 16:09:43,676 DEBUG [c.c.h.x.r.XenServerStorageProcessor]
(DirectAgent-13:ctx-d982de4d) Failed to destroy pbd
SR_BACKEND_FAILURE_40The SR scan failed [opterr=['INTERNAL_ERROR',
'Db_exn.Uniqueness_constraint_violation(VDI, uuid,
70e21c84-cfe2-4af3-9a26-64e3d939cda6)']]
at com.xensource.xenapi.Types.checkResponse(Types.java:2006)
at
[jira] [Commented] (CLOUDSTACK-5259) Xenserver - Not able to create template from snapshot.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-5259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13966209#comment-13966209
]
ASF subversion and git services commented on CLOUDSTACK-5259:
-
Commit ee0254352b3894f14cb11e5cc688f57405935ee3 in cloudstack's branch
refs/heads/4.2 from [~aprateek]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=ee02543 ]
CLOUDSTACK-5259: added 32 bit support for vhd-util
Xenserver - Not able to create template from snapshot.
---
Key: CLOUDSTACK-5259
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5259
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Management Server
Affects Versions: 4.3.0
Environment: Build from 4.3
Reporter: Sangeetha Hariharan
Assignee: Abhinandan Prateek
Priority: Critical
Fix For: 4.3.0
Attachments: management-server.rar, xen1-2.rar, xen1.rar, xen2.rar
Xenserver - Not able to create template from snapshot.
Steps to reproduce the problem:
Set up - Advanced zone with Xenserver 6.2
Created hourly recurring snapshot.
Create a template from snapshot.
Template creation fails with the following exception:
Failed to create
template/usr/local/cloud/systemvm/scripts/storage/secondary/create_privatetemplate_from_snapshot_xen.sh:
line 65: /bin/vhd-util: No such file or directory30#failed to query
/mnt/SecStorage/8d6190f7-3fc3-3a66-8a8c-bd8e50f2bbc6/snapshots/9/89/a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
We see the following vhd file exist in the secondary store.
root@nfs3 89]# pwd
/export/home/sangeetha/felton/xen/secondary/snapshots/9/89
[root@nfs3 89]# ls -ltr
total 2579628
-rw-r--r-- 1 root root 7186309632 Nov 22 15:42
8546a63f-dc01-4348-babc-c34c138579c7.vhd
-rw-r--r-- 1 root root 155537920 Nov 22 16:36
9d1404ca-c97e-4f6b-a1a4-3bb5fb1d3900.vhd
-rw-r--r-- 1 root root 229081600 Nov 24 18:52
0323b0cb-446e-4550-a443-d135c4a960b8.vhd
-rw-r--r-- 1 root root 75690496 Nov 24 19:35
e440d533-c5cf-464c-940a-505d5b0108c4.vhd
-rw-r--r-- 1 root root 81994240 Nov 24 20:35
53f884fb-cd9c-4c35-bcf1-b90f3ce0ea5f.vhd
-rw-r--r-- 1 root root 81994240 Nov 24 21:35
8ad156ad-e63f-44e1-a8ad-7bcc8acd0b26.vhd
-rw-r--r-- 1 root root 79892992 Nov 24 22:35
2781b5af-7c92-482c-8775-f331c7df9b2b.vhd
-rw-r--r-- 1 root root 75690496 Nov 24 23:35
a2c06f0c-92e4-41b2-a4cb-7d1675146111.vhd
-rw-r--r-- 1 root root 81994240 Nov 25 00:35
3bd9fe33-ce59-4148-825f-f9e75e56d088.vhd
-rw-r--r-- 1 root root 81994240 Nov 25 01:35
ab414c2b-ed16-4ee2-b3f8-d17b5075fe8d.vhd
-rw-r--r-- 1 root root 81994240 Nov 25 02:35
cdd97481-d32d-4350-aaae-0a2132c2d934.vhd
-rw-r--r-- 1 root root 81994240 Nov 25 03:35
1d82a5a0-1a75-44f3-8a27-dffcf1127b62.vhd
-rw-r--r-- 1 root root 81994240 Nov 25 04:35
061043e7-9c22-404c-88e5-183ab4590f5e.vhd
-rw-r--r-- 1 root root 81994240 Nov 25 05:35
f82e0d43-e83b-493b-b953-6f06a94a369b.vhd
-rw-r--r-- 1 root root 84095488 Nov 25 06:35
6c0065ad-9fc0-4ce6-957c-0475153c2ed4.vhd
[root@nfs3 89]#
Management server logs:
2013-11-25 13:01:43,109 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) submit async job-726, details:
AsyncJobVO {id:726, userI
d: 2, accountId: 2, instanceType: Template, instanceId: 204, cmd:
org.apache.cloudstack.api.command.user.template.CreateTemplateCmd, cmdInfo:
{sessionkey:2I2cmFDP
FQyACWMGWW8h54MGdC0\u003d,cmdEventType:TEMPLATE.CREATE,ctxUserId:2,httpmethod:GET,osTypeId:e7460654-52fe-11e3-821d-665544288891,isPublic:true,i
sdynamicallyscalable:false,response:json,id:204,displayText:temp99,snapshotid:b6e507c5-3758-458f-bc98-01e69e2402b0,passwordEnabled:false,name
:temp99,_:1385402509285,ctxAccountId:2,ctxStartEventId:21369},
cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0, result:
null, init
Msid: 112516401760401, completeMsid: null, lastUpdated: null, lastPolled:
null, created: null}
2013-11-25 13:01:43,110 DEBUG [c.c.a.ApiServlet]
(catalina-exec-15:ctx-8576afd8 ctx-2f9b87f6) ===END=== 10.215.3.7 -- GET
command=createTemplateresponse=jsonsess
ionkey=2I2cmFDPFQyACWMGWW8h54MGdC0%3Dsnapshotid=b6e507c5-3758-458f-bc98-01e69e2402b0name=temp99displayText=temp99osTypeId=e7460654-52fe-11e3-821d-665544288891is
Public=truepasswordEnabled=falseisdynamicallyscalable=false_=1385402509285
2013-11-25 13:01:43,127 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl]
(Job-Executor-105:ctx-d53e3263 ctx-2f9b87f6) template 204 is already in
store:1, type:Image
2013-11-25 13:01:43,134 DEBUG [o.a.c.s.m.AncientDataMotionStrategy]
(Job-Executor-105:ctx-d53e3263 ctx-2f9b87f6) copyAsync inspecting src type
SNAPSHOT
