[jira] [Commented] (CLOUDSTACK-9518) test_01_test_vm_volume_snapshot Smoke Test Fails
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541934#comment-15541934
]
Abhinandan Prateek commented on CLOUDSTACK-9518:
As per code this failure seems to be by design:
The marvin test is taking a VM snapshot followed by snapshot of root volume.
There is a check "// Check that Vm to which this volume is attached does not
have VM Snapshots".
As per specs
https://cwiki.apache.org/confluence/display/CLOUDSTACK/VM+Snapshots , only
concurrent snapshotting is not allowed.
Below is the commit that placed that restriction:
commit a4d8215ebba6009fc4b17ef7b61ff51238f0f404
Author: Anshul Gangwar
Date: Thu Oct 9 10:37:21 2014 +0530
CLOUDSTACK-7688, CLOUDSTACK-7747: restricted various operations for VM with
VM snapshots which breaks VM snapshots.
Now they are informed that they cannot perform the operation.
To perform operation they have to remove VM snapshots of VM.
> test_01_test_vm_volume_snapshot Smoke Test Fails
>
>
> Key: CLOUDSTACK-9518
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9518
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: mavin
>Affects Versions: 4.8.1
> Environment: CentOS 7.2 + VMware 5.5u3 + NFS Primary/Secondary Storage
> CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary Storage
>Reporter: John Burwell
>Assignee: Abhinandan Prateek
>Priority: Critical
> Labels: 4.8.2.0-smoke-test-failure
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
> Attachments: test_vm_snapshots.py.xml
>
>
> The {{test_01_test_vm_volume_snapshot}} test case in the {{test_vm_snapshot}}
> is failing with the following error:
> {code}
> 2016-09-28 00:33:18,076 - CRITICAL - EXCEPTION:
> test_01_test_vm_volume_snapshot: ['Traceback (most recent call last):\n', '
> File "/u sr/lib64/python2.7/unittest/case.py", line 369, in run\n
> testMethod()\n', ' File "/marvin/tests/smoke/test_vm_snapshots.py", line
> 399, in test_01_test_vm_volume_snapshot\n
> domainid=self.account.domainid\n', ' File
> "/usr/lib/python2.7/site-packages/marvin/lib/base.py", l ine 1106, in
> create\nreturn Snapshot(apiclient.createSnapshot(cmd).__dict__)\n', '
> File "/usr/lib/python2.7/site-packages/marvin/cloud
> stackAPI/cloudstackAPIClient.py", line 3102, in createSnapshot\nresponse
> = self.connection.marvinRequest(command, response_type=respons e,
> method=method)\n', ' File
> "/usr/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 379,
> in marvinRequest\nraise e\n' , 'CloudstackAPIException: Execute cmd:
> createsnapshot failed, due to: errorCode: 431, errorText:Volume snapshot is
> not allowed, please det ach it from VM with VM Snapshots\n']
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-8353) Including windows guest performance improvement flags like hv_vapic and hv_spinlock in CCP
[ https://issues.apache.org/jira/browse/CLOUDSTACK-8353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542022#comment-15542022 ] Andrija Panic commented on CLOUDSTACK-8353: --- Guys, any progress on this ? We are on 4.5.1, and 1 major customer is regularyy affected with BSOD on Windows 2008 R2. Not sure what to do, or what a workarround would be - they have many, many servers, and its impossible to quickly upgrade to Windows 2012 R2 (which works fine) Any ideas, comments, please ? > Including windows guest performance improvement flags like hv_vapic and > hv_spinlock in CCP > -- > > Key: CLOUDSTACK-8353 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8353 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: KVM >Affects Versions: 4.5.0 >Reporter: Bharat Kumar >Assignee: Bharat Kumar > > There is a bug in KVM that causes a BSOD for Windows 2008 R2 and 7 or > earlier. fix was added in libvirt 1.1.1 The fix requires enabling the > "hv_relaxed" option for the affected VMs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajani Karuturi resolved CLOUDSTACK-9364. - Resolution: Fixed > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9524) Some marvin tests don't check hypervisor before executing ssh into VR
Rohit Yadav created CLOUDSTACK-9524: --- Summary: Some marvin tests don't check hypervisor before executing ssh into VR Key: CLOUDSTACK-9524 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9524 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Rohit Yadav Assignee: Rohit Yadav Fix For: Future, 4.10.0.0, 4.9.1.0, 4.8.2.0 Some marvin tests dont' check router hypervisor, before trying to ssh to VR by ssh into mgmt server first and then using the default ssh keys. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9525) add support for windows 10 guest os in xenserver 6.5
Rajani Karuturi created CLOUDSTACK-9525: --- Summary: add support for windows 10 guest os in xenserver 6.5 Key: CLOUDSTACK-9525 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9525 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Reporter: Rajani Karuturi Assignee: Rajani Karuturi -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9525) add support for windows 10 guest os in xenserver 6.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542098#comment-15542098 ] ASF GitHub Bot commented on CLOUDSTACK-9525: GitHub user karuturi opened a pull request: https://github.com/apache/cloudstack/pull/1698 CLOUDSTACK-9525 add support for windows 10 added guest_os and guest_os_hypervisor mappings for windows10 and xenserver 6.5.0 You can merge this pull request into a Git repository by running: $ git pull https://github.com/karuturi/cloudstack CLOUDSTACK-9525 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1698.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1698 commit d2e151dada803c12883a01cd8225f6c2a74ffa94 Author: Rajani Karuturi Date: 2016-10-03T10:29:00Z CLOUDSTACK-9525 add support for windows 10 guest os in xenserver 6.5.0 > add support for windows 10 guest os in xenserver 6.5 > > > Key: CLOUDSTACK-9525 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9525 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9526) Marvin test_deploy_vgpu_enabled_vm.py - Fix a hardcoded username and password
Boris Stoyanov created CLOUDSTACK-9526:
--
Summary: Marvin test_deploy_vgpu_enabled_vm.py - Fix a hardcoded
username and password
Key: CLOUDSTACK-9526
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9526
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: marvin
Affects Versions: 4.10.0.0, 4.9.1.0, 4.8.2.0
Reporter: Boris Stoyanov
Looks like another password issue with this test
{code}
AuthenticationException: Authentication failed.
Trying SSH Connection: Host:10.2.2.38 User:root
Port:22 RetryCnt:57===
SshClient: Exception under createConnection: ['Traceback (most recent call
last):\n', ' File "/usr/lib/python2.7/site-packages/marvin/sshClient.py", line
121, in createConnection\ntimeout=self.timeout)\n', ' File
"/usr/lib/python2.7/site-packages/paramiko/client.py", line 380, in connect\n
look_for_keys, gss_auth, gss_kex, gss_deleg_creds, gss_host)\n', ' File
"/usr/lib/python2.7/site-packages/paramiko/client.py", line 603, in _auth\n
raise saved_exception\n', 'AuthenticationException: Authentication failed.\n']
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/marvin/sshClient.py", line 121, in
createConnection{code}
{code}[root@trl-97-x-cs48-bstoyanov-marvin ~]# cat
/marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py |grep testdata
self.testdata = self.testClient.getParsedTestDataConfig()
port=self.testdata['configurableData']['host']["publicport"],
user=self.testdata['configurableData']['host']["username"],
passwd=self.testdata['configurableData']['host']["password"]){code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9526) Marvin test_deploy_vgpu_enabled_vm.py - Fix a hardcoded username and password
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Stoyanov resolved CLOUDSTACK-9526.
Resolution: Fixed
Fixed with https://github.com/apache/cloudstack/pull/1692
> Marvin test_deploy_vgpu_enabled_vm.py - Fix a hardcoded username and password
> -
>
> Key: CLOUDSTACK-9526
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9526
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: marvin
>Affects Versions: 4.10.0.0, 4.9.1.0, 4.8.2.0
>Reporter: Boris Stoyanov
>
> Looks like another password issue with this test
> {code}
> AuthenticationException: Authentication failed.
> Trying SSH Connection: Host:10.2.2.38 User:root
> Port:22 RetryCnt:57===
> SshClient: Exception under createConnection: ['Traceback (most recent call
> last):\n', ' File "/usr/lib/python2.7/site-packages/marvin/sshClient.py",
> line 121, in createConnection\ntimeout=self.timeout)\n', ' File
> "/usr/lib/python2.7/site-packages/paramiko/client.py", line 380, in connect\n
>look_for_keys, gss_auth, gss_kex, gss_deleg_creds, gss_host)\n', ' File
> "/usr/lib/python2.7/site-packages/paramiko/client.py", line 603, in _auth\n
> raise saved_exception\n', 'AuthenticationException: Authentication
> failed.\n']
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/marvin/sshClient.py", line 121, in
> createConnection{code}
> {code}[root@trl-97-x-cs48-bstoyanov-marvin ~]# cat
> /marvin/tests/smoke/test_deploy_vgpu_enabled_vm.py |grep testdata
> self.testdata = self.testClient.getParsedTestDataConfig()
>
> port=self.testdata['configurableData']['host']["publicport"],
>
> user=self.testdata['configurableData']['host']["username"],
>
> passwd=self.testdata['configurableData']['host']["password"]){code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9524) Some marvin tests don't check hypervisor before executing ssh into VR
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rohit Yadav updated CLOUDSTACK-9524: Status: Reviewable (was: In Progress) > Some marvin tests don't check hypervisor before executing ssh into VR > - > > Key: CLOUDSTACK-9524 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9524 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > Some marvin tests dont' check router hypervisor, before trying to ssh to VR > by ssh into mgmt server first and then using the default ssh keys. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9071) stats.output.uri stops the server from starting if the uri is malformed
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542334#comment-15542334 ] ASF GitHub Bot commented on CLOUDSTACK-9071: Github user wido commented on the issue: https://github.com/apache/cloudstack/pull/1673 @jburwell You need to configure the management server with Graphite enabled with a wrongly entered URI to trigger this bug. This is a manual error when somebody gives in a wrongly formed URL. The Graphite output was not broken by default. > stats.output.uri stops the server from starting if the uri is malformed > --- > > Key: CLOUDSTACK-9071 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9071 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.6.0 >Reporter: Carles Figuerola > > After inputting a malformed uri (was missing the graphite://) and restarting > the management service, the application stops at: > 2015-11-17 11:06:42,861 INFO [c.c.s.StatsCollector] > (localhost-startStop-1:null) metrics.dev.company.net is not a valid protocol > for external statistics. No statistics will be send. > No more logs are output and tomcat is up but serving a completely blank page. > When the uri has this form: (graphite://metrics.dev.company.net:2013), the > end result is very similar to the previous one > (also, the last word should be "sent") -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542424#comment-15542424 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 Travis issue? > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542428#comment-15542428
]
ASF GitHub Bot commented on CLOUDSTACK-9504:
Github user jburwell commented on the issue:
https://github.com/apache/cloudstack/pull/1642
@mike-tutkowski The Travis build is failing with the following error:
```
0.04s$ ./tools/travis/script.sh ${TESTS}
Running tests: smoke/test_usage_events smoke/test_vm_life_cycle
smoke/test_vm_snapshots smoke/test_volumes smoke/test_vpc_redundant
smoke/test_vpc_router_nics smoke/test_vpc_vpn smoke/misc/test_deploy_vm
smoke/misc/test_vm_ha smoke/misc/test_escalations_templates
smoke/misc/test_vm_sync
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
./tools/travis/script.sh: line 44: nosetests: command not found
Traceback (most recent call last):
File "./tools/travis/xunit-reader.py", line 27, in
import texttable
ImportError: No module named texttable
```
I don't know if that is due to a change in the PR or Travis just need to be
re-kicked.
> Fully support system VMs on managed storage
> ---
>
> Key: CLOUDSTACK-9504
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.10.0.0
> Environment: All
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.10.0.0
>
>
> There are three related items for this ticket:
> 1) Do not permit "custom IOPS" as a parameter when creating a system offering
> (throw an exception if this parameter is passed in).
> 2) If you transition managed storage into maintenance mode and system VMs
> were running on that managed storage, the host-side clustered file systems
> (SRs on XenServer) are not removed. Remove them.
> 3) Add integration tests for system VMs with managed storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542434#comment-15542434 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 @jburwell I think it's Travis. I've changed the commit SHA twice now and it failed both times plus it fails with #1600, as well (even though I pushed that one multiple times, too). Not sure why it can't find nosetests. > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542438#comment-15542438 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1642 @rhtyd any ideas? > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9513) Migrate transifex workflow and format to json
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542485#comment-15542485 ] ASF GitHub Bot commented on CLOUDSTACK-9513: GitHub user milamberspace opened a pull request: https://github.com/apache/cloudstack/pull/1699 CLOUDSTACK-9513 Migrate transifex workflow and format to json Move the localization resource files from Java Properties format to JSON Key-Value format Change the Transifex sync script to handle JSON resource files instead of Properties files Update the README Remove old version from the Transifex configuration file Remove unused gen-l10n.py script and update the ui/pom.xml to remove the execution of this script cc @rhtyd @jburwell You can merge this pull request into a Git repository by running: $ git pull https://github.com/milamberspace/cloudstack L10N_MigrateToJSONkeyValue Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1699.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1699 commit f8bb65a81546cd47561b717d84c686738b8c6fbc Author: Milamber Date: 2016-10-03T13:17:50Z CLOUDSTACK-9513 Migrate transifex workflow and format to json Move the localization resource files from Java Properties format to JSON Key-Value format Change the Transifex sync script to handle JSON resource files instead of Properties files Update the README Remove old version from the Transifex configuration file Remove unused gen-l10n.py script and update the ui/pom.xml to remove the execution of this script > Migrate transifex workflow and format to json > - > > Key: CLOUDSTACK-9513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9513 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0 > > > With the changes introduced by the PR > https://github.com/apache/cloudstack/pull/1669 we no longer need > messages.properties format. Therefore, we can migrate Transifex workflow to > the json format. /cc [~milamber] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9525) add support for windows 10 guest os in xenserver 6.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542498#comment-15542498 ] ASF GitHub Bot commented on CLOUDSTACK-9525: Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1698 @karuturi @rhtyd I might be mistaken but we also need to add mapping into cloudstack/vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareGuestOsMapper and/or plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/KVMGuestOsMapper In the past if not added on vmware it would create VM with 'Other-64 bit' OS type instead e.g. this Jira ticket 'CLOUDSTACK-5922:Incorrect handling RHEL guests for 5.5 to 5.9' The same concern is for recently merged PR1696. > add support for windows 10 guest os in xenserver 6.5 > > > Key: CLOUDSTACK-9525 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9525 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542554#comment-15542554 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1696 @rhtyd @jburwell @karuturi I confirm the same issue with this PR as with 'CLOUDSTACK-5922:Incorrect handling RHEL guests for 5.5 to 5.9 When Os type is specified as Ubuntu 16.04  and VM is started on VmWare it actually creates VM with OS type 'Other (64-bit)'  The fix was to put a respective entry into vmware-base/src/com/cloud/hypervisor/vmware/util/VmwareGuestOsMapper.java https://github.com/apache/cloudstack/commit/05c6b455ae89480d84ba5dfa4dc79d3336ebd458 Can we roll back this PR and make it right? An alternative path wold be to figure out why adding entries into tables is not good enough and why changes in the code is still required. > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9527) test_01_test_vm_volume_snapshot not supported for Xen, tests keep failing
Boris Stoyanov created CLOUDSTACK-9527:
--
Summary: test_01_test_vm_volume_snapshot not supported for Xen,
tests keep failing
Key: CLOUDSTACK-9527
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9527
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: marvin
Affects Versions: 4.10.0.0, 4.9.1.0, 4.8.2.0
Reporter: Boris Stoyanov
Skipping this test for Xen since the tests keeps failling
{code}virtualmachineid=bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49
Error 431: VM snapshot for this VM is not allowed. This VM has volumes attached
which has snapshots, please remove all snapshots before taking VM snapshot
{
"cserrorcode": 4350,
"errorcode": 431,
"errortext": "VM snapshot for this VM is not allowed. This VM has volumes
attached which has snapshots, please remove all snapshots before taking VM
snapshot",
"uuidList": []
}
(local) SBCM5> create snapshot volumeid=34b96f5c-0343-4877-8e69-de27c10245bd
Error 431: Volume snapshot is not allowed, please detach it from VM with VM
Snapshots
{
"cserrorcode": 4350,
"errorcode": 431,
"errortext": "Volume snapshot is not allowed, please detach it from VM with
VM Snapshots",
"uuidList": []
}
(local) SBCM5> detach volume id=34b96f5c-0343-4877-8e69-de27c10245bd
Async job 0bfd5ae7-69f9-45c1-aca7-ef83ecbcdba3 failed
Error 431, Root volume detach can happen only when vm is in states: Stopped or
Destroyed
{
"accountid": "6e957aef-894c-11e6-8a4c-06828c01079c",
"cmd":
"org.apache.cloudstack.api.command.admin.volume.DetachVolumeCmdByAdmin",
"created": "2016-10-03T14:40:22+0100",
"jobid": "0bfd5ae7-69f9-45c1-aca7-ef83ecbcdba3",
"jobinstanceid": "34b96f5c-0343-4877-8e69-de27c10245bd",
"jobinstancetype": "Volume",
"jobprocstatus": 0,
"jobresult": {
"errorcode": 431,
"errortext": "Root volume detach can happen only when vm is in states:
Stopped or Destroyed"
},
"jobresultcode": 530,
"jobresulttype": "object",
"jobstatus": 2,
"userid": "6e958637-894c-11e6-8a4c-06828c01079c"
}
(local) SBCM5> stop virtualmachine id=bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49
{
"accountid": "6e957aef-894c-11e6-8a4c-06828c01079c",
"cmd": "org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin",
"created": "2016-10-03T14:40:51+0100",
"jobid": "92c72725-245a-4897-a9f7-b1a61b49d57d",
"jobinstanceid": "bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
"jobinstancetype": "VirtualMachine",
"jobprocstatus": 0,
"jobresult": {
"virtualmachine": {
"account": "admin",
"affinitygroup": [],
"cpunumber": 1,
"cpuspeed": 100,
"cpuused": "0.21%",
"created": "2016-10-03T14:25:16+0100",
"details": {
"hypervisortoolsversion": "xenserver56"
},
"diskioread": 0,
"diskiowrite": 0,
"diskkbsread": 2404,
"diskkbswrite": 327,
"displayname": "VM-bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
"displayvm": true,
"domain": "ROOT",
"domainid": "3f07ff46-894c-11e6-8a4c-06828c01079c",
"guestosid": "3f36045e-894c-11e6-8a4c-06828c01079c",
"haenable": false,
"hypervisor": "XenServer",
"id": "bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
"instancename": "i-2-18-VM",
"isdynamicallyscalable": true,
"jobid": "92c72725-245a-4897-a9f7-b1a61b49d57d",
"jobstatus": 0,
"memory": 128,
"name": "VM-bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
"networkkbsread": 0,
"networkkbswrite": 0,
"nic": [
{
"gateway": "10.1.1.1",
"id": "a49eac90-9fa2-4618-9989-436d6e3d5eee",
"ipaddress": "10.1.1.2",
"isdefault": true,
"macaddress": "02:00:38:54:00:01",
"netmask": "255.255.255.0",
"networkid": "5d721377-09e8-4ab4-9be8-f24e5da6cfd5",
"networkname": "test",
"secondaryip": [],
"traffictype": "Guest",
"type": "Isolated"
}
],
"ostypeid": 142,
"passwordenabled": false,
"rootdeviceid": 0,
"rootdevicetype": "ROOT",
"securitygroup": [],
"serviceofferingid": "eae0e093-6d2e-4641-9d1a-fe004e420d55",
"serviceofferingname": "Tiny Instance",
"state": "Stopped",
"tags": [],
"templatedisplaytext": "CentOS 5.6(64-bit) no GUI (XenServer)",
"templateid": "3f0b934e-894c-11e6-8a4c-06828c01079c",
"templatename": "CentOS 5.6(64-bit) no GUI (XenServer)",
"userid": "6e958637-894c-11e6-8a4c-06828c01079c",
"username": "admin",
"zoneid": "0ffd9c60-a8e7-4209-8e0e-4c54a0446f6d",
"zonename": "trl-97-x-cs48-bstoyanov"
}
},
"jobresultcode": 0,
"jobresulttype": "object",
"jobstatus": 1,
"userid": "6e958637-894c-11e6-8a4c-06828c01079c"
}
(local) SBCM5> detach volume id=34b96f5c-0343-4877-8e69-de27c10245bd
Async job 7de72a7f-cbdb-4f73
[jira] [Resolved] (CLOUDSTACK-9527) test_01_test_vm_volume_snapshot not supported for Xen, tests keep failing
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Stoyanov resolved CLOUDSTACK-9527.
Resolution: Fixed
fixed with https://github.com/apache/cloudstack/pull/1692
> test_01_test_vm_volume_snapshot not supported for Xen, tests keep failing
> -
>
> Key: CLOUDSTACK-9527
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9527
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: marvin
>Affects Versions: 4.10.0.0, 4.9.1.0, 4.8.2.0
>Reporter: Boris Stoyanov
>
> Skipping this test for Xen since the tests keeps failling
> {code}virtualmachineid=bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49
> Error 431: VM snapshot for this VM is not allowed. This VM has volumes
> attached which has snapshots, please remove all snapshots before taking VM
> snapshot
> {
> "cserrorcode": 4350,
> "errorcode": 431,
> "errortext": "VM snapshot for this VM is not allowed. This VM has volumes
> attached which has snapshots, please remove all snapshots before taking VM
> snapshot",
> "uuidList": []
> }
> (local) SBCM5> create snapshot volumeid=34b96f5c-0343-4877-8e69-de27c10245bd
> Error 431: Volume snapshot is not allowed, please detach it from VM with VM
> Snapshots
> {
> "cserrorcode": 4350,
> "errorcode": 431,
> "errortext": "Volume snapshot is not allowed, please detach it from VM with
> VM Snapshots",
> "uuidList": []
> }
> (local) SBCM5> detach volume id=34b96f5c-0343-4877-8e69-de27c10245bd
> Async job 0bfd5ae7-69f9-45c1-aca7-ef83ecbcdba3 failed
> Error 431, Root volume detach can happen only when vm is in states: Stopped
> or Destroyed
> {
> "accountid": "6e957aef-894c-11e6-8a4c-06828c01079c",
> "cmd":
> "org.apache.cloudstack.api.command.admin.volume.DetachVolumeCmdByAdmin",
> "created": "2016-10-03T14:40:22+0100",
> "jobid": "0bfd5ae7-69f9-45c1-aca7-ef83ecbcdba3",
> "jobinstanceid": "34b96f5c-0343-4877-8e69-de27c10245bd",
> "jobinstancetype": "Volume",
> "jobprocstatus": 0,
> "jobresult": {
> "errorcode": 431,
> "errortext": "Root volume detach can happen only when vm is in states:
> Stopped or Destroyed"
> },
> "jobresultcode": 530,
> "jobresulttype": "object",
> "jobstatus": 2,
> "userid": "6e958637-894c-11e6-8a4c-06828c01079c"
> }
> (local) SBCM5> stop virtualmachine id=bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49
> {
> "accountid": "6e957aef-894c-11e6-8a4c-06828c01079c",
> "cmd": "org.apache.cloudstack.api.command.admin.vm.StopVMCmdByAdmin",
> "created": "2016-10-03T14:40:51+0100",
> "jobid": "92c72725-245a-4897-a9f7-b1a61b49d57d",
> "jobinstanceid": "bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
> "jobinstancetype": "VirtualMachine",
> "jobprocstatus": 0,
> "jobresult": {
> "virtualmachine": {
> "account": "admin",
> "affinitygroup": [],
> "cpunumber": 1,
> "cpuspeed": 100,
> "cpuused": "0.21%",
> "created": "2016-10-03T14:25:16+0100",
> "details": {
> "hypervisortoolsversion": "xenserver56"
> },
> "diskioread": 0,
> "diskiowrite": 0,
> "diskkbsread": 2404,
> "diskkbswrite": 327,
> "displayname": "VM-bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
> "displayvm": true,
> "domain": "ROOT",
> "domainid": "3f07ff46-894c-11e6-8a4c-06828c01079c",
> "guestosid": "3f36045e-894c-11e6-8a4c-06828c01079c",
> "haenable": false,
> "hypervisor": "XenServer",
> "id": "bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
> "instancename": "i-2-18-VM",
> "isdynamicallyscalable": true,
> "jobid": "92c72725-245a-4897-a9f7-b1a61b49d57d",
> "jobstatus": 0,
> "memory": 128,
> "name": "VM-bbd3104b-a8a7-4ca2-8d22-15b9ea2cea49",
> "networkkbsread": 0,
> "networkkbswrite": 0,
> "nic": [
> {
> "gateway": "10.1.1.1",
> "id": "a49eac90-9fa2-4618-9989-436d6e3d5eee",
> "ipaddress": "10.1.1.2",
> "isdefault": true,
> "macaddress": "02:00:38:54:00:01",
> "netmask": "255.255.255.0",
> "networkid": "5d721377-09e8-4ab4-9be8-f24e5da6cfd5",
> "networkname": "test",
> "secondaryip": [],
> "traffictype": "Guest",
> "type": "Isolated"
> }
> ],
> "ostypeid": 142,
> "passwordenabled": false,
> "rootdeviceid": 0,
> "rootdevicetype": "ROOT",
> "securitygroup": [],
> "serviceofferingid": "eae0e093-6d2e-4641-9d1a-fe004e420d55",
> "serviceofferingname": "Tiny Instance",
> "state": "Stopped",
> "tags": [],
> "templatedisplaytext": "CentOS 5.6(64-bit) no GUI (XenServer)",
> "templateid": "3f0b934e-894c
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542620#comment-15542620 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1696 @serg38 @rhtyd I am going to rollback this merge as it appears that the patch does not fix the issue. I would also like to explore @serg38's point that we shouldn't need to make code changes to support a new OS. > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9379) Support nested virtualization at VM level on VMware Hypervisor
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542770#comment-15542770
]
ASF GitHub Bot commented on CLOUDSTACK-9379:
Github user nvazquez commented on the issue:
https://github.com/apache/cloudstack/pull/1542
Hi @rhtyd, we ran `test_internal_lb.py` and `test_vpc_vpn.py` using
`tl-vmware.ova` template and got this results:
`test_vpc_vpn` is ok:
```
Test Site 2 Site VPN Across redundant VPCs ... === TestName:
test_01_redundant_vpc_site2site_vpn | Status : SUCCESS ===
ok
Test Remote Access VPN in VPC ... === TestName:
test_01_vpc_remote_access_vpn | Status : SUCCESS ===
ok
Test Site 2 Site VPN Across VPCs ... === TestName:
test_01_vpc_site2site_vpn | Status : SUCCESS ===
ok
--
Ran 3 tests in 1949.605s
OK
```
However, `test_internal_lb` fails, we could find some issues:
- /sbin/ip is needed but not present in template {Cmd: /sbin/ip addr show
eth0 |grep 'inet '| cut -f6 -d' ' > /tmp/index.html via Host: 10.140.12.107}
{returns: [u'sh: /sbin/ip: not found']}
- 2 more tests fail due to a difference in wget on new template: {Cmd:
/usr/bin/wget -T3 -qO- --user=XX --password=XX http://:8081/admin?stats via
Host: 10.140.12.106} {returns: [u"/usr/bin/wget: unrecognized option '..
- We have some strange erros in this functions which require more arguments
than given but couldn't find out why
```
2016-10-02 22:13:20,881 - CRITICAL - EXCEPTION:
execute_internallb_haproxy_tests: ['Traceback (most recent call last):\n', '
File "/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
testMethod()\n', 'TypeError: execute_internallb_haproxy_tests() takes exactly 2
arguments (1 given)\n']
2016-10-02 22:13:20,883 - CRITICAL - EXCEPTION:
execute_internallb_roundrobin_tests: ['Traceback (most recent call last):\n', '
File "/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
testMethod()\n', 'TypeError: execute_internallb_roundrobin_tests() takes
exactly 2 arguments (1 given)\n']
2016-10-02 22:13:20,885 - CRITICAL - EXCEPTION: run_ssh_test_accross_hosts:
['Traceback (most recent call last):\n', ' File
"/usr/local/lib/python2.7/unittest/case.py", line 331, in run\n
testMethod()\n', 'TypeError: run_ssh_test_accross_hosts() takes at least 3
arguments (1 given)\n']
```
> Support nested virtualization at VM level on VMware Hypervisor
> --
>
> Key: CLOUDSTACK-9379
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9379
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.9.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Fix For: 4.10.0.0
>
>
> h2. Introduction
> It is desired to support nested virtualization at VM level for VMware
> hypervisor. Current behaviour supports enabling/desabling global nested
> virtualization by modifying global config {{'vmware.nested.virtualization'}}.
> It is wished to improve this feature, having control at VM level instead of a
> global control only.
> h2. Proposal
> A new global configuration is added, to enable/disable VM nested
> virtualization control: {{'vmware.nested.virtualization.perVM'}}. Default
> value=false
> h2. Behaviour
> After a vm deployment or start command, vm params include
> {{nestedVirtualizationFlag}} key and its value is:
> * true -> nested virtualization enabled
> * false -> nested virtualization disabled
> We will determinate nested virtualization enabled/disabled by examining:
> * (1) global configuration {{'vmware.nested.virtualization'}} value
> * (2) global configuration {{'vmware.nested.virtualization.perVM'}} value
> * (3) {{'nestedVirtualizationFlag'}} value in {{user_vm_details}} if present,
> null if not.
> Using this 3 values, there are different use cases:
> # (1) = TRUE, (2) = TRUE, (3) is null -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = TRUE, (2) = FALSE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) is null -> DISABLED
> # (1) = FALSE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = FALSE, (2) = FALSE -> DISABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9515) internal LB vm is not handled when parsing cmd_line.json, resulting in internal LB vm not come up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9515: - Fix Version/s: (was: 4.9.2.0) 4.10.0.0 > internal LB vm is not handled when parsing cmd_line.json, resulting in > internal LB vm not come up > - > > Key: CLOUDSTACK-9515 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9515 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.8.1 > Environment: CentOS 7.2 + VMWare 5.5u3 + NFS primary/secondary storage >Reporter: Murali Reddy >Assignee: Murali Reddy >Priority: Critical > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > internal LB vm is not handled when parsing cmd_line.json, resulting in > internal LB vm not come up. > parsing cmd_line to create 'ips' data bag, never handled internal lb vm, but > still > worked due to another bug. support for internal lb vm is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542818#comment-15542818 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1696 @jburwell @rhtyd Sorry for a flood of messages. I checked and we do have mapping for all OS for Vmware 6 in ACS. It was introduced in 4.7 so that means this PR needs to have those 2 lines added (or a new PR created for this) INSERT IGNORE INTO cloud.guest_os_hypervisor (uuid,hypervisor_type, hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) VALUES (UUID(),'VMware', '6.0', 'ubuntuGuest', 255, utc_timestamp(), 0); INSERT IGNORE INTO cloud.guest_os_hypervisor (uuid,hypervisor_type, hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) VALUES (UUID(),'VMware', '6.0', 'ubuntu64Guest', 256, utc_timestamp(), 0); > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542801#comment-15542801 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1696 @jburwell @rhtyd I apologies. The issue in our environment was due to using ESX v6. Once I added new mapping for it Vmware properly assigned Os type. It would be nice to officially certify ESX6 for ACS. It has been a supported platform for one of the commercial distribution for some time already. INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) VALUES (UUID(),'VMware', '6.0', 'ubuntuGuest', 255, utc_timestamp(), 0); INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) VALUES (UUID(),'VMware', '6.0', 'ubuntu64Guest', 256, utc_timestamp(), 0); > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9525) add support for windows 10 guest os in xenserver 6.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542827#comment-15542827 ] ASF GitHub Bot commented on CLOUDSTACK-9525: Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1698 @karuturi Can we add mappings for Windows 10 for Vmware hypervisors as well? > add support for windows 10 guest os in xenserver 6.5 > > > Key: CLOUDSTACK-9525 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9525 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542940#comment-15542940 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1696 @serg38 good catch regarding vSphere 6. As I noted earlier, I will be rolling back this merge, and we will address it on re-submission. Once we resolve the VMware 5.5, XenServer 6.5, and KVM smoke test issues in #1692, we plan to execute the vSphere6 certification tests for 4.9.1.0 and 4.10.0.0. In anticipation of this testing, vSphere 6 support has already been added to Trillian and blueorangutan. It hasn't been added to the default matrix in order to avoid any additional variables stabilizing the smoke test suite. > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15542993#comment-15542993 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1696 @jburwell rollback is not necessary. We've no guest os mappings for VMware 6.0, those need to be added. If needed, I can send a new PR. /cc @serg38 > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543006#comment-15543006
]
ASF GitHub Bot commented on CLOUDSTACK-9504:
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1642
@jburwell @mike-tutkowski looks like marvin fails to get installed
properly, one of the dependency fails with following:
Command "/opt/python/2.7.10/bin/python2.7 -u -c "import setuptools,
tokenize;__file__='/tmp/pip-build-wNNQnH/cryptography/setup.py';exec(compile(getattr(tokenize,
'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))"
install --record /tmp/pip-ELOxnP-record/install-record.txt
--single-version-externally-managed --compile --user --prefix=" failed with
error code 1 in /tmp/pip-build-wNNQnH/cryptography/
Feel free to try to fix it, else I'll open a new PR and see if it works
with latest 4.9 and master branches, and fix anything necessary tomorrow. I'll
keep you posted.
> Fully support system VMs on managed storage
> ---
>
> Key: CLOUDSTACK-9504
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
>Affects Versions: 4.10.0.0
> Environment: All
>Reporter: Mike Tutkowski
>Assignee: Mike Tutkowski
> Fix For: 4.10.0.0
>
>
> There are three related items for this ticket:
> 1) Do not permit "custom IOPS" as a parameter when creating a system offering
> (throw an exception if this parameter is passed in).
> 2) If you transition managed storage into maintenance mode and system VMs
> were running on that managed storage, the host-side clustered file systems
> (SRs on XenServer) are not removed. Remove them.
> 3) Add integration tests for system VMs with managed storage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9379) Support nested virtualization at VM level on VMware Hypervisor
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543015#comment-15543015
]
ASF GitHub Bot commented on CLOUDSTACK-9379:
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1542
Thanks for testing @nvazquez I think since @NuxRo built new vmware
templates, we can consume macchinina/vmware:
http://dl.openvm.eu/cloudstack/macchinina/x86_64/testing
The TinyCore based template I had created lacks 'ip/iproute' package and
httpd, I'll try to fix it though as this point since Lucian has already fixed
macchinina it might be not necessary.
> Support nested virtualization at VM level on VMware Hypervisor
> --
>
> Key: CLOUDSTACK-9379
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9379
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
>Affects Versions: 4.9.0
>Reporter: Nicolas Vazquez
>Assignee: Nicolas Vazquez
> Fix For: 4.10.0.0
>
>
> h2. Introduction
> It is desired to support nested virtualization at VM level for VMware
> hypervisor. Current behaviour supports enabling/desabling global nested
> virtualization by modifying global config {{'vmware.nested.virtualization'}}.
> It is wished to improve this feature, having control at VM level instead of a
> global control only.
> h2. Proposal
> A new global configuration is added, to enable/disable VM nested
> virtualization control: {{'vmware.nested.virtualization.perVM'}}. Default
> value=false
> h2. Behaviour
> After a vm deployment or start command, vm params include
> {{nestedVirtualizationFlag}} key and its value is:
> * true -> nested virtualization enabled
> * false -> nested virtualization disabled
> We will determinate nested virtualization enabled/disabled by examining:
> * (1) global configuration {{'vmware.nested.virtualization'}} value
> * (2) global configuration {{'vmware.nested.virtualization.perVM'}} value
> * (3) {{'nestedVirtualizationFlag'}} value in {{user_vm_details}} if present,
> null if not.
> Using this 3 values, there are different use cases:
> # (1) = TRUE, (2) = TRUE, (3) is null -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = TRUE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = TRUE, (2) = FALSE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) is null -> DISABLED
> # (1) = FALSE, (2) = TRUE, (3) = TRUE -> ENABLED
> # (1) = FALSE, (2) = TRUE, (3) = FALSE -> DISABLED
> # (1) = FALSE, (2) = FALSE -> DISABLED
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543025#comment-15543025 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 Travis, which was failing for a similar reason for #1600, passed, so I will (once again) change the commit SHA and re-push. In fact, while I'm at it, I'll rebase it against the latest from master before re-pushing. > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9513) Migrate transifex workflow and format to json
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543026#comment-15543026 ] ASF GitHub Bot commented on CLOUDSTACK-9513: Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1699 Sweet! Thanks @milamberspace I was going to send this in few days, but you beat me to it :) I'll review this tomorrow and get back to you. > Migrate transifex workflow and format to json > - > > Key: CLOUDSTACK-9513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9513 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0 > > > With the changes introduced by the PR > https://github.com/apache/cloudstack/pull/1669 we no longer need > messages.properties format. Therefore, we can migrate Transifex workflow to > the json format. /cc [~milamber] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9513) Migrate transifex workflow and format to json
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543028#comment-15543028 ] ASF GitHub Bot commented on CLOUDSTACK-9513: Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1699 @blueorangutan package > Migrate transifex workflow and format to json > - > > Key: CLOUDSTACK-9513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9513 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0 > > > With the changes introduced by the PR > https://github.com/apache/cloudstack/pull/1669 we no longer need > messages.properties format. Therefore, we can migrate Transifex workflow to > the json format. /cc [~milamber] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9513) Migrate transifex workflow and format to json
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543032#comment-15543032 ] ASF GitHub Bot commented on CLOUDSTACK-9513: Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1699 I will add this PR to the list to merge post resolution of #1692 > Migrate transifex workflow and format to json > - > > Key: CLOUDSTACK-9513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9513 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0 > > > With the changes introduced by the PR > https://github.com/apache/cloudstack/pull/1669 we no longer need > messages.properties format. Therefore, we can migrate Transifex workflow to > the json format. /cc [~milamber] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9364) Add Support for Ubuntu 16.04
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543062#comment-15543062 ] ASF GitHub Bot commented on CLOUDSTACK-9364: Github user serg38 commented on the issue: https://github.com/apache/cloudstack/pull/1696 @rhtyd @jburwell Actually ESX 6 mapping are here schema-461to470.sql INSERT IGNORE INTO `cloud`.`hypervisor_capabilities` values (25,UUID(),'VMware','6.0',128,0,13,32,1,1); INSERT IGNORE INTO `cloud`.`guest_os_hypervisor` (uuid,hypervisor_type, hypervisor_version, guest_os_name, guest_os_id, created, is_user_defined) SELECT UUID(),'VMware', '6.0', guest_os_name, guest_os_id, utc_timestamp(), 0 FROM `cloud`.`guest_os_hypervisor` WHERE hypervisor_type='VMware' AND hypervisor_version='5.5' AND (guest_os_id NOT IN (1,2,3,4,62,63,64,65,156,157,221,222) AND guest_os_id NOT BETWEEN 121 AND 130); > Add Support for Ubuntu 16.04 > > > Key: CLOUDSTACK-9364 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9364 > Project: CloudStack > Issue Type: Task > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Wei Zhou >Assignee: Rohit Yadav > Fix For: Future, 4.9.1.0 > > > Ubuntu 16.04 has been released on 21st April > http://releases.ubuntu.com/16.04/ > We need to support it -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543135#comment-15543135 ] ASF GitHub Bot commented on CLOUDSTACK-9504: GitHub user mike-tutkowski reopened a pull request: https://github.com/apache/cloudstack/pull/1642 CLOUDSTACK-9504: System VMs on Managed Storage This PR makes it easier to spin up system VMs on managed storage. Managed storage is when you have a dedicated volume on a SAN for a particular virtual disk (making it easier to deliver QoS). For example, with this PR, you'd likely have a single virtual disk for a system VM. On XenServer, that virtual disk resides by itself in a storage repository (no other virtual disks share this storage repository). It was possible in the past to spin up system VMs that used managed storage, but this PR facilitates the use case by making changes to the System Service Offering dialog (and by putting in some parameter checks in the management server). JIRA ticket: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 You can merge this pull request into a Git repository by running: $ git pull https://github.com/mike-tutkowski/cloudstack managed_system_vms Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1642.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1642 > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543136#comment-15543136 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 I still got a weird Travis failure, so I decided to close and re-open this PR. > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543134#comment-15543134 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski closed the pull request at: https://github.com/apache/cloudstack/pull/1642 > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543236#comment-15543236 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 Closing and re-opening the PR fixed the Travis issue. > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times
Paul Angus created CLOUDSTACK-9528: -- Summary: SSVM Downloads (built-in) template multiple times Key: CLOUDSTACK-9528 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Management Server, Secondary Storage, XenServer Affects Versions: 4.9.0 Environment: ACS 4.9 with XenServer 6.5SP1 Reporter: Paul Angus SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in template multiple times (concurrently). Once this has happened the built-in template could not be used to deploy VMs as couldstack found 2 VHDs in the directory and threw an insufficient capacity exception. The template was being downloaded locally (at 35MB/s) with no drop outs. There are in fact multiple issues here: 1. SSVM not behaving properly and downloading mulitple copies. 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. The full path and filename of the VHD is in its data base, it should use it. 3. what is template.properties for? the filename is contained within it, as is an MDSUM to check for consistency 4. the filename in template.properties is different to the one in the database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Angus updated CLOUDSTACK-9528: --- Attachment: Capture.PNG during download of template > SSVM Downloads (built-in) template multiple times > - > > Key: CLOUDSTACK-9528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Secondary Storage, XenServer >Affects Versions: 4.9.0 > Environment: ACS 4.9 with XenServer 6.5SP1 >Reporter: Paul Angus > Attachments: Capture.PNG > > > SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in > template multiple times (concurrently). > Once this has happened the built-in template could not be used to deploy VMs > as couldstack found 2 VHDs in the directory and threw an insufficient > capacity exception. > The template was being downloaded locally (at 35MB/s) with no drop outs. > There are in fact multiple issues here: > 1. SSVM not behaving properly and downloading mulitple copies. > 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. > The full path and filename of the VHD is in its data base, it should use it. > 3. what is template.properties for? the filename is contained within it, as > is an MDSUM to check for consistency > 4. the filename in template.properties is different to the one in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Angus updated CLOUDSTACK-9528: --- Attachment: Capture2 (1).PNG post download of template > SSVM Downloads (built-in) template multiple times > - > > Key: CLOUDSTACK-9528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Secondary Storage, XenServer >Affects Versions: 4.9.0 > Environment: ACS 4.9 with XenServer 6.5SP1 >Reporter: Paul Angus > Attachments: Capture.PNG, Capture2 (1).PNG > > > SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in > template multiple times (concurrently). > Once this has happened the built-in template could not be used to deploy VMs > as couldstack found 2 VHDs in the directory and threw an insufficient > capacity exception. > The template was being downloaded locally (at 35MB/s) with no drop outs. > There are in fact multiple issues here: > 1. SSVM not behaving properly and downloading mulitple copies. > 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. > The full path and filename of the VHD is in its data base, it should use it. > 3. what is template.properties for? the filename is contained within it, as > is an MDSUM to check for consistency > 4. the filename in template.properties is different to the one in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
Paul Angus created CLOUDSTACK-9529: -- Summary: Marvin Tests do not clean up properly Key: CLOUDSTACK-9529 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: marvin Affects Versions: 4.9.0 Environment: ACS 4.9 Reporter: Paul Angus Priority: Minor After running the smoketest suite against XenServer 6.5 it was found that the tests had left a number of resources behind or in use. * 20 public IP addresses had been consumed and not cleaned up. * 22 guest networks remained * 6 VPCs remained * 30 Accounts remained * 20 VRs * 26 compute offerings * 8 Disk offerings * 12 network offerings * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9504) Fully support system VMs on managed storage
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543669#comment-15543669 ] ASF GitHub Bot commented on CLOUDSTACK-9504: Github user mike-tutkowski commented on the issue: https://github.com/apache/cloudstack/pull/1642 @jburwell Excellent...closing and re-opening the ticket fixed the CI issue. > Fully support system VMs on managed storage > --- > > Key: CLOUDSTACK-9504 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9504 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server >Affects Versions: 4.10.0.0 > Environment: All >Reporter: Mike Tutkowski >Assignee: Mike Tutkowski > Fix For: 4.10.0.0 > > > There are three related items for this ticket: > 1) Do not permit "custom IOPS" as a parameter when creating a system offering > (throw an exception if this parameter is passed in). > 2) If you transition managed storage into maintenance mode and system VMs > were running on that managed storage, the host-side clustered file systems > (SRs on XenServer) are not removed. Remove them. > 3) Add integration tests for system VMs with managed storage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9525) add support for windows 10 guest os in xenserver 6.5
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544093#comment-15544093 ] ASF GitHub Bot commented on CLOUDSTACK-9525: Github user jburwell commented on the issue: https://github.com/apache/cloudstack/pull/1698 @serg38 @karuturi can you also include the mappings for KVM and HyperV? > add support for windows 10 guest os in xenserver 6.5 > > > Key: CLOUDSTACK-9525 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9525 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Reporter: Rajani Karuturi >Assignee: Rajani Karuturi > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9516) Invalid Attribute PhysicalNetwork.vlan Fails Smoke Tests
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Burwell updated CLOUDSTACK-9516:
-
Assignee: Rohit Yadav (was: Murali Reddy)
> Invalid Attribute PhysicalNetwork.vlan Fails Smoke Tests
>
>
> Key: CLOUDSTACK-9516
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9516
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: marvin
>Affects Versions: 4.8.1
> Environment: CentOS 7.2 + VMware 5.5u3 + NFS Primary/Secondary Storage
> CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary Storage
>Reporter: John Burwell
>Assignee: Rohit Yadav
>Priority: Critical
> Labels: 4.8.2.0-smoke-test-failure
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
> Attachments: test_guest_vlan_range.py.xml,
> test_non_contigiousvlan.py.xml
>
>
> The setup of the following test suites fail due to a reference to the
> {{vlan}} attribute which does not exist on the {{PhysicalNetwork}} class in
> [common.py|https://github.com/apache/cloudstack/blob/4.8/tools/marvin/marvin/lib/common.py#L1060]:
> *
> [test_guest_vlan_range|https://github.com/apache/cloudstack/blob/4.8/test/integration/smoke/test_guest_vlan_range.py]
> *
> [test_non_contigiousvlan|https://github.com/apache/cloudstack/blob/4.8/test/integration/smoke/test_non_contigiousvlan.py]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-9516) Invalid Attribute PhysicalNetwork.vlan Fails Smoke Tests
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Burwell resolved CLOUDSTACK-9516.
--
Resolution: Fixed
The {test_guest_vlan_range} and {test_non_contigiousvlan} test suite pass for
the most recent VMware, XenServer, and KVM test runs on [PR
#1692|https://github.com/apache/cloudstack/pull/1692].
> Invalid Attribute PhysicalNetwork.vlan Fails Smoke Tests
>
>
> Key: CLOUDSTACK-9516
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9516
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: marvin
>Affects Versions: 4.8.1
> Environment: CentOS 7.2 + VMware 5.5u3 + NFS Primary/Secondary Storage
> CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary Storage
>Reporter: John Burwell
>Assignee: Rohit Yadav
>Priority: Critical
> Labels: 4.8.2.0-smoke-test-failure
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
> Attachments: test_guest_vlan_range.py.xml,
> test_non_contigiousvlan.py.xml
>
>
> The setup of the following test suites fail due to a reference to the
> {{vlan}} attribute which does not exist on the {{PhysicalNetwork}} class in
> [common.py|https://github.com/apache/cloudstack/blob/4.8/tools/marvin/marvin/lib/common.py#L1060]:
> *
> [test_guest_vlan_range|https://github.com/apache/cloudstack/blob/4.8/test/integration/smoke/test_guest_vlan_range.py]
> *
> [test_non_contigiousvlan|https://github.com/apache/cloudstack/blob/4.8/test/integration/smoke/test_non_contigiousvlan.py]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9515) internal LB vm is not handled when parsing cmd_line.json, resulting in internal LB vm not come up
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9515: - Assignee: Rohit Yadav (was: Murali Reddy) > internal LB vm is not handled when parsing cmd_line.json, resulting in > internal LB vm not come up > - > > Key: CLOUDSTACK-9515 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9515 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) >Affects Versions: 4.8.1 > Environment: CentOS 7.2 + VMWare 5.5u3 + NFS primary/secondary storage >Reporter: Murali Reddy >Assignee: Rohit Yadav >Priority: Critical > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > internal LB vm is not handled when parsing cmd_line.json, resulting in > internal LB vm not come up. > parsing cmd_line to create 'ips' data bag, never handled internal lb vm, but > still > worked due to another bug. support for internal lb vm is needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CLOUDSTACK-9514) MarvinTests: some host credentials are hardcoded, make them to be picked up from config file
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell reopened CLOUDSTACK-9514: -- > MarvinTests: some host credentials are hardcoded, make them to be picked up > from config file > > > Key: CLOUDSTACK-9514 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9514 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.8.1 > Environment: CentOS 7.2 + VMWare 5.5u3 + NFS primary/secondary storage >Reporter: Boris Stoyanov >Priority: Critical > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > test_router_dhcphosts.py > test_routers_iptables_default_policy.py > Have hardcoded values for host credentials which are making our tests fail if > we setup different from default. > Making them to be picked up from the config file would be more sufficient for > everyone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CLOUDSTACK-9516) Invalid Attribute PhysicalNetwork.vlan Fails Smoke Tests
[
https://issues.apache.org/jira/browse/CLOUDSTACK-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Burwell reopened CLOUDSTACK-9516:
--
> Invalid Attribute PhysicalNetwork.vlan Fails Smoke Tests
>
>
> Key: CLOUDSTACK-9516
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9516
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: marvin
>Affects Versions: 4.8.1
> Environment: CentOS 7.2 + VMware 5.5u3 + NFS Primary/Secondary Storage
> CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary Storage
>Reporter: John Burwell
>Assignee: Rohit Yadav
>Priority: Critical
> Labels: 4.8.2.0-smoke-test-failure
> Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
> Attachments: test_guest_vlan_range.py.xml,
> test_non_contigiousvlan.py.xml
>
>
> The setup of the following test suites fail due to a reference to the
> {{vlan}} attribute which does not exist on the {{PhysicalNetwork}} class in
> [common.py|https://github.com/apache/cloudstack/blob/4.8/tools/marvin/marvin/lib/common.py#L1060]:
> *
> [test_guest_vlan_range|https://github.com/apache/cloudstack/blob/4.8/test/integration/smoke/test_guest_vlan_range.py]
> *
> [test_non_contigiousvlan|https://github.com/apache/cloudstack/blob/4.8/test/integration/smoke/test_non_contigiousvlan.py]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9528: - Labels: 4.8.2.0-smoke-test-failure (was: ) > SSVM Downloads (built-in) template multiple times > - > > Key: CLOUDSTACK-9528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Secondary Storage, XenServer >Affects Versions: 4.8.1, 4.9.0 > Environment: ACS 4.9 with XenServer 6.5SP1 >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > Attachments: Capture.PNG, Capture2 (1).PNG > > > SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in > template multiple times (concurrently). > Once this has happened the built-in template could not be used to deploy VMs > as couldstack found 2 VHDs in the directory and threw an insufficient > capacity exception. > The template was being downloaded locally (at 35MB/s) with no drop outs. > There are in fact multiple issues here: > 1. SSVM not behaving properly and downloading mulitple copies. > 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. > The full path and filename of the VHD is in its data base, it should use it. > 3. what is template.properties for? the filename is contained within it, as > is an MDSUM to check for consistency > 4. the filename in template.properties is different to the one in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9528: - Affects Version/s: 4.8.1 > SSVM Downloads (built-in) template multiple times > - > > Key: CLOUDSTACK-9528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Secondary Storage, XenServer >Affects Versions: 4.8.1, 4.9.0 > Environment: ACS 4.9 with XenServer 6.5SP1 >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > Attachments: Capture.PNG, Capture2 (1).PNG > > > SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in > template multiple times (concurrently). > Once this has happened the built-in template could not be used to deploy VMs > as couldstack found 2 VHDs in the directory and threw an insufficient > capacity exception. > The template was being downloaded locally (at 35MB/s) with no drop outs. > There are in fact multiple issues here: > 1. SSVM not behaving properly and downloading mulitple copies. > 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. > The full path and filename of the VHD is in its data base, it should use it. > 3. what is template.properties for? the filename is contained within it, as > is an MDSUM to check for consistency > 4. the filename in template.properties is different to the one in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9528) SSVM Downloads (built-in) template multiple times
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9528: - Fix Version/s: 4.8.2.0 4.9.1.0 4.10.0.0 > SSVM Downloads (built-in) template multiple times > - > > Key: CLOUDSTACK-9528 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9528 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, Secondary Storage, XenServer >Affects Versions: 4.8.1, 4.9.0 > Environment: ACS 4.9 with XenServer 6.5SP1 >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > Attachments: Capture.PNG, Capture2 (1).PNG > > > SSVM under XenServer 6.5SP1 and ACS 4.9 was found to download the built-in > template multiple times (concurrently). > Once this has happened the built-in template could not be used to deploy VMs > as couldstack found 2 VHDs in the directory and threw an insufficient > capacity exception. > The template was being downloaded locally (at 35MB/s) with no drop outs. > There are in fact multiple issues here: > 1. SSVM not behaving properly and downloading mulitple copies. > 2. Why is cloudstack 'blindly' looking in a directory for a VHD to pick up. > The full path and filename of the VHD is in its data base, it should use it. > 3. what is template.properties for? the filename is contained within it, as > is an MDSUM to check for consistency > 4. the filename in template.properties is different to the one in the > database. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544165#comment-15544165 ] John Burwell commented on CLOUDSTACK-9529: -- I am upgrading the priority of this defect to "Major" because it portends to resource exhaustion for longer test runs. > Marvin Tests do not clean up properly > - > > Key: CLOUDSTACK-9529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.9.0 > Environment: ACS 4.9 >Reporter: Paul Angus >Priority: Minor > Labels: 4.8.2.0-smoke-test-failure > > After running the smoketest suite against XenServer 6.5 it was found that the > tests had left a number of resources behind or in use. > * 20 public IP addresses had been consumed and not cleaned up. > * 22 guest networks remained > * 6 VPCs remained > * 30 Accounts remained > * 20 VRs > * 26 compute offerings > * 8 Disk offerings > * 12 network offerings > * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9529: - Labels: 4.8.2.0-smoke-test-failure (was: ) > Marvin Tests do not clean up properly > - > > Key: CLOUDSTACK-9529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.9.0 > Environment: ACS 4.9 >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > > After running the smoketest suite against XenServer 6.5 it was found that the > tests had left a number of resources behind or in use. > * 20 public IP addresses had been consumed and not cleaned up. > * 22 guest networks remained > * 6 VPCs remained > * 30 Accounts remained > * 20 VRs > * 26 compute offerings > * 8 Disk offerings > * 12 network offerings > * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9529: - Priority: Major (was: Minor) > Marvin Tests do not clean up properly > - > > Key: CLOUDSTACK-9529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.9.0 > Environment: ACS 4.9 >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > > After running the smoketest suite against XenServer 6.5 it was found that the > tests had left a number of resources behind or in use. > * 20 public IP addresses had been consumed and not cleaned up. > * 22 guest networks remained > * 6 VPCs remained > * 30 Accounts remained > * 20 VRs > * 26 compute offerings > * 8 Disk offerings > * 12 network offerings > * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9529: - Environment: CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary Storage (was: ACS 4.9) > Marvin Tests do not clean up properly > - > > Key: CLOUDSTACK-9529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.8.1, 4.9.0 > Environment: CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary > Storage >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > After running the smoketest suite against XenServer 6.5 it was found that the > tests had left a number of resources behind or in use. > * 20 public IP addresses had been consumed and not cleaned up. > * 22 guest networks remained > * 6 VPCs remained > * 30 Accounts remained > * 20 VRs > * 26 compute offerings > * 8 Disk offerings > * 12 network offerings > * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9529: - Fix Version/s: 4.8.2.0 4.9.1.0 4.10.0.0 > Marvin Tests do not clean up properly > - > > Key: CLOUDSTACK-9529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.8.1, 4.9.0 > Environment: CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary > Storage >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > After running the smoketest suite against XenServer 6.5 it was found that the > tests had left a number of resources behind or in use. > * 20 public IP addresses had been consumed and not cleaned up. > * 22 guest networks remained > * 6 VPCs remained > * 30 Accounts remained > * 20 VRs > * 26 compute offerings > * 8 Disk offerings > * 12 network offerings > * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-9529) Marvin Tests do not clean up properly
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Burwell updated CLOUDSTACK-9529: - Affects Version/s: 4.8.1 > Marvin Tests do not clean up properly > - > > Key: CLOUDSTACK-9529 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9529 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: marvin >Affects Versions: 4.8.1, 4.9.0 > Environment: CentOS 7.2 + XenServer 6.5 + NFS Primary/Secondary > Storage >Reporter: Paul Angus > Labels: 4.8.2.0-smoke-test-failure > Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0 > > > After running the smoketest suite against XenServer 6.5 it was found that the > tests had left a number of resources behind or in use. > * 20 public IP addresses had been consumed and not cleaned up. > * 22 guest networks remained > * 6 VPCs remained > * 30 Accounts remained > * 20 VRs > * 26 compute offerings > * 8 Disk offerings > * 12 network offerings > * 13 VPC offerings -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9513) Migrate transifex workflow and format to json
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544380#comment-15544380 ] ASF GitHub Bot commented on CLOUDSTACK-9513: Github user blueorangutan commented on the issue: https://github.com/apache/cloudstack/pull/1699 Packaging result: ✔centos6 ✔centos7 ✔debian. JID-47 > Migrate transifex workflow and format to json > - > > Key: CLOUDSTACK-9513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9513 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0 > > > With the changes introduced by the PR > https://github.com/apache/cloudstack/pull/1669 we no longer need > messages.properties format. Therefore, we can migrate Transifex workflow to > the json format. /cc [~milamber] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-9513) Migrate transifex workflow and format to json
[ https://issues.apache.org/jira/browse/CLOUDSTACK-9513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544525#comment-15544525 ] ASF GitHub Bot commented on CLOUDSTACK-9513: Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1699 +1 LGTM Screenshots:   > Migrate transifex workflow and format to json > - > > Key: CLOUDSTACK-9513 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9513 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: UI >Reporter: Rohit Yadav >Assignee: Rohit Yadav > Fix For: Future, 4.10.0.0 > > > With the changes introduced by the PR > https://github.com/apache/cloudstack/pull/1669 we no longer need > messages.properties format. Therefore, we can migrate Transifex workflow to > the json format. /cc [~milamber] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
