[jira] [Commented] (CLOUDSTACK-8910) The reserved_capacity field increases suddenly after a vmware host failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895530#comment-15895530
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8910:


Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/892
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 421
 Hypervisor xenserver
 NetworkType Advanced
 Passed=103
 Failed=2
 Skipped=7

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_routers_network_ops.py

 * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failing since 2 
runs

 * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failing since 
3 runs


**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


> The reserved_capacity field increases suddenly after a vmware host failure
> --
>
> Key: CLOUDSTACK-8910
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8910
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: sudharma jain
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9112) deployVM thread is holding the global lock on network longer and cause delays and some improvements in the planner

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895269#comment-15895269
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9112:


Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1180
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 420
 Hypervisor xenserver
 NetworkType Advanced
 Passed=102
 Failed=3
 Skipped=7

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_routers_network_ops.py

 * test_02_isolate_network_FW_PF_default_routes_egress_false Failed

 * test_01_RVR_Network_FW_PF_SSH_default_routes_egress_true Failed

 * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failing since 
2 runs


**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


> deployVM thread is holding the global lock on network longer and cause delays 
> and some improvements in the planner
> --
>
> Key: CLOUDSTACK-9112
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9112
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.6.0
>Reporter: Harikrishna Patnala
>Assignee: Harikrishna Patnala
> Fix For: Future
>
>
> There are some VM deployment failures happening when multiple VMs are 
> deployed at a time, failures mainly due to NetworkModel code that iterates 
> over all the vlans in the pod. This causes each deployVM thread to hold the 
> global lock on Network longer and cause delays. This delay in turn causes 
> more threads to choose same host and fail since capacity is not available on 
> that host.
> Following are some changes required to be done to reduce delays during VM 
> deployments which in turn causes some vm deployment failures when multiple 
> VMs are launched at a time.
> - In Planner, remove the clusters that do not contain a host with matching 
> service offering tag. This will save some iterations over clusters that dont 
> have matching tagged host 
> - In NetworkModel, do not query the vlans for the pod within the loop. Also 
> optimized the logic to query the ip/ipv6 
> - In DeploymentPlanningManagerImpl, do not process the affinity group if the 
> plan has hostId provided.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9413) VmIpFetchTask NullPointerException

[Nathan Johnson (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895171#comment-15895171
 ] 

Nathan Johnson commented on CLOUDSTACK-9413:


We're seeing the same thing.  I think this might be caused by this line:

VMInstanceVO vmInstance = _vmInstanceDao.findById(vmId);

returning a null, and then being dereferenced on this line (2221 as of 4.8.0):

_vmIpFetchThreadExecutor.execute(new VmIpAddrFetchThread(vmId, nicId, 
vmInstance.getInstanceName(),

It would be easy enough to put some sort of guard around the instance name 
fetching, however I'm not sure what it actually means if there is no 
corresponding record in the vm_instance table, and what should happen here.

[~jayapal] do you have any thoughts?


> VmIpFetchTask NullPointerException
> --
>
> Key: CLOUDSTACK-9413
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9413
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.8.0
> Environment: CentOS 6.8 (latest)
>Reporter: Fabian Stelzer
>Priority: Minor
>
> I'm getting the following exception in the management server logs exactly 
> every 3 minutes. However i don't see any impact on production or management 
> functionality.
> [c.c.v.UserVmManagerImpl] (UserVm-Scavenger-1:ctx-33f26ddb) Caught the 
> Exception in VmIpFetchTask
> java.lang.NullPointerException
>   at 
> com.cloud.vm.UserVmManagerImpl$VmIpFetchTask.runInContext(UserVmManagerImpl.java:2221)
>   at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
>   at 
> org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
>   at 
> org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>   at 
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9821) Unable to deploy user VM in Basic Zone

[Mike Tutkowski (JIRA)]

Mike Tutkowski created CLOUDSTACK-9821:
--

 Summary: Unable to deploy user VM in Basic Zone
 Key: CLOUDSTACK-9821
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9821
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public (Anyone can view this level - this is the default.)
  Components: Network Controller
Affects Versions: 4.10.0.0, 4.10
 Environment: Ubuntu 12.04 for CS MS
Reporter: Mike Tutkowski
Priority: Blocker
 Fix For: 4.10.0.0, 4.10


>From my e-mails on dev@ concerning this issue (messages listed oldest to 
>newest):

I see the following exception when trying to deploy a user VM in a Basic Zone 
with two XenServer 6.5 hosts in one cluster. My system VMs have all deployed 
properly. The user template gets downloaded fine. I can see the user VM begin 
to start on a XenServer host, then it goes away. We then automatically try on 
the other host. I can see the VM begin to start there for a moment, then it 
goes away.

I am just deploying the user VM’s template and root disk to NFS (same place 
where the template and root disks of my system VMs are).

I am using the built-in XenServer CentOS 5.6 (64 bit) template with 1 vCPU, 500 
MHz, and 256 MB memory.

WARN  [c.c.a.r.v.VirtualRoutingResource] (DirectAgent-7:ctx-35aded78) 
(logid:aab9c320) Expected 1 answers while executing VmDataCommand but received 2
WARN  [c.c.v.VirtualMachinePowerStateSyncImpl] 
(DirectAgentCronJob-14:ctx-27fb1ac3) (logid:2c342f23) VM state was updated but 
update time is null?! vm id: 6
INFO  [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-2c7d2dce) 
(logid:a56a9a8c) Begin cleanup expired async-jobs
INFO  [o.a.c.f.j.i.AsyncJobManagerImpl] (AsyncJobMgr-Heartbeat-1:ctx-2c7d2dce) 
(logid:a56a9a8c) End cleanup expired async-jobs
INFO  [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-383a632c) 
(logid:541e9ba5) Found 0 removed accounts to cleanup
INFO  [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-383a632c) 
(logid:541e9ba5) Found 0 disabled accounts to cleanup
INFO  [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-383a632c) 
(logid:541e9ba5) Found 0 inactive domains to cleanup
INFO  [c.c.u.AccountManagerImpl] (AccountChecker-1:ctx-383a632c) 
(logid:541e9ba5) Found 0 disabled projects to cleanup
WARN  [c.c.h.x.r.CitrixResourceBase] (DirectAgent-16:ctx-7c901443) 
(logid:aab9c320) callHostPlugin failed for cmd: default_network_rules with args 
secIps: 0:, vmName: i-2-6-VM, vmID: 6, vmIP: 10.117.40.53, vmMAC: 
06:b2:f4:00:00:22,  due to There was a failure communicating with the plugin.
WARN  [c.c.h.x.r.w.x.CitrixStartCommandWrapper] (DirectAgent-16:ctx-7c901443) 
(logid:aab9c320) Catch Exception: class 
com.cloud.utils.exception.CloudRuntimeException due to 
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: 
default_network_rules with args secIps: 0:, vmName: i-2-6-VM, vmID: 6, vmIP: 
10.117.40.53, vmMAC: 06:b2:f4:00:00:22,  due to There was a failure 
communicating with the plugin.
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: 
default_network_rules with args secIps: 0:, vmName: i-2-6-VM, vmID: 6, vmIP: 
10.117.40.53, vmMAC: 06:b2:f4:00:00:22,  due to There was a failure 
communicating with the plugin.
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:338)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:188)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixStartCommandWrapper.execute(CitrixStartCommandWrapper.java:53)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1691)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 

[jira] [Commented] (CLOUDSTACK-9198) VR gets created in the disabled POD

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895091#comment-15895091
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9198:


Github user GabrielBrascher commented on the issue:

https://github.com/apache/cloudstack/pull/1278
  
@anshul1886 I would like to raise the point previously discussed by me and 
@rafaelweingartner. I think that we should pay attention if the change of user 
and caller will really do the job. So far I do not see how this PR changes the 
behavior.

Basically this code changes two parameters in startVirtualRouter 
[_callerUser_ and _caller_ when calling startVirtualRouter(router, callerUser, 
caller, routerDeploymentDefinition.getParams())]. However, those parameters are 
only used inside startVirtualRouter when calling the method start(router, user, 
caller, params, null).

```
if (router.getRole() != Role.VIRTUAL_ROUTER || 
!router.getIsRedundantRouter()) {
return start(router, user, caller, params, null);
}
```

The problem is that the method **start** does not use either the _user_ and 
the _caller_ parameters in the overridden implementation (the one that you are 
using).

```
protected DomainRouterVO start(DomainRouterVO router, final User user, 
final Account caller, final Map params, final DeploymentPlan 
planToDeploy)
throws StorageUnavailableException, 
InsufficientCapacityException, ConcurrentOperationException, 
ResourceUnavailableException {
s_logger.debug("Starting router " + router);
try {
_itMgr.advanceStart(router.getUuid(), params, planToDeploy, 
null);
} catch (final OperationTimedoutException e) {
throw new ResourceUnavailableException("Starting router " + 
router + " failed! " + e.toString(), DataCenter.class, 
router.getDataCenterId());
}
if (router.isStopPending()) {
s_logger.info("Clear the stop pending flag of router " + 
router.getHostName() + " after start router successfully!");
router.setStopPending(false);
router = _routerDao.persist(router);
}
// We don't want the failure of VPN Connection affect the status of
// router, so we try to make connection
// only after router start successfully
final Long vpcId = router.getVpcId();
if (vpcId != null) {
_s2sVpnMgr.reconnectDisconnectedVpnByVpc(vpcId);
}
return _routerDao.findById(router.getId());
}
```

Sorry, but I can't see how your code alters the behavior as intended. Can 
you please show that by changing the parameters _user_ and _caller_ you are 
changing the behavior?

Thanks in advance.


> VR gets created in the disabled POD
> ---
>
> Key: CLOUDSTACK-9198
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9198
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>
> VR gets created in the disabled POD



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895069#comment-15895069
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9814:


Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack/pull/1987
  
@niteshsarda I suggest you adding line 2281 from "managementService" to 
"domainMgr". The only difference between those two methods is this line. 
Assuming that you changed the method calls, and then everything started 
working. 

Then, please delete the 
com.cloud.server.ManagementServerImpl.updateDomain(UpdateDomainCmd), it is not 
used. It is incredible to have a method with ~100 duplicated between classes.



> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : Sample
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9815) Application Container Service

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895045#comment-15895045
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9815:


GitHub user DaanHoogland opened a pull request:

https://github.com/apache/cloudstack/pull/1988

WIP: CLOUDSTACK-9815 intergration of ApplicationClusterService

  this external plugin will be integrated as core plugin. It was originally 
created as plugin on 4.5. bouncycaste needs updating and several integration 
problems are still blocking a merge.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/shapeblue/cloudstack application-clusters

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1988.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 #1988


commit ad03449239df0d17ef9dfd9bede96081d9e657e4
Author: Daan Hoogland 
Date:   2017-03-03T20:56:53Z

intergration of ContainerClusterService as ApplicationClusterService
  this external plugin will be integrated as core plugin




> Application Container Service
> -
>
> Key: CLOUDSTACK-9815
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9815
> Project: CloudStack
>  Issue Type: New Feature
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Daan Hoogland
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9820) simplify application_cluster_details

[Daan Hoogland (JIRA)]

Daan Hoogland created CLOUDSTACK-9820:
-

 Summary: simplify application_cluster_details
 Key: CLOUDSTACK-9820
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9820
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Daan Hoogland


this could be a key/value table that is up to the application to decide how to 
fill.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9819) generalize functionality and supply proper hook

[Daan Hoogland (JIRA)]

Daan Hoogland created CLOUDSTACK-9819:
-

 Summary: generalize functionality and supply proper hook
 Key: CLOUDSTACK-9819
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9819
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Daan Hoogland


extract any k8 specific code



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9689) [Hyper-V] VM console is freezing sometimes

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895032#comment-15895032
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9689:


Github user ramkatru commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1845#discussion_r104242930
  
--- Diff: 
services/console-proxy-rdp/rdpconsole/src/main/java/streamer/apr/AprSocketSource.java
 ---
@@ -103,44 +103,46 @@ public void poll(boolean block) {
 if (verbose)
 System.out.println("[" + this + "] INFO: Reading data from 
stream.");
 
-// to unblock during reboot
-long startTime = System.currentTimeMillis();
 // FIXME: If pull is destroyed or socket is closed, segfault 
will happen here
-int actualLength = (block) ? // Blocking read
-Socket.recv(socket, buf.data, buf.offset, 
buf.data.length - buf.offset)
-: // Non-blocking read
-Socket.recvt(socket, buf.data, buf.offset, 
buf.data.length - buf.offset, 500);
+int actualLength;
+if(block) {
+// Blocking read
+actualLength = Socket.recv(socket, buf.data, buf.offset, 
buf.data.length - buf.offset);
+} else {
+// non blocking read with 5 seconds timeout
+Socket.timeoutSet(socket, 500);
+actualLength = Socket.recv(socket, buf.data, buf.offset, 
buf.data.length - buf.offset);
--- End diff --

@anshul1886 can you please verify if timeout can be set on a socket that is 
not opened with APR_SO_NONBLOCK flag?


> [Hyper-V] VM console is freezing sometimes
> --
>
> Key: CLOUDSTACK-9689
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9689
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>
> With some VMs console is freezing very frequently and becomes unresponsive



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9818) review and update documentation

[Daan Hoogland (JIRA)]

Daan Hoogland created CLOUDSTACK-9818:
-

 Summary: review and update documentation
 Key: CLOUDSTACK-9818
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9818
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Daan Hoogland






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9817) create test automation for known supported applications

[Daan Hoogland (JIRA)]

Daan Hoogland created CLOUDSTACK-9817:
-

 Summary: create test automation for known supported applications
 Key: CLOUDSTACK-9817
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9817
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Daan Hoogland






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9816) fix bouncy castle version

[Daan Hoogland (JIRA)]

Daan Hoogland created CLOUDSTACK-9816:
-

 Summary: fix bouncy castle version
 Key: CLOUDSTACK-9816
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9816
 Project: CloudStack
  Issue Type: Sub-task
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Daan Hoogland






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (CLOUDSTACK-9815) Application Container Service

[Daan Hoogland (JIRA)]

Daan Hoogland created CLOUDSTACK-9815:
-

 Summary: Application Container Service
 Key: CLOUDSTACK-9815
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9815
 Project: CloudStack
  Issue Type: New Feature
  Security Level: Public (Anyone can view this level - this is the default.)
Reporter: Daan Hoogland






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9604) Root disk resize support for VMware and XenServer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895022#comment-15895022
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9604:


Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1813
  
Still fails but error is different now
Exception: Job failed: {jobprocstatus : 0, created : 
u'2017-03-03T09:20:53+', jobresult : {errorcode : 530, errortext : u'Unable 
to start a VM due to insufficient capacity'}, cmd : 
u'org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin', userid : 
u'83ba8c54-ffed-11e6-b1e4-067b8a010729', jobstatus : 2, jobid : 
u'2d7de855-e6d8-4b06-83c4-c880e75c6fb1', jobresultcode : 530, jobinstanceid : 

@borisstoyanov It would be awesome if we can get management server log 
around the exception.


> Root disk resize support for VMware and XenServer
> -
>
> Key: CLOUDSTACK-9604
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9604
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Priyank Parihar
>Assignee: Priyank Parihar
> Attachments: 1.png, 2.png, 3.png
>
>
> Currently the root size of an instance is locked to that of the template. 
> This creates unnecessary template duplicates, prevents the creation of a 
> market place, wastes time and disk space and generally makes work more 
> complicated.
> Real life example - a small VPS provider might want to offer the following 
> sizes (in GB):
> 10,20,40,80,160,240,320,480,620
> That's 9 offerings.
> The template selection could look like this, including real disk space used:
> Windows 2008 ~10GB
> Windows 2008+Plesk ~15GB
> Windows 2008+MSSQL ~15GB
> Windows 2012 ~10GB
> Windows 2012+Plesk ~15GB
> Windows 2012+MSSQL ~15GB
> CentOS ~1GB
> CentOS+CPanel ~3GB
> CentOS+Virtualmin ~3GB
> CentOS+Zimbra ~3GB
> CentOS+Docker ~2GB
> Debian ~1GB
> Ubuntu LTS ~1GB
> In this case the total disk space used by templates will be 828 GB, that's 
> almost 1 TB. If your storage is expensive and limited SSD this can get 
> painful!
> If the root resize feature is enabled we can reduce this to under 100 GB.
> Specifications and Description 
> Administrators don't want to deploy duplicate OS templates of differing 
> sizes just to support different storage packages. Instead, the VM deployment 
> can accept a size for the root disk and adjust the template clone 
> accordingly. In addition, CloudStack already supports data disk resizing for 
> existing volumes, we can extend that functionality to resize existing root 
> disks. 
>   As mentioned, we can leverage the existing design for resizing an existing 
> volume. The difference with root volumes is that we can't resize via disk 
> offering, therefore we need to verify that no disk offering was passed, just 
> a size. The existing enforcements of new size > existing size will still 
> server their purpose.
>For deployment-based resize (ROOT volume size different from template 
> size), we pass the rootdisksize parameter when the existing code allocates 
> the root volume. In the process, we validate that the root disk size is > 
> existing template size, and non-zero. This will persist the root volume as 
> the desired size regardless of whether or not the VM is started on deploy. 
> Then hypervisor specific code needs to be made to pay attention to the 
> VolumeObjectTO's size attribute and use that when doing the work of cloning 
> from template, rather than inheriting the template's size. This can be 
> implemented one hypervisor at a time, and as such there needs to be a check 
> in UserVmManagerImpl to fail unsupported hypervisors with 
> InvalidParameterValueException when the rootdisksize is passed.
>
> Hypervisor specific changes
> XenServer
> Resize ROOT volume is only supported for stopped VMs
> Newly created ROOT volume will be resized after clone from template
> VMware  
> Resize ROOT volume is only supported for stopped VMs.
> New size should be large then the previous size.
> Newly created ROOT volume will be resized after clone from template iff
>  There is no root disk chaining.(means use Full clone)
> And Root Disk controller setting is not  IDE.
> Previously created Root Volume could be resized iif
> There is no root disk chaining.
> And Root Disk controller setting is not  IDE.
> Web Services APIs
> resizeVolume API call will not change, but it will accept volume UUIDs of 
> root volumes in id parameter for resizing.
> deployVirtualMachine API call will allow new rootdisksize parameter to be 
> passed. This parameter will be used as the disk size (in GB) when cloning 
> from template.
> UI
> 1) (refer attached image 1) shows UI that resize volume option is added for 

[jira] [Commented] (CLOUDSTACK-9604) Root disk resize support for VMware and XenServer

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15895013#comment-15895013
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9604:


Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1813
  
Trillian test result (tid-927)
Environment: vmware-55u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 44318 seconds
Marvin logs: 
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr1813-t927-vmware-55u3.zip
Intermitten failure detected: 
/marvin/tests/smoke/test_deploy_vm_root_resize.py
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: 
/marvin/tests/smoke/test_routers_network_ops.py
Intermitten failure detected: /marvin/tests/smoke/test_snapshots.py
Intermitten failure detected: /marvin/tests/smoke/test_vm_snapshots.py
Test completed. 45 look ok, 4 have error(s)


Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_01_test_vm_volume_snapshot | `Failure` | 337.78 | test_vm_snapshots.py
test_04_rvpc_privategw_static_routes | `Failure` | 843.48 | 
test_privategw_acl.py
test_02_list_snapshots_with_removed_data_store | `Error` | 81.00 | 
test_snapshots.py
test_02_list_snapshots_with_removed_data_store | `Error` | 86.09 | 
test_snapshots.py
test_00_deploy_vm_root_resize | `Error` | 157.40 | 
test_deploy_vm_root_resize.py
test_01_vpc_site2site_vpn | Success | 376.44 | test_vpc_vpn.py
test_01_vpc_remote_access_vpn | Success | 161.93 | test_vpc_vpn.py
test_01_redundant_vpc_site2site_vpn | Success | 598.35 | test_vpc_vpn.py
test_02_VPC_default_routes | Success | 389.68 | test_vpc_router_nics.py
test_01_VPC_nics_after_destroy | Success | 786.48 | test_vpc_router_nics.py
test_05_rvpc_multi_tiers | Success | 673.21 | test_vpc_redundant.py
test_04_rvpc_network_garbage_collector_nics | Success | 1549.38 | 
test_vpc_redundant.py
test_03_create_redundant_VPC_1tier_2VMs_2IPs_2PF_ACL_reboot_routers | 
Success | 738.76 | test_vpc_redundant.py
test_02_redundant_VPC_default_routes | Success | 660.05 | 
test_vpc_redundant.py
test_01_create_redundant_VPC_2tiers_4VMs_4IPs_4PF_ACL | Success | 1376.11 | 
test_vpc_redundant.py
test_09_delete_detached_volume | Success | 31.00 | test_volumes.py
test_06_download_detached_volume | Success | 50.61 | test_volumes.py
test_05_detach_volume | Success | 110.34 | test_volumes.py
test_04_delete_attached_volume | Success | 15.24 | test_volumes.py
test_03_download_attached_volume | Success | 20.31 | test_volumes.py
test_02_attach_volume | Success | 58.76 | test_volumes.py
test_01_create_volume | Success | 524.94 | test_volumes.py
test_change_service_offering_for_vm_with_snapshots | Success | 584.65 | 
test_vm_snapshots.py
test_03_delete_vm_snapshots | Success | 275.23 | test_vm_snapshots.py
test_02_revert_vm_snapshots | Success | 232.19 | test_vm_snapshots.py
test_01_create_vm_snapshots | Success | 161.71 | test_vm_snapshots.py
test_deploy_vm_multiple | Success | 247.59 | test_vm_life_cycle.py
test_deploy_vm | Success | 0.03 | test_vm_life_cycle.py
test_advZoneVirtualRouter | Success | 0.02 | test_vm_life_cycle.py
test_10_attachAndDetach_iso | Success | 26.83 | test_vm_life_cycle.py
test_09_expunge_vm | Success | 125.23 | test_vm_life_cycle.py
test_08_migrate_vm | Success | 66.07 | test_vm_life_cycle.py
test_07_restore_vm | Success | 0.10 | test_vm_life_cycle.py
test_06_destroy_vm | Success | 10.17 | test_vm_life_cycle.py
test_03_reboot_vm | Success | 5.15 | test_vm_life_cycle.py
test_02_start_vm | Success | 20.30 | test_vm_life_cycle.py
test_01_stop_vm | Success | 10.15 | test_vm_life_cycle.py
test_CreateTemplateWithDuplicateName | Success | 216.47 | test_templates.py
test_08_list_system_templates | Success | 0.03 | test_templates.py
test_07_list_public_templates | Success | 0.04 | test_templates.py
test_05_template_permissions | Success | 0.06 | test_templates.py
test_04_extract_template | Success | 10.24 | test_templates.py
test_03_delete_template | Success | 5.14 | test_templates.py
test_02_edit_template | Success | 90.12 | test_templates.py
test_01_create_template | Success | 110.83 | test_templates.py
test_10_destroy_cpvm | Success | 266.91 | test_ssvm.py
test_09_destroy_ssvm | Success | 243.85 | test_ssvm.py
test_08_reboot_cpvm | Success | 156.62 | test_ssvm.py
test_07_reboot_ssvm | Success | 158.51 | test_ssvm.py
test_06_stop_cpvm | Success | 211.98 | test_ssvm.py
test_05_stop_ssvm | Success | 183.83 | test_ssvm.py
test_04_cpvm_internals | Success | 1.26 | test_ssvm.py
test_03_ssvm_internals | Success | 3.46 | test_ssvm.py
test_02_list_cpvm_vm | Success | 0.14 | 

[jira] [Commented] (CLOUDSTACK-9705) Unauthenticated API allows Admin password reset

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894958#comment-15894958
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9705:


Github user ramkatru commented on the issue:

https://github.com/apache/cloudstack/pull/1865
  
tag:mergeready


> Unauthenticated API allows Admin password reset
> ---
>
> Key: CLOUDSTACK-9705
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9705
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Anshul Gangwar
>Assignee: Anshul Gangwar
>
> The "unauthenticated API" allows a caller to reset CloudStack administrator 
> passwords. This presents a security risk becaues it allows for privilege 
> escallation attacks. First, if the unauthenticated API is listening on the 
> network (instead of locally) then any user on the network can reset admin 
> passwords. If, the API is only listening locally, then any user with access 
> to the local box can resset admin passwords. This would allow them to access 
> other hosts within the cloudstack deployment.
> While it may be important to provide a recovery mechanism for admin passwords 
> that have been lost or hyjacked, such a solution needs to be secure. We 
> should either remove this feature from the Unauthenticated API, or provide a 
> solution that is less open to abuse.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-8862) Issuing multiple attach-volume commands simultaneously can be problematic

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894943#comment-15894943
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8862:


Github user ramkatru commented on the issue:

https://github.com/apache/cloudstack/pull/1900
  
tag:mergeready


> Issuing multiple attach-volume commands simultaneously can be problematic
> -
>
> Key: CLOUDSTACK-8862
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8862
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.5.0, 4.5.1, 4.5.2, 4.6.0
> Environment: N/A
>Reporter: Mike Tutkowski
> Fix For: Future
>
>
> If a user submits two volumeAttach commands around the same time, the first 
> one can succeed while the second one can fail and can lead CloudStack to ask 
> the underlying storage plug-in to remove the volume from a given ACL (but the 
> volume should be in the ACL because the first attachVolume command succeeded).
> A somewhat similar problem can happen if you submit the second attachVolume 
> command to another VM in the same cluster.
> Proposed solution:
> A data volume should make use of a new column in the volumes table: 
> attach_state (or some name like that).
> This column can have five possible values: null (for root disks), detached 
> (default state for data volumes), attaching, attached, and detaching.
> When an attachVolume command is submitted, the volume should immediately be 
> placed into the "attaching" state. If a transition to that state is not 
> possible, an exception is thrown (for example, if you're already in the 
> "attached" state, you can't transition to the "attaching" state).
> A similar kind of logic already exists for volume snapshots.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9165) unable to use reserved IP range in a network for external VMs

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894729#comment-15894729
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9165:


Github user cloudmonger commented on the issue:

https://github.com/apache/cloudstack/pull/1246
  
### ACS CI BVT Run
 **Sumarry:**
 Build Number 419
 Hypervisor xenserver
 NetworkType Advanced
 Passed=103
 Failed=2
 Skipped=7

_Link to logs Folder (search by build_no):_ 
https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0


**Failed tests:**
* test_volumes.py

 * test_06_download_detached_volume Failed

* test_routers_network_ops.py

 * test_02_RVR_Network_FW_PF_SSH_default_routes_egress_false Failed


**Skipped tests:**
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm

**Passed test suits:**
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


> unable to use reserved IP range in a network for external VMs
> -
>
> Key: CLOUDSTACK-9165
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9165
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: sudharma jain
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9795) VRs used as VPC Routers have logrotate in cron.daily instead of cron.hourly

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894597#comment-15894597
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9795:


Github user dmabry closed the pull request at:

https://github.com/apache/cloudstack/pull/1974


> VRs used as VPC Routers have logrotate in cron.daily instead of cron.hourly
> ---
>
> Key: CLOUDSTACK-9795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9795
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VPC
>Affects Versions: 4.8.0, 4.9.0, 4.8.1.1, 4.9.0.1
> Environment: The VR when deploy as a stand alone router has logrotate 
> moved from cron.daily to cron.hourly, but when used as a VPC router 
> (vpcrouter) the logrotate file is left in cron.daily.
>Reporter: David Mabry
>Priority: Minor
>  Labels: easyfix
> Fix For: 4.10
>
>
> The VR when deploy as a stand alone router has logrotate moved from 
> cron.daily to cron.hourly, but when used as a VPC router (vpcrouter) the 
> logrotate file is left in cron.daily.
> This causes anyone using the VR as a VPC to have issues with /var/log filling 
> up and causing the VR to fail ungracefully.  This prevents VMs from spinning 
> up in the VPC, adding new acls and creating new LB rules.
> The fix is to move the logrotate from cron.daily to cron.hourly and configure 
> cloud.log to rotate and compress at 20MB.  I will submit a PR against master 
> that will move logrotate.  It is a minor change to cloud-early on the VRs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9795) VRs used as VPC Routers have logrotate in cron.daily instead of cron.hourly

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894596#comment-15894596
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9795:


Github user dmabry commented on the issue:

https://github.com/apache/cloudstack/pull/1974
  
Thanks @rhtyd!


> VRs used as VPC Routers have logrotate in cron.daily instead of cron.hourly
> ---
>
> Key: CLOUDSTACK-9795
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9795
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VPC
>Affects Versions: 4.8.0, 4.9.0, 4.8.1.1, 4.9.0.1
> Environment: The VR when deploy as a stand alone router has logrotate 
> moved from cron.daily to cron.hourly, but when used as a VPC router 
> (vpcrouter) the logrotate file is left in cron.daily.
>Reporter: David Mabry
>Priority: Minor
>  Labels: easyfix
> Fix For: 4.10
>
>
> The VR when deploy as a stand alone router has logrotate moved from 
> cron.daily to cron.hourly, but when used as a VPC router (vpcrouter) the 
> logrotate file is left in cron.daily.
> This causes anyone using the VR as a VPC to have issues with /var/log filling 
> up and causing the VR to fail ungracefully.  This prevents VMs from spinning 
> up in the VPC, adding new acls and creating new LB rules.
> The fix is to move the logrotate from cron.daily to cron.hourly and configure 
> cloud.log to rotate and compress at 20MB.  I will submit a PR against master 
> that will move logrotate.  It is a minor change to cloud-early on the VRs.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-4238) invalid username and password when loggin in

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-4238.

Resolution: Fixed

> invalid username and password when loggin in
> 
>
> Key: CLOUDSTACK-4238
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4238
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup, Management Server
>Affects Versions: 4.1.0
> Environment: Distributor ID: Ubuntu
> Description:Ubuntu 12.04.2 LTS
> Release:12.04
> Codename:   precise
> CloudStack version 4.1.1-1 using the 
>Reporter: John Cabs
>Priority: Minor
>
> I installed cloudstack 4.1 from scratch with fresh Ubuntu OS. after the 
> installation, I hit this issue:
> 1. first time to login to the UI but it pops-up with "invalid username and 
> password"
> 2. restart the server, went to the UI and again it shows the same error
> Alternative Solution:
> I went to the logs /var/log/cloudstack/management/management-server.log wait 
> for the "Admin user enabled" to show and then I tried to login and it was 
> successful.
> 2013-08-12 00:37:05,843 INFO  [cloud.server.ManagementServerImpl] 
> (Timer-1:null) Startup CloudStack management server...
> 2013-08-12 00:37:06,012 INFO  [cloud.server.ManagementServerImpl] 
> (Timer-1:null) Admin user enabled
> Is there a way to lessen the waiting time?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-1870) Implement a 512 bit salted SHA authenticator/encoder for cloudstack

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-1870.

Resolution: Fixed

> Implement a 512 bit salted SHA authenticator/encoder for cloudstack
> ---
>
> Key: CLOUDSTACK-1870
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1870
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Venkata Siva Vijayendra Bhamidipati
>Assignee: Chip Childers
>Priority: Minor
> Fix For: Future
>
>
> As of now SHA 256 bit salted authentication is the best level of security we 
> have for users in cloudstack. Implement a SHA 512 bit salted authenticator 
> for better security.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-2213) russian language select failure

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-2213.

Resolution: Fixed

> russian language select failure
> ---
>
> Key: CLOUDSTACK-2213
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2213
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.0.1, 4.0.2
> Environment: centos 6.4 / kvm
>Reporter: Valery Ciareszka
>Priority: Minor
> Fix For: Future
>
> Attachments: css_missing.jpg, messages_ru_RU.properties.jpg, 
> syntaxerror.jpg
>
>
> 1. setup cloudstack management
> 2. open it in web browser
> 3. choose russian language
> 4. try to login
> you will see blank page
> This issue is caused by 2(at least) problems:
> 1. one incorrect translation string variable 
> message.action.change.service.warning.for.router in 
> /usr/share/cloud/management/webapps/client/WEB-INF/classes/resources/messages_ru_RU.properties
>  - there is \n symbol there instead of translated version
> 2. missing 
> /usr/share/cloud/management/webapps/client/css/cloudstack3.ru_RU.css file 
> I replaced variable message.action.change.service.warning.for.router with 
> proper text and copied css from  
> /usr/share/cloud/management/webapps/client/css/cloudstack3.ja.css to get 
> quick fix



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-1702) Error messages returning numeric ID's in some places instead of UUIDs

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-1702.

Resolution: Fixed

> Error messages returning numeric ID's in some places instead of UUIDs
> -
>
> Key: CLOUDSTACK-1702
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1702
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.0.0, 4.1.0, 4.2.0
>Reporter: Chip Childers
>Priority: Minor
>
> As reported by George here:
> http://markmail.org/message/ldmbf2i77tgrai7f



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-963) [cloud.utils.AnnotationHelper] class java.lang.Stringdoes not have a Table annotation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-963.
-
Resolution: Fixed

> [cloud.utils.AnnotationHelper]  class java.lang.Stringdoes not have a Table 
> annotation
> --
>
> Key: CLOUDSTACK-963
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-963
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
> Environment: Running on cloudstack - master branch
>Reporter: Prasanna Santhanam
>Priority: Minor
> Fix For: Future
>
>
> whenever a host is added to cloudstack i see the INFO message in the logs 
> about missing Table annotation:
> Related to the recent cloud-utils refactor? The message also doesn't seem to 
> indicate any INFO, proobably a WARN/ERROR?
> 2013-01-11 23:42:39,985 INFO  [xen.discoverer.XcpServerDiscoverer] 
> (1589138432@qtp-1513148157-5:null) Found host acs-qa-h20 ip=10.223.78.20 
> product version=6.0.2
> 2013-01-11 23:42:39,993 INFO  [cloud.utils.AnnotationHelper] 
> (1589138432@qtp-1513148157-5:null) 
> class java.lang.Stringdoes not have a Table annotation
> 2013-01-11 23:42:39,993 DEBUG [cloud.network.NetworkManagerImpl] 
> (1589138432@qtp-1513148157-5:null) Failed to retrive the default label for 
> storage traffic:zone: 1 hypervisor: XenServer due to:Unable to find the 
> default physical network with traffic=Storage in the specified zone id
> --
> 2013-01-11 23:43:05,008 DEBUG [cloud.api.ApiServlet] 
> (1513306926@qtp-1513148157-0:null) ===START===  0:0:0:0:0:0:0:1 -- GET  
> allocationstate=Enabled=W7IfidZg8KCiCjO8X-jB46-BdndysOb1SvbDht3XdDBT99gWfPm6Z36Rk52j0IWrtMJZL6ItPV1AEhCoQMSVRA=updateZone=7b21e7ea-969d-49d9-8293-5ebea8be4cea=json=d7hpLc16eXvooaq%2BQMbaVy4E9qE%3D
> 2013-01-11 23:43:05,049 INFO  [cloud.utils.AnnotationHelper] 
> (1513306926@qtp-1513148157-0:null) 
> class java.lang.Stringdoes not have a Table annotation
> 2013-01-11 23:43:05,070 INFO  [cloud.configuration.ConfigurationManagerImpl] 
> (1513306926@qtp-1513148157-0:null) No storage traffic type was specified by 
> admin, create default storage traffic on physical network 200 with same 
> configure of management traffic type
> --
> 2013-01-11 23:43:46,675 INFO  [xen.discoverer.XcpServerDiscoverer] 
> (1513306926@qtp-1513148157-0:null) Found host acs-qa-h21 ip=10.223.78.140 
> product version=6.0.2
> 2013-01-11 23:43:46,681 INFO  [cloud.utils.AnnotationHelper] 
> (1513306926@qtp-1513148157-0:null) 
> class java.lang.Stringdoes not have a Table annotation



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1284) UI - Tooltip - Inconsistent tool tip rendering among installation wizards

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1284.
--
Resolution: Fixed

> UI - Tooltip - Inconsistent tool tip rendering among installation wizards
> -
>
> Key: CLOUDSTACK-1284
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1284
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.1.0, 4.2.0
> Environment: RHEL 6.3 Build #15
>Reporter: Parth Jagirdar
>Priority: Minor
> Attachments: 4 (1).jpg
>
>
> ToolTips on Basic Zone installation wizard (The one you get at upon a fresh 
> install just after Login page) have Heading/Title "Hints" which is 
> inconsistent with all other tooltips presented in other wizards. (Screen 4)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-4071) [UI] - Word 'Default' is misspelled in descripiton of integration.api.port under Global settings.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-4071.

Resolution: Fixed

> [UI] - Word 'Default' is misspelled in descripiton of integration.api.port 
> under Global settings. 
> --
>
> Key: CLOUDSTACK-4071
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4071
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
> Environment: Build: CloudPlatform-4.2-335-rhel6.3
>Reporter: Pradeep S
>Assignee: Jessica Wang
>Priority: Minor
> Fix For: Future
>
> Attachments: api.JPG
>
>
> Default is misspelled as "Defaul" in description of integration.api.port.
> Screenshot is attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-4055) Windows Server 2012 (64-Bit) being deployed as 'Other OS' type

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-4055.

Resolution: Fixed

> Windows Server 2012 (64-Bit) being deployed as 'Other OS' type
> --
>
> Key: CLOUDSTACK-4055
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4055
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.2.0
>Reporter: Ahmad Emneina
>Priority: Minor
> Fix For: Future
>
> Attachments: win2012_other_os.png
>
>
> Registered a Windows Server 2012 64-bit template in ACS and made sure Windows 
> Server 2012 (64-Bit) was selected as the OS type when registering the 
> template, however when we build an instance in CS it creates the OS type in 
> VMware as Other (64-Bit). Running VMware 5.1.0 and have confirmed that the OS 
> type is an available option in VMware.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-8873) listLoadBalancerRules response JSON publicport/privateport not an int, zonename missing

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-8873.
--
Resolution: Fixed

> listLoadBalancerRules response JSON publicport/privateport not an int, 
> zonename missing
> ---
>
> Key: CLOUDSTACK-8873
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8873
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: René Moser
>Priority: Trivial
> Fix For: Future
>
>
> h2. actual
> {code:none}
> {
>   "count": 1, 
>   "loadbalancerrule": [
> {
>   "account": "foo", 
>   "algorithm": "source", 
>   "cidrlist": "", 
>   "domain": "STXT", 
>   "domainid": "3a291b29-b184-4ddc-bdcc-8298c237942e", 
>   "id": "22bf1066-8bc3-425d-a213-a49431f7b865", 
>   "name": "foo", 
>   "networkid": "48df88b1-c2e2-432d-811a-681a2be74dde", 
>   "privateport": "80", 
>   "publicip": "1.2.4.5", 
>   "publicipid": "5d94a86d-0ee9-429a-9a5b-f57da4ee60cb", 
>   "publicport": "80", 
>   "state": "Add", 
>   "tags": [], 
>   "zoneid": "9e683e49-f4db-4b44-82ad-708689e9c4c8"
> }
>   ]
> }
> {code}
> h2. expected
> {code:none}
> {
>   "count": 1, 
>   "loadbalancerrule": [
> {
>   "account": "foo", 
>   "algorithm": "source", 
>   "cidrlist": "", 
>   "domain": "STXT", 
>   "domainid": "3a291b29-b184-4ddc-bdcc-8298c237942e", 
>   "id": "22bf1066-8bc3-425d-a213-a49431f7b865", 
>   "name": "foo", 
>   "networkid": "48df88b1-c2e2-432d-811a-681a2be74dde", 
>   "privateport": 80, 
>   "publicip": "1.2.4.5", 
>   "publicipid": "5d94a86d-0ee9-429a-9a5b-f57da4ee60cb", 
>   "publicport": 80, 
>   "state": "Add", 
>   "tags": [], 
>   "zoneid": "9e683e49-f4db-4b44-82ad-708689e9c4c8"
>   "zonename": "myzone"
> }
>   ]
> }
> {code}
> *Note: also check the response for createLoadBalancerRule when fixing this!*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2785) Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, infrastructure.css

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2785.
--
Resolution: Fixed

> Missing css files : vnmcAsa1000v.css, vnmcNetworkProvider.css, 
> infrastructure.css
> -
>
> Key: CLOUDSTACK-2785
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2785
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
> Environment: Master
>Reporter: Isaac Chiang
>Priority: Minor
>  Labels: ui
> Attachments: Screen Shot 2013-05-31 at 5.29.05 PM.png
>
>
> The following css files are failed to include : vnmcAsa1000v.css, 
> vnmcNetworkProvider.css, infrastructure.css



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-8368) [UI] Grouping/Categorization of Service Offerings

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-8368.
--
Resolution: Incomplete

Feature request that I did not understand the use and no one seemed to have 
worked on it

> [UI] Grouping/Categorization of Service Offerings
> -
>
> Key: CLOUDSTACK-8368
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8368
> Project: CloudStack
>  Issue Type: Wish
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Jan-Arve Nygård
>Priority: Trivial
>
> The option to group or categorize Service Offerings into groups would be 
> useful for installation with lots of different service offerings.
> This could done as a expandable list view per defined group. Maybe dynamic 
> groups based on host and storage tags could be an option as well.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2535) Cleanup port-profiles that gets created on Nexus switch as part of network cleanup

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2535.
--
Resolution: Fixed

> Cleanup port-profiles that gets created on Nexus switch as part of network 
> cleanup
> --
>
> Key: CLOUDSTACK-2535
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2535
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Devices
>Affects Versions: pre-4.0.0, 4.0.0
> Environment: Vmware
>Reporter: Koushik Das
>Assignee: Sateesh Chodapuneedi
>Priority: Minor
> Fix For: Future
>
>
> Port profiles are not cleaned up when a guest network using it gets removed. 
> As part of network shutdown all port profiles that got created on the Nexus 
> switch should be removed.
> The same problem is also there for vSwitch and dvSwitch.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1570) Document ability to manage basic and advanced zones

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1570.
--
Resolution: Fixed

> Document ability to manage basic and advanced zones
> ---
>
> Key: CLOUDSTACK-1570
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1570
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.2.0
>Reporter: Jessica Tomechak
>Priority: Minor
> Fix For: Future
>
>
> If there are changes to the UI, it could affect documentation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-5550) UI - Api key and secret key not fully visible in user detail view.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-5550.
--
Resolution: Fixed

> UI - Api key and secret key not fully visible in user detail view.
> --
>
> Key: CLOUDSTACK-5550
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5550
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.3.0
> Environment: Build from 4.3
>Reporter: Sangeetha Hariharan
>Priority: Minor
> Fix For: Future
>
> Attachments: api-key.png, secret-key.png
>
>
> UI - Api key and secret key not fully visible in user detail view.
> Steps to reproduce the problem:
> Go to Accounts->select any account and use "View users". 
> Select any user and generate keys.
> Notice that "api key" and "secret key" get truncated in the user detail view.
> Attaching screenshots:



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-5182) Doc issue - "HA-Enabled Virtual Machines" and "HA for Hosts" have same content

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-5182.
--
Resolution: Fixed

> Doc issue - "HA-Enabled Virtual Machines" and "HA for Hosts" have same content
> --
>
> Key: CLOUDSTACK-5182
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5182
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Shanker Balan
>Priority: Minor
>
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html-single/Admin_Guide/index.html#ha-enabled-vm
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html-single/Admin_Guide/index.html#ha-for-hosts
> 17.3. HA-Enabled Virtual Machines
> 17.4. HA for Hosts
> Both sections have same content as below:
> "The user can specify a virtual machine as HA-enabled. By default, all 
> virtual router VMs and Elastic Load Balancing VMs are automatically 
> configured as HA-enabled. When an HA-enabled VM crashes, CloudStack detects 
> the crash and restarts the VM automatically within the same Availability 
> Zone. HA is never performed across different Availability Zones. CloudStack 
> has a conservative policy towards restarting VMs and ensures that there will 
> never be two instances of the same VM running at the same time. The 
> Management Server attempts to start the VM on another Host in the same 
> cluster.
> HA features work with iSCSI or NFS primary storage. HA with local storage is 
> not supported."



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2616) com.mysql.jdbc.exceptions.jdbc4.CommunicationsException error is displayed in management server log after long time of inactive mysql connection

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2616.
--
Resolution: Fixed

> com.mysql.jdbc.exceptions.jdbc4.CommunicationsException error is displayed in 
> management server log after long time of inactive mysql connection
> 
>
> Key: CLOUDSTACK-2616
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2616
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0, 4.2.0
> Environment: Build from 4.1
>Reporter: Tetsuya Arita
>Priority: Minor
> Attachments: db.properties, jdbc-error.txt
>
>
> after a long time of inactivity, the following / attached error message is 
> displayed in management server.
> Then I cannot login to GUI for several times.
> after some trials, I can login to GUI.
> I attached management server log and db.properties.
> this error was duplicated to 
> https://issues.apache.org/jira/browse/CLOUDSTACK-1805 . 
> CLOUDSTACK-1805 was not resolved but closed. so I would like to open this 
> ticket to track.
> 2013-05-22 00:56:58,807 DEBUG [cloud.api.ApiServlet] (catalina-exec-1:null) 
> ===START===  103.2.128.24 -- POST  null
> 2013-05-22 00:56:58,810 ERROR [cloud.api.ApiServlet] (catalina-exec-1:null) 
> unknown exception writing api response
> com.cloud.utils.exception.CloudRuntimeException: DB Exception on: 
> com.mysql.jdbc.JDBC4PreparedStatement@65f65296: SELECT domain.id, 
> domain.parent, domain.name, domain.owner, domain.path, domain.level, 
> domain.removed, domain.child_count, domain.next_child_seq, domain.state, 
> domain.network_domain, domain.uuid FROM domain WHERE domain.path = _binary'/' 
>  AND domain.removed IS NULL  ORDER BY RAND() LIMIT 1
> at 
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:415)
> at 
> com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:350)
> at 
> com.cloud.utils.db.GenericDaoBase.findOneIncludingRemovedBy(GenericDaoBase.java:860)
> at 
> com.cloud.utils.db.GenericDaoBase.findOneBy(GenericDaoBase.java:871)
> at 
> com.cloud.domain.dao.DomainDaoImpl.findDomainByPath(DomainDaoImpl.java:200)
> at sun.reflect.GeneratedMethodAccessor351.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:39)
> at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
> at sun.proxy.$Proxy45.findDomainByPath(Unknown Source)
> at 
> com.cloud.user.DomainManagerImpl.findDomainByPath(DomainManagerImpl.java:175)
> at 
> com.cloud.user.DomainManagerImpl.findDomainByPath(DomainManagerImpl.java:62)
> at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at 

[jira] [Closed] (CLOUDSTACK-4018) LDAP:able to configure ldap with invalid queryfilter and search base values

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-4018.
--
Resolution: Fixed

> LDAP:able to configure ldap with invalid queryfilter and search base values
> ---
>
> Key: CLOUDSTACK-4018
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4018
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.2.0
>Reporter: sadhu suresh
>Priority: Minor
>
> try to provide invalid values for ldap query filter and search base
>  after (&(email=%e))  write any string it will accpet like " 
> (&(email=%e))sadhu"
> also for searchbase if we enter invalid values its accepting and registering 
> successfully
> http://10.147.59.126:8080/client/api?command=ldapConfig=CN%3Dtest%2CCN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcom=_=10.147.38.163=CN%3DUsers%2CDC%3Dhyd-qa%2CDC%3Dcom=(%26amp%3B(mail%3D%25e)sadhu=389=false=json=gNp53otI4v395R8Blh5OI7j59wE%3D
> { "ldapconfigresponse" :  { "ldapconfig" : 
> {"hostname":"10.147.38.163","port":"389","ssl":"false","searchbase":"CN=Users,DC=hyd-qa,DC=com","queryfilter":"((mail=%e)sadhu","binddn":"CN=test,CN=Users,DC=hyd-qa,DC=com"}
>  }  }



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-7819) Cannot add tags to project

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-7819.
--
Resolution: Invalid

> Cannot add tags to project
> --
>
> Key: CLOUDSTACK-7819
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7819
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.4.1
>Reporter: Bartek Sierakowski
>Priority: Trivial
> Attachments: man_server.log
>
>
> User(project admin) can not add tag to the project via GUI or API.
> GUI error: ! Status Acct [UUID username] does not have permission to operate 
> within domain id=1
> I management server logs in attached file.
> To reproduce: logon as non privileged user, create a project, try to add tag



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-4883) Installing New Memory in XenServer is not Detected

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-4883.
--
Resolution: Fixed

> Installing New Memory in XenServer is not Detected
> --
>
> Key: CLOUDSTACK-4883
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4883
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Hypervisor Controller
>Affects Versions: 4.2.0
> Environment: XenServer 6.2
>Reporter: Soheil Eizadi
>Assignee: Abhinandan Prateek
>Priority: Minor
>
> I had a use case where my XenServer ran out of memory and I could not
> create any more instances on CloudStack.
> I shutdown the XenServer and increased the memory on XenServer and
> brought up the Management Server again, but the Management Server still
> sees the old values, however the Stats from the Host view show the correct 
> memory.
> -Soheil
> 
> From: Nitin Mehta [nitin.me...@citrix.com]
> Sent: Wednesday, October 16, 2013 12:15 PM
> To: d...@cloudstack.apache.org
> Subject: Re: XenServer Memory Increase Problem
> Soheil - I guess this is a bug that addition of new memory isn't detected.
> File it if not already done.
> I would suggest you to change the DB as of now. Right tables are host and
> op_host_capacity (capacity_type=0).
> You might have to keep in mind the over provisioning factors you have
> kept. See if changing it works.
> On 16/10/13 11:56 AM, "Soheil Eizadi"  wrote:
> >I am running on CloudStack Master 4.3.
> >
> >I had a use case where my XenServer ran out of memory and I could not
> >create any more instances on CloudStack.
> >I shutdown the XenServer and increased the memory on XenServer and
> >brought up the Management Server again, but the Management Server still
> >sees the old values. How is this suppose to work?
> >
> >As a workaround I assume I could find the database entry for the old RAM
> >value and update with the new Memory Total.
> >
> >Here is some more detailed logs:
> >
> >The stats for the XenServer from CloudStack:
> >
> >Total CPU   2 x 2.67 GHz
> >CPU Utilized0.08%
> >CPU Allocated for VMs   0%
> >Memory Total7.03 GB
> >Memory Allocated2.50 GB
> >Memory Used 3.60 MB
> >Network Read558.23 MB
> >Network Write   23.20 MB
> >
> >
> >The log of memory problem:
> >WARN  [o.a.c.alerts] (Job-Executor-5:ctx-3b5b1c95)  alertType:: 8 //
> >dataCenterId:: 1 // podId:: null // clusterId:: null // message:: Failed
> >to deploy Vm with Id: 27, on Host wi
> >th Id: null
> >INFO  [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-5:ctx-3b5b1c95)
> >com.cloud.exception.InsufficientServerCapacityException: Unable to create
> >a deployment for VM[User|test-2]Scope=in
> >terface com.cloud.dc.DataCenter; id=1
> >INFO  [o.a.c.a.c.u.v.DeployVMCmd] (Job-Executor-5:ctx-3b5b1c95) Unable to
> >create a deployment for VM[User|test-2]
> >com.cloud.exception.InsufficientServerCapacityException: Unable to create
> >a deployment for VM[User|test-2]Scope=interface com.cloud.dc.DataCenter;
> >id=1
> >at
> >org.apache.cloudstack.engine.cloud.entity.api.VMEntityManagerImpl.reserveV
> >irtualMachine(VMEntityManagerImpl.java:210)
> >at
> >org.apache.cloudstack.engine.cloud.entity.api.VirtualMachineEntityImpl.res
> >erve(VirtualMachineEntityImpl.java:198)
> >at
> >com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:
> >3372)
> >at
> >com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:
> >2954)
> >at
> >com.cloud.vm.UserVmManagerImpl.startVirtualMachine(UserVmManagerImpl.java:
> >2940)
> >at
> >com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorD
> >ispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
> >at
> >org.apache.cloudstack.api.command.user.vm.DeployVMCmd.execute(DeployVMCmd.
> >java:421)
> >at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:161)
> >at
> >com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:97)
> >at
> >org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$1.run(AsyncJ
> >obManagerImpl.java:526)
> >at
> >java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> >at
> >java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> >at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> >at
> >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
> >1110)
> >at
> >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
> >:603)
> >at java.lang.Thread.run(Thread.java:679)
> 

[jira] [Closed] (CLOUDSTACK-3784) build_asf.sh script need to check if gpg-agent is running

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-3784.
--
Resolution: Fixed

> build_asf.sh script need to check if gpg-agent is running
> -
>
> Key: CLOUDSTACK-3784
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3784
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.1.0, 4.1.1, 4.2.0
> Environment: rhel 6.4 with ACS 4.1.1
>Reporter: ilya musayev
>Assignee: ilya musayev
>Priority: Minor
>
> build_asf.sh will go into continuous loop if gpg-agent is not running.
> add a logic to check if gpg-agent is running with --daemon 
> --use-standard-socket, make this step optional.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1497) Alien VM's are deleted on migration by xenserver.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1497.
--
Resolution: Invalid

> Alien VM's are deleted on migration by xenserver.
> -
>
> Key: CLOUDSTACK-1497
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1497
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.0.0
> Environment: Cloudstack 4.0.0 managing xenserver 6.0.2
>Reporter: Javier Ayllon
>Priority: Minor
>  Labels: cloudstack, xenserver
>
> On management server startup, several messages indicate that alien vm's are 
> recognized and ignored for vm management. 
> When trying to migrate an alien vm from one xenserver to another in the same 
> xenserver cluster, the alien vm is destroyed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-4440) CloudStack should handle native VMware HA for virtual routers

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-4440.
--
Resolution: Fixed

> CloudStack should handle native VMware HA for virtual routers
> -
>
> Key: CLOUDSTACK-4440
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4440
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc, Management Server
>Affects Versions: 4.5.0
>Reporter: Kirk Kosinski
>Assignee: Sateesh Chodapuneedi
>Priority: Minor
>  Labels: ha, networking, virtualrouter, vmware, vsphere
>
> Currently when a virtual router is rebooted by native VMware HA in vSphere, 
> it will lose its network and iptables configuration and cause connectivity 
> problems for VMs. Resolving this requires manual intervention by the 
> CloudStack administrator; the router must be rebooted, or the network 
> restarted.
> This behavior is not ideal and will prolong downtime caused by an HA event, 
> and there is no point for the non-functional virtual router to even be 
> running. CloudStack should handle this situation gracefully by reconfiguring 
> a virtual router that is successfully rebooted by VMware HA. 
> In the meantime this limitation should be documented.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1478) [DOC] Document baremetal kickstart

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1478.
--
Resolution: Fixed

> [DOC] Document baremetal kickstart
> --
>
> Key: CLOUDSTACK-1478
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1478
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.3.2
>Reporter: Jessica Tomechak
>Priority: Minor
> Fix For: Future
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-2439) "Domain" field under login page should be mandatory for the non root accounts.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-2439.

Resolution: Fixed

> "Domain" field under login page should be mandatory for the non root accounts.
> --
>
> Key: CLOUDSTACK-2439
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2439
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: manasaveloori
>Priority: Minor
> Fix For: Future
>
>
> Steps:
> Log in as admin
> create a domain under root domain.(Eg:/root/test)
> Create an account with new domain.
> Log out of admin account and log in with new account user without specifying 
> any domain.
> Expected:
> For non root accounts having domain_id other than 1 ,the domain field should 
> be made Mandatory as username and password fields.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1442) Document BigSwitch plugin

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1442.
--
Resolution: Fixed

> Document BigSwitch plugin
> -
>
> Key: CLOUDSTACK-1442
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1442
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Jessica Tomechak
>Assignee: Kanzhe Jiang
>Priority: Minor
> Fix For: Future
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-4778) cloudstack-sysvmadm gives an error on Ubuntu

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-4778.

Resolution: Fixed

> cloudstack-sysvmadm gives an error on Ubuntu
> 
>
> Key: CLOUDSTACK-4778
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4778
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Upgrade
>Affects Versions: 4.2.0
>Reporter: Kirk Kosinski
>Priority: Minor
>  Labels: ubuntu, upgrade
>
> When running the cloudstack-sysvmadm on a Ubuntu management server, the 
> following error is seen:
> /usr/bin/cloudstack-sysvmadm: line 21: /etc/rc.d/init.d/functions: No such 
> file or directory
> The script is trying to source a file (/etc/rc.d/init.d/functions) that does 
> not exist on Ubuntu 12.04. The script should be updated to work properly on a 
> Ubuntu management server.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2215) SSVM does not use allocated storage ip range

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2215.
--
Resolution: Fixed

> SSVM does not use allocated storage ip range
> 
>
> Key: CLOUDSTACK-2215
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Network Controller, Storage Controller
>Affects Versions: 4.0.1, 4.0.2, 4.1.0, 4.2.0
> Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've 
> not seen fixes for this yet.
> VMWare vSphere 5.0 with Advanced Network
>Reporter: ilya musayev
>Assignee: ilya musayev
>Priority: Minor
>  Labels: Network, SSVM
>
> Create Advanced Network Zone, assign a range of IPs to storage network, also 
> predefine public range. 
> The Secondary Storage VM gets the IPs of Public Networks and not whats its 
> been given. In my example, i've defined two public networks - with very small 
> ip range (4 on each). I noticed that SSVM took 2 IPs from Public Network A, 
> and 1 IP from Public Network B. 
> If you have stringent setup and you need to allocate IPs as designed and 
> setup firewall rules, one would expect to setup firewall rules on storage ip 
> range, thinking that SSVM is going to use the IP from that range, however, 
> instead - it uses public ip range.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1659) Create Press page for the Apache CMS site

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1659.
--
Resolution: Fixed

> Create Press page for the Apache CMS site
> -
>
> Key: CLOUDSTACK-1659
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1659
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Website
>Affects Versions: Future
>Reporter: Joe Brockmeier
>Assignee: Joe Brockmeier
>Priority: Minor
> Fix For: Future
>
>
> Create a  press page with information needed to write about Apache 
> CloudStack, find contacts, etc. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-5225) vmware os type error for redhat 6.x

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-5225.
--
Resolution: Fixed

> vmware os type error for redhat 6.x
> ---
>
> Key: CLOUDSTACK-5225
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5225
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: VMware
>Affects Versions: 4.2.0
>Reporter: Jijun
>Priority: Minor
>  Labels: vmware
>
> upload a redhat 6.x iso or template , start a vm using it. check the os type 
> in vsphere client, the vm os type is other 64 linux. the vmware-tools can not 
> be installed due to the issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2436) Message "You do not have any affinity groups. Please continue to the next step." is shown multiple time

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2436.
--
Resolution: Fixed

> Message "You do not have any affinity groups. Please continue to the next 
> step." is shown multiple time
> ---
>
> Key: CLOUDSTACK-2436
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2436
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
>Reporter: prashant kumar mishra
>Priority: Minor
> Fix For: Future
>
> Attachments: screenshot-1.jpg
>
>
> please check screenshot for better understanding.
> Steps to reproduce
> ---
> 1-Create two Adv zones
> 2-click add instance action button 
> 3-Select 1st zone , proceed till step 5(till affinity)
> 4-By clicking on action button "previous"  come back to zone selection page 
> (step one)
> 5-Select  second zone  and repeat step 2,3,4 
> 6-select alternatively zone1/Zone2  and Repeat step 2-4
> Expected
> --
> Message   "You do not have any affinity groups. Please continue to the next 
> step." should be displayed only single time
> Actual
> ---
> Message is getting displayed multiple times



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1283) UI - Tooltip - Need a clean way to differentiate between Alt Tag's and Tooltips.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1283.
--
Resolution: Fixed

> UI - Tooltip - Need a clean way to differentiate between Alt Tag's and 
> Tooltips.
> 
>
> Key: CLOUDSTACK-1283
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1283
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.1.0, 4.2.0
> Environment: RHEL 6.3 Build 15
>Reporter: Parth Jagirdar
>Priority: Minor
> Attachments: 4 (2).jpg, 4 (3).jpg
>
>
> Please refer to Comments in 
> https://issues.apache.org/jira/browse/CLOUDSTACK-176
> It may be that these are not Tooltips. (Refer to both screens attached) 
> But it is definitely within the feature scope; due to fact that a new feature 
> should not disrupt an existing one. Assuming ALT TAG's were pre existent.
> Either we should make them both work in harmony and with clear distinction. 
> Or should disable 1 features as other is doing the exact same job.
> Tagging as Minor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1285) UI -Tooltip - Lengthy and inconsistent description among toolips

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1285.
--
Resolution: Fixed

> UI -Tooltip - Lengthy and inconsistent description among toolips
> 
>
> Key: CLOUDSTACK-1285
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1285
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.1.0, 4.2.0
> Environment: RHEL 6.3 Build#15
>Reporter: Parth Jagirdar
>Priority: Minor
> Attachments: 3.jpg, 4.jpg
>
>
>  "A unique name for the template. This will be visible to users, so choose 
> something descriptive" ; I think 94 Characters are too much for a ToolTip 
> representing name. (Screen 4)
> And is also inconsistent with other tooltips for names which are more concise 
> and simple such as "A name for the Zone". (Refer to Screen 4 and compare it 
> to Screen 3)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1225) Storage System vm id keeps on increasing

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1225.
--
Resolution: Fixed

> Storage System vm id keeps on increasing 
> -
>
> Key: CLOUDSTACK-1225
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1225
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.0.1
> Environment: Cloud Stack Mgmnt server 4.0.1 :XCP Virtual Machine 
> running with CentOS release 6.2 (Final)/ 2.6.32-220.el6.x86_64
> Mysql:5.1.67,Host: XCP Host 1.4.90-53341c,Storage: both primary and secondary 
> is on management server (/export/primary and /export/secondary),ip address: 
> Every machine is having public ip in the same CIDR.
>Reporter: kevin parker
>Priority: Minor
>  Labels: 4.0.1_Candidate
>
> Its been 3 weeks since i am working on Cloud Stack 4.0.1 
> (http://jenkins.cloudstack.org/view/4.0.1/job/build-4.0.1-nonoss-rhel63/)  
> but couldn't even start system vms..In UI its showing "Creating system VMs 
> (this may take a while)" but nothing is happening and i also noticed that  
> select * from cloud.vm_instance\G;  is increasing every minute. every 
> minute-two new id is getting generated with state Expunging.
> But In UI it is still trying to create system VM but is actually failing but 
> there is no way to alert user about this.Will this ever stop?
> sample error:
>  Exception while trying to start secondary storage vm
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a 
> deployment for VM[SecondaryStorageVm|s-91-VM]Scope=interface 
> com.cloud.dc.DataCenter; id=1
> 2013-02-11 08:15:59,375 WARN  [cloud.api.ApiDispatcher] 
> (Job-Executor-8:job-8) class com.cloud.api.ServerApiException : Fail to start 
> system vm
> this is the log:http://pastebin.com/fE5uUgZt



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1287) The list table is malformed when scrolling down in the global setting page

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1287.
--
Resolution: Fixed

> The list table is malformed when scrolling down in the global setting page
> --
>
> Key: CLOUDSTACK-1287
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1287
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
> Environment: Master branch
>Reporter: Isaac Chiang
>Priority: Minor
>  Labels: ui
> Attachments: screenshot-1.jpg
>
>
> When scrolling down the list table in global setting page, the width of the 
> columns are changed after each "listConfiguration" request



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1025) If an ISO is deleted there is no check if the ISO is actually attached to a guest or not.

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1025.
--
Resolution: Fixed

> If an ISO is deleted there is no check if the ISO is actually attached to a 
> guest or not.
> -
>
> Key: CLOUDSTACK-1025
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1025
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: ISO
>Affects Versions: 4.0.0
>Reporter: Funs Kessen
>Priority: Minor
>
> It's possible to remove ISO images that are still attached to VMs, this 
> results in the hypervisor having stale NFS handles and IO errors on the non 
> existing attached ISO.
> for example:
> Jan 21 13:33:07 XX tapdisk[6360]: 
> /var/run/sr-mount/f1c9b60b-516f-9f9d-9c1c-2021505f2c51/238-7-2e48e390-9f0d-31bb-92b2-71ca50d0e349.iso:
>  __tapdisk_vbd_complete_td_request: 185 messages suppressed
> Jan 21 13:33:07 XX tapdisk[6360]: ERROR: errno -116 at 
> __tapdisk_vbd_complete_td_request: req tap-1.0: read 0x0008 secs @ 0x 
> - Stale NFS file handle
> Jan 21 13:33:07 XX last message repeated 14 times
> Jan 21 13:33:07 XX tapdisk[6360]: ERROR: errno -116 at 
> __tapdisk_vbd_complete_td_request: req tap-1.0: read 0x0008 secs @ 0x0010 
> - Stale NFS file handle
> Jan 21 13:33:07 XX tapdisk[6360]: 
> /var/run/sr-mount/f1c9b60b-516f-9f9d-9c1c-2021505f2c51/238-7-2e48e390-9f0d-31bb-92b2-71ca50d0e349.iso:
>  __tapdisk_vbd_complete_td_request: too many errors, dropped.
> Jan 21 13:33:07 XX kernel: end_request: I/O error, dev tdb, sector 0
> Jan 21 13:33:07 XX last message repeated 14 times



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1177) CloudStack always reports 'invalid username or password' when using IE10

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1177.
--
Resolution: Fixed

> CloudStack always reports 'invalid username or password' when using IE10
> 
>
> Key: CLOUDSTACK-1177
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1177
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.0.0
> Environment: Windows 8 (Enterprise) running IE10
>Reporter: Paul Angus
>Priority: Minor
>
> When using IE10 on Windows 8; CloudStack always reports 'invalid username or 
> password'.  Work-a-rounds are - use a different browser Firefox/Chrome etc or 
> change IE browser mode to IE9, IE8 or IE7.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-8918) [Install] Db Error after install - Unknown column 'iso_id1' in 'field list'

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-8918.
--
Resolution: Fixed

> [Install] Db Error after install - Unknown column 'iso_id1' in 'field list'
> ---
>
> Key: CLOUDSTACK-8918
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8918
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Install and Setup
>Affects Versions: 4.6.0
>Reporter: Raja Pullela
>Assignee: Daan Hoogland
>Priority: Trivial
> Fix For: Future
>
>
> Following error is seen in the MS logs 
> 2015-09-28 07:52:52,756 ERROR [c.c.u.d.Upgrade410to420] (main:null) 
> migrateDatafromIsoIdInVolumesTable:Exception:Unknown column 'iso_id1' in 
> 'field list'
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 
> 'iso_id1' in 'field list'
>   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>   at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>   at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
>   at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
>   at com.mysql.jdbc.Util.getInstance(Util.java:386)
>   at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052)
>   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3597)
>   at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3529)
>   at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1990)
>   at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2151)
>   at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2625)
>   at 
> com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2119)
>   at 
> com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2283)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>   at 
> org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
>   at 
> com.cloud.upgrade.dao.Upgrade410to420.migrateDatafromIsoIdInVolumesTable(Upgrade410to420.java:2378)
>   at 
> com.cloud.upgrade.dao.Upgrade410to420.performDataMigration(Upgrade410to420.java:110)
>   at 
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:345)
>   at 
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:468)
>   at 
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.checkIntegrity(CloudStackExtendedLifeCycle.java:65)
>   at 
> org.apache.cloudstack.spring.lifecycle.CloudStackExtendedLifeCycle.start(CloudStackExtendedLifeCycle.java:55)
>   at 
> org.springframework.context.support.DefaultLifecycleProcessor.doStart(DefaultLifecycleProcessor.java:167)
>   at 
> org.springframework.context.support.DefaultLifecycleProcessor.access$200(DefaultLifecycleProcessor.java:51)
>   at 
> org.springframework.context.support.DefaultLifecycleProcessor$LifecycleGroup.start(DefaultLifecycleProcessor.java:339)
>   at 
> org.springframework.context.support.DefaultLifecycleProcessor.startBeans(DefaultLifecycleProcessor.java:143)
>   at 
> org.springframework.context.support.DefaultLifecycleProcessor.onRefresh(DefaultLifecycleProcessor.java:108)
>   at 
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:947)
>   at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:482)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContext(DefaultModuleDefinitionSet.java:145)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet$2.with(DefaultModuleDefinitionSet.java:122)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:245)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:250)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.withModule(DefaultModuleDefinitionSet.java:233)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.loadContexts(DefaultModuleDefinitionSet.java:117)
>   at 
> org.apache.cloudstack.spring.module.model.impl.DefaultModuleDefinitionSet.load(DefaultModuleDefinitionSet.java:79)
>   at 

[jira] [Resolved] (CLOUDSTACK-6837) Template order changes are not permanent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-6837.

Resolution: Fixed

> Template order changes are not permanent
> 
>
> Key: CLOUDSTACK-6837
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6837
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.1.1, 4.2.1
> Environment: KVM Environment running CS 4.2.1.1
>Reporter: Nick Sindlinger
>Priority: Trivial
> Fix For: Future
>
>
> When using the Template Order buttons in the UI the changes can be seen 
> immediately. However upon leaving the template menu and returning to it you 
> will find that they have returned to the default order and that your changes 
> have not take effect. 
> I can see the API calls taking place in the management logs to reorder all 
> the templates however the changes are not permanent. 
> 2014-06-03 10:44:54,981 DEBUG [cloud.api.ApiServlet] (TP-Processor11:null) 
> ===START===  69.170.148.179 -- GET  
> command=updateTemplate=json=zuM01Ft9Okr5oCJmcs4%2FVQMKXgo%3D=a7668b03-d998-46d2-9044-d9c9f54dd03e=14&_=1401810294947
> 2014-06-03 10:44:55,001 DEBUG [cloud.api.ApiServlet] (TP-Processor5:null) 
> ===END===  69.170.148.179 -- GET  
> command=updateTemplate=json=zuM01Ft9Okr5oCJmcs4%2FVQMKXgo%3D=fd635fc6-599c-41a3-ae88-b4fb9d4d9f0d=19&_=1401810294940



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (CLOUDSTACK-8873) listLoadBalancerRules response JSON publicport/privateport not an int, zonename missing

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner reopened CLOUDSTACK-8873:


> listLoadBalancerRules response JSON publicport/privateport not an int, 
> zonename missing
> ---
>
> Key: CLOUDSTACK-8873
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8873
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: René Moser
>Priority: Trivial
> Fix For: Future
>
>
> h2. actual
> {code:none}
> {
>   "count": 1, 
>   "loadbalancerrule": [
> {
>   "account": "foo", 
>   "algorithm": "source", 
>   "cidrlist": "", 
>   "domain": "STXT", 
>   "domainid": "3a291b29-b184-4ddc-bdcc-8298c237942e", 
>   "id": "22bf1066-8bc3-425d-a213-a49431f7b865", 
>   "name": "foo", 
>   "networkid": "48df88b1-c2e2-432d-811a-681a2be74dde", 
>   "privateport": "80", 
>   "publicip": "1.2.4.5", 
>   "publicipid": "5d94a86d-0ee9-429a-9a5b-f57da4ee60cb", 
>   "publicport": "80", 
>   "state": "Add", 
>   "tags": [], 
>   "zoneid": "9e683e49-f4db-4b44-82ad-708689e9c4c8"
> }
>   ]
> }
> {code}
> h2. expected
> {code:none}
> {
>   "count": 1, 
>   "loadbalancerrule": [
> {
>   "account": "foo", 
>   "algorithm": "source", 
>   "cidrlist": "", 
>   "domain": "STXT", 
>   "domainid": "3a291b29-b184-4ddc-bdcc-8298c237942e", 
>   "id": "22bf1066-8bc3-425d-a213-a49431f7b865", 
>   "name": "foo", 
>   "networkid": "48df88b1-c2e2-432d-811a-681a2be74dde", 
>   "privateport": 80, 
>   "publicip": "1.2.4.5", 
>   "publicipid": "5d94a86d-0ee9-429a-9a5b-f57da4ee60cb", 
>   "publicport": 80, 
>   "state": "Add", 
>   "tags": [], 
>   "zoneid": "9e683e49-f4db-4b44-82ad-708689e9c4c8"
>   "zonename": "myzone"
> }
>   ]
> }
> {code}
> *Note: also check the response for createLoadBalancerRule when fixing this!*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-8873) listLoadBalancerRules response JSON publicport/privateport not an int, zonename missing

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-8873.

Resolution: Fixed

> listLoadBalancerRules response JSON publicport/privateport not an int, 
> zonename missing
> ---
>
> Key: CLOUDSTACK-8873
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8873
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: René Moser
>Priority: Trivial
> Fix For: Future
>
>
> h2. actual
> {code:none}
> {
>   "count": 1, 
>   "loadbalancerrule": [
> {
>   "account": "foo", 
>   "algorithm": "source", 
>   "cidrlist": "", 
>   "domain": "STXT", 
>   "domainid": "3a291b29-b184-4ddc-bdcc-8298c237942e", 
>   "id": "22bf1066-8bc3-425d-a213-a49431f7b865", 
>   "name": "foo", 
>   "networkid": "48df88b1-c2e2-432d-811a-681a2be74dde", 
>   "privateport": "80", 
>   "publicip": "1.2.4.5", 
>   "publicipid": "5d94a86d-0ee9-429a-9a5b-f57da4ee60cb", 
>   "publicport": "80", 
>   "state": "Add", 
>   "tags": [], 
>   "zoneid": "9e683e49-f4db-4b44-82ad-708689e9c4c8"
> }
>   ]
> }
> {code}
> h2. expected
> {code:none}
> {
>   "count": 1, 
>   "loadbalancerrule": [
> {
>   "account": "foo", 
>   "algorithm": "source", 
>   "cidrlist": "", 
>   "domain": "STXT", 
>   "domainid": "3a291b29-b184-4ddc-bdcc-8298c237942e", 
>   "id": "22bf1066-8bc3-425d-a213-a49431f7b865", 
>   "name": "foo", 
>   "networkid": "48df88b1-c2e2-432d-811a-681a2be74dde", 
>   "privateport": 80, 
>   "publicip": "1.2.4.5", 
>   "publicipid": "5d94a86d-0ee9-429a-9a5b-f57da4ee60cb", 
>   "publicport": 80, 
>   "state": "Add", 
>   "tags": [], 
>   "zoneid": "9e683e49-f4db-4b44-82ad-708689e9c4c8"
>   "zonename": "myzone"
> }
>   ]
> }
> {code}
> *Note: also check the response for createLoadBalancerRule when fixing this!*



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-6009) cloudstack presenting wrong used memory values

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-6009.

Resolution: Fixed

> cloudstack presenting wrong used memory values
> --
>
> Key: CLOUDSTACK-6009
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6009
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Rafael Weingärtner
>Priority: Minor
>
> Hi folks, I have sent an e-mail about this issue. And I was hoping to discuss 
> it before I opened a jira ticket. However, no one seemed to care about it.
> So, here is the problem:
> There is a wrong value being presented on infrastructure > Hosts.
> The data used to present on statistics tab is got from "listHosts" API method:
> http://cloudstack.apache.org/docs/api/apidocs-4.2/root_admin/listHosts.html
> “listHosts” is the method which returns those values about the host (mem, cpu 
> and etc).
>  It returns these values about the host’s memory: 
> memoryallocated   the amount of the host's memory currently allocated
> memorytotal   the memory total of the host
> memoryusedthe amount of the host's memory currently used
> The API Doc does not say the metric used on those values. But, I took a look 
> at the CS source code. And it turned out that the first two values are given 
> in bytes, while the third one is given in KB and that is why that value looks 
> so small when presented on statistics tab. It is not being converted in a 
> proper way on the UI.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-4847) UI Error "Failed to delete storage pool on host"

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-4847.

Resolution: Fixed

> UI Error "Failed to delete storage pool on host"
> 
>
> Key: CLOUDSTACK-4847
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4847
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.2.0
> Environment: [root@csman2-1 ~]# rpm -qa|grep cloudstack
> cloudstack-management-4.2.0-1.el6.x86_64
> cloudstack-common-4.2.0-1.el6.x86_64
> cloudstack-awsapi-4.2.0-1.el6.x86_64
> cloudstack-cli-4.2.0-1.el6.x86_64
> cloudstack-usage-4.2.0-1.el6.x86_64
> [root@csman2-1 ~]# 
> [root@csman2-1 ~]# lsb
> lsblklsb_release  
> [root@csman2-1 ~]# lsb_release -a
> LSB Version:  :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
> Distributor ID:   CentOS
> Description:  CentOS release 6.4 (Final)
> Release:  6.4
> Codename: Final
>Reporter: Shanker Balan
>Priority: Minor
>
> Hi,
> In CloudStack 4.2, If adding a primary storage fails from the 'Infrastructure 
> -> Primary Storage -> Add Primary Storage' tab, the UI reports as "Failed to 
> delete storage pool on host".
> The error message should be "Failed to add storage pool on host".
> See screenshots:
> http://imgur.com/s1g7FBW (Add Primary Storage Screen)
> http://imgur.com/MYH1IyB (Error on addition)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-5219) Cannot create a template from an existing Snapshot (Simulator)

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-5219.

Resolution: Fixed

> Cannot create a template from an existing Snapshot (Simulator)
> --
>
> Key: CLOUDSTACK-5219
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5219
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.2.0
>Reporter: David Grizzanti
>Assignee: Meghna Kale
>Priority: Minor
> Attachments: VmSnapshot.jpg, volumeSnapshotSuccess.jpg, 
> volumeTemplatesFromSnapshot.jpg
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-917) QA - review Document vSphere / ESXi patch installation procedure

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-917.
-
Resolution: Fixed

This seems to be already fixed. In any case we can reopen it.

> QA - review Document vSphere / ESXi patch installation procedure
> 
>
> Key: CLOUDSTACK-917
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-917
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Test
>Affects Versions: 4.1.0
>Reporter: Sudha Ponnaganti
>Priority: Minor
> Fix For: Future
>
>
> - review docs for this procedure 
> - Need to perform the procedure as well



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-1460) UI : List Storage table has unused column name Actions

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-1460.

Resolution: Fixed

> UI : List Storage table has unused column name Actions
> --
>
> Key: CLOUDSTACK-1460
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1460
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.1.0, 4.2.0
> Environment: RHEL 6.3
>Reporter: Parth Jagirdar
>Priority: Minor
> Attachments: storage column.jpg
>
>
> Either Actions column should be removed from the table Or should actually be 
> populated by some actions.
> A Blank column shouldn't exists.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-2075) List capacity error causes UI to display status overlay

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-2075.

Resolution: Fixed

> List capacity error causes UI to display status overlay
> ---
>
> Key: CLOUDSTACK-2075
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2075
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.0.0
> Environment: CentOS 6.3
> XenServer
>Reporter: Diogo Monteiro
>Priority: Minor
>
> Every time an action is performed on the UI a overlay pops up with the title 
> "Status" and nothing else.
> Looking at the network activity this call seems to be causing the issue: 
> api?command=listCapacity=json
> Here is a ss of the bug: 
> http://diogogmt.files.wordpress.com/2013/04/cloudstack-ui-status-error.png



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-8817) listFirewallRules response JSON startport/endport not an int

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-8817.

Resolution: Fixed

> listFirewallRules response JSON startport/endport not an int
> 
>
> Key: CLOUDSTACK-8817
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8817
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.6.0
>Reporter: René Moser
>Priority: Trivial
>
> h2. Summary
> listFirewallRules returns endpoint and startpoint values as String.
> h2. Excpected results
> {code}
> {
>   "count": 1 
>   "firewallrule": [
> {
>   "cidrlist": "0.0.0.0/0", 
>   "endport": 22, 
>   "fordisplay": true, 
>   "id": "126dccd4-ed9a-42a5-bd25-204aab8c8f03", 
>   "ipaddress": "10.101.0.21", 
>   "ipaddressid": "c70e7a84-4fa2-40a0-a70d-f64101663f21", 
>   "networkid": "b0c50de4-015e-4b28-a12a-8955698ebc2a", 
>   "protocol": "tcp", 
>   "startport": 22, 
>   "state": "Active", 
>   "tags": []
> }
>   ]
> }
> {code}
> h2. Actuall results
> {code}
> {
>   "count": 1 
>   "firewallrule": [
> {
>   "cidrlist": "0.0.0.0/0", 
>   "endport": "22", 
>   "fordisplay": true, 
>   "id": "126dccd4-ed9a-42a5-bd25-204aab8c8f03", 
>   "ipaddress": "10.101.0.21", 
>   "ipaddressid": "c70e7a84-4fa2-40a0-a70d-f64101663f21", 
>   "networkid": "b0c50de4-015e-4b28-a12a-8955698ebc2a", 
>   "protocol": "tcp", 
>   "startport": "22", 
>   "state": "Active", 
>   "tags": []
> }
>   ]
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-8781) Superfluous field during VPC creation

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-8781.

Resolution: Fixed

> Superfluous field during VPC creation
> -
>
> Key: CLOUDSTACK-8781
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8781
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Affects Versions: 4.6.0
>Reporter: Nick Livens
>Assignee: Nick Livens
>Priority: Trivial
> Fix For: Future
>
> Attachments: addVpc.png
>
>
> When creating a VPC, there is a superfluous field "Public Load Balancer 
> Provider" which is being ignored since the LB Provider is specified in the 
> VPC offering. This might confuse the users whether they can use a different 
> LB provider than the one specified in the VPC offering.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-8202) Templates /IOS items order list is not persistent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-8202.

Resolution: Fixed

> Templates /IOS  items order list is not persistent
> --
>
> Key: CLOUDSTACK-8202
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8202
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: ISO, Template
>Affects Versions: 4.4.2
> Environment: CS 4.4.2 on CentOS release 6.6 (Final)
>Reporter: Adam Kamali
>Priority: Trivial
>  Labels: Template
>
> When trying to list the templates or ISO images in certain order (let us say 
> alphabetical or based on OS type) the item list will not be retained after 
> log off.
> Service offering on the other hand (order list works fine) so it's only 
> Templates / ISO view that is affected.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-1069) Document workaround for: CS and LDAP user validation can't happen simultaneously

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-1069.

Resolution: Fixed

> Document workaround for: CS and LDAP user validation can't happen 
> simultaneously
> 
>
> Key: CLOUDSTACK-1069
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1069
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Affects Versions: 4.0.0
>Reporter: Jessica Tomechak
>Assignee: Hugo Trippaers
>Priority: Minor
>
> Add the following to the section on LDAP Authentication in the Admin Guide:
> LDAP User Authentication
> Limitation
> CloudStack and LDAP user authentication can't happen simultaneously because 
> the CloudStack user password is MD5 hashed and the LDAP server expects the 
> password in plain text. To workaround: 
> 1. Disable password hashing:
> a. Open the sharedFunctions.js file located at 
> /usr/share/cloud/management/webapps/client/
> scripts.
> b. Set the following variables to false:
> var md5HashedLogin = false;
> 2. Open /etc/cloud/management/components.xml file.
> 3. Change the following:
> 
> to
> 
> 4. Restart the Cloud Management service.
> service cloud-management restart
> Now, the users can successfully log in by using either the LDAP credentials 
> or the CloudStack credentials.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-2532) remove bogus self assign to parent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-2532.

Resolution: Fixed

> remove bogus self assign to parent
> --
>
> Key: CLOUDSTACK-2532
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2532
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.0.2
>Reporter: Dave Brosius
>Priority: Trivial
> Attachments: 2532.txt
>
>
> code assigns
> this.parent = parent;
> even tho there isn't any non-field parent in the constructor...
> removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-9065) Packaging RPM: Add option for package release version, cleanup and lint

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-9065.

Resolution: Fixed

> Packaging RPM: Add option for package release version, cleanup and lint
> ---
>
> Key: CLOUDSTACK-9065
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9065
> Project: CloudStack
>  Issue Type: Improvement
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Packaging
>Affects Versions: 4.6.0
>Reporter: David Amorim Faria
>Assignee: David Amorim Faria
>Priority: Trivial
>
> In RPM Packaging, add option for package release version.
> Also, code cleanup and some linting.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-7161) API: The response of an "updateNetworkACLItem" command returns a "createnetworkaclresponse"

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-7161.

Resolution: Fixed

> API: The response of an "updateNetworkACLItem" command returns a 
> "createnetworkaclresponse"
> ---
>
> Key: CLOUDSTACK-7161
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7161
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Patrick D.
>Priority: Trivial
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (CLOUDSTACK-6735) Clicking on instances when viewing an instance should not return you to the dashboard

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner reopened CLOUDSTACK-6735:


> Clicking on instances when viewing an instance should not return you to the 
> dashboard
> -
>
> Key: CLOUDSTACK-6735
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6735
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Website
>Affects Versions: 4.3.0
> Environment: OS: Mac OS X
> Browser: Chrome 34.0.x
>Reporter: Bret Mette
>Priority: Trivial
>  Labels: html
> Attachments: 2014-05-20_2332.png
>
>
> Clicking on "instances" in the bread crumbs when viewing an instance returns 
> you do the dashboard.
> Current behavior: Dashboard is displayed.
> Expected behavior: Instances list is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (CLOUDSTACK-6735) Clicking on instances when viewing an instance should not return you to the dashboard

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner resolved CLOUDSTACK-6735.

Resolution: Fixed

> Clicking on instances when viewing an instance should not return you to the 
> dashboard
> -
>
> Key: CLOUDSTACK-6735
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6735
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Website
>Affects Versions: 4.3.0
> Environment: OS: Mac OS X
> Browser: Chrome 34.0.x
>Reporter: Bret Mette
>Priority: Trivial
>  Labels: html
> Attachments: 2014-05-20_2332.png
>
>
> Clicking on "instances" in the bread crumbs when viewing an instance returns 
> you do the dashboard.
> Current behavior: Dashboard is displayed.
> Expected behavior: Instances list is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (CLOUDSTACK-2532) remove bogus self assign to parent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner reopened CLOUDSTACK-2532:

  Assignee: (was: Dave Brosius)

> remove bogus self assign to parent
> --
>
> Key: CLOUDSTACK-2532
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2532
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.0.2
>Reporter: Dave Brosius
>Priority: Trivial
> Attachments: 2532.txt
>
>
> code assigns
> this.parent = parent;
> even tho there isn't any non-field parent in the constructor...
> removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2225) Automation - Add Automation for QuickView and Table widgent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2225.
--
Resolution: Unresolved

Issue closed for the lack of information regarding its necessity and 
implementation.

> Automation - Add Automation for QuickView and Table widgent
> ---
>
> Key: CLOUDSTACK-2225
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2225
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: UI
>Reporter: Sudha Ponnaganti
>Priority: Trivial
> Fix For: Future
>
>
> Add automation for this feature 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-6735) Clicking on instances when viewing an instance should not return you to the dashboard

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-6735.
--
Resolution: Fixed

> Clicking on instances when viewing an instance should not return you to the 
> dashboard
> -
>
> Key: CLOUDSTACK-6735
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6735
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server, Website
>Affects Versions: 4.3.0
> Environment: OS: Mac OS X
> Browser: Chrome 34.0.x
>Reporter: Bret Mette
>Priority: Trivial
>  Labels: html
> Attachments: 2014-05-20_2332.png
>
>
> Clicking on "instances" in the bread crumbs when viewing an instance returns 
> you do the dashboard.
> Current behavior: Dashboard is displayed.
> Expected behavior: Instances list is displayed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2532) remove bogus self assign to parent

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2532.
--
Resolution: Fixed

Solved

> remove bogus self assign to parent
> --
>
> Key: CLOUDSTACK-2532
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2532
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: API
>Affects Versions: 4.0.2
>Reporter: Dave Brosius
>Assignee: Dave Brosius
>Priority: Trivial
> Attachments: 2532.txt
>
>
> code assigns
> this.parent = parent;
> even tho there isn't any non-field parent in the constructor...
> removed.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-5793) [Automation]: Moving all Services Classes in existing tests to config

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-5793.
--
Resolution: Fixed

Seems to have already been done

> [Automation]: Moving all Services Classes in existing tests to config
> -
>
> Key: CLOUDSTACK-5793
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5793
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Automation, marvin
>Reporter: Santhosh Kumar Edukulla
>Assignee: Girish Shilamkar
>Priority: Minor
>
> Logging this bug to track moving Service\data class from existing tests to 
> config.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1576) Viewing of the primary storage failed on MS

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1576.
--
Resolution: Invalid

Issue closed for the lack of information regarding its necessity and 
implementation.

> Viewing of the primary storage failed on MS 
> 
>
> Key: CLOUDSTACK-1576
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1576
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Management Server
>Reporter: Fang Wang
>Priority: Minor
>
> with Master branch,  on MS UI, there is primary storage deployed. When 
> clicking to view details, failure window popped up and nothing shows. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-2705) [meta-data] Fetching meta-data using the URL http://10.1.1.1/latest/meta-data/<> doesn't work

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-2705.
--
Resolution: Cannot Reproduce

Issue closed for the lack of information regarding its necessity and 
implementation.

> [meta-data] Fetching meta-data using the URL 
> http://10.1.1.1/latest/meta-data/<> doesn't work
> -
>
> Key: CLOUDSTACK-2705
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2705
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
> Environment: commit # 80a3c0535e0a8ad3edba3713a61d063a176191d8
>Reporter: venkata swamybabu budumuru
>Priority: Minor
>
> Steps to reproduce :
> - As per the 4.0.2 admin guide 
> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.2/html/Admin_Guide/user-data-and-meta-data.html,
> User should be able access meta-data using the link 
> http://10.1.1.1/latest/meta-data/ but, it didnt work. The only link 
> that works here is : http://10.1.1.1/latest/{metadata type}
> Either we need update our docs or we need to make the above link accessible 
> to fetch the meta-data.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1441) Document ApiDiscoverService

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1441.
--
Resolution: Fixed

It has already been documented

> Document ApiDiscoverService
> ---
>
> Key: CLOUDSTACK-1441
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1441
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Doc
>Reporter: Jessica Tomechak
>Priority: Minor
>  Labels: api
> Fix For: Future
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (CLOUDSTACK-1259) NPE at service shutdown

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-1259.
--
Resolution: Invalid

Issue closed for the lack of information regarding its necessity and 
implementation.

> NPE at service shutdown
> ---
>
> Key: CLOUDSTACK-1259
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1259
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Prasanna Santhanam
>Priority: Minor
>
> During shutdown of mgmt service the following NPE is observed:
> 2013-02-13 15:53:33,128 ERROR [async.dao.SyncQueueItemDaoImpl] 
> (AsyncJobMgr-Heartbeat-1:null) Unexpected excetpion, 
> java.lang.NullPointerException
> at 
> org.apache.log4j.helpers.PatternConverter.spacePad(PatternConverter.java:107)
> at 
> org.apache.log4j.helpers.PatternConverter.format(PatternConverter.java:80)
> at org.apache.log4j.PatternLayout.format(PatternLayout.java:506)
> at org.apache.log4j.net.SyslogAppender.append(SyslogAppender.java:320)
> at 
> org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251)
> at 
> org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66)
> at org.apache.log4j.Category.callAppenders(Category.java:206)
> at org.apache.log4j.Category.forcedLog(Category.java:391)
> at org.apache.log4j.Category.warn(Category.java:1043)
> at com.cloud.utils.db.Transaction.getConnection(Transaction.java:552)
> at 
> com.cloud.utils.db.Transaction.prepareStatement(Transaction.java:461)
> at 
> com.cloud.utils.db.Transaction.prepareAutoCloseStatement(Transaction.java:454)
> at 
> com.cloud.async.dao.SyncQueueItemDaoImpl.getNextQueueItems(SyncQueueItemDaoImpl.java:95)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37)
> at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:610)
> at 
> org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:65)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:90)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:622)
> at 
> com.cloud.async.SyncQueueManagerImpl.dequeueFromAny(SyncQueueManagerImpl.java:141)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> com.cloud.async.SyncQueueManagerImpl.dequeueFromAny(SyncQueueManagerImpl.java:141)
> at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at 
> org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:689)
> at 
> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
> at 
> org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:80)
> at 
> com.cloud.utils.db.TransactionContextBuilder.AroundAnyMethod(TransactionContextBuilder.java:37)
> at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at 
> org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:621)
> at 
> 

[jira] [Closed] (CLOUDSTACK-947) QA - Ability to manage advanced and baic zones in single instance of CS

[JIRA]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Rafael Weingärtner closed CLOUDSTACK-947.
-
Resolution: Fixed

This has already been fixed from what I understand.

> QA - Ability to manage advanced and baic zones in single instance of CS 
> 
>
> Key: CLOUDSTACK-947
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-947
> Project: CloudStack
>  Issue Type: Sub-task
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Affects Versions: 4.1.0
>Reporter: Sudha Ponnaganti
>Priority: Minor
> Fix For: Future
>
>
> core tasks that need to be done:
> - review requirements/FS
> - upload test plan/test cases
> - get test cases reviewed
> - add automation
> - upload test results
> - review documentation



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9603) 'concurrent.snapshots.threshold.perhost' parameter should not accept String

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894377#comment-15894377
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9603:


Github user sateesh-chodapuneedi commented on the issue:

https://github.com/apache/cloudstack/pull/1776
  
@borisstoyanov Can you please trigger tests for this PR? Tests could be 
over any hypervisor/simulator as the fix is pretty generic.


> 'concurrent.snapshots.threshold.perhost' parameter should not accept String
> ---
>
> Key: CLOUDSTACK-9603
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9603
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Priyank Parihar
>Assignee: Priyank Parihar
>Priority: Minor
>
> concurrent.snapshots.threshold.perhost this setting at global and cluster 
> level should accept only integer values. It is accepting string values as 
> well which should be rejected.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-8910) The reserved_capacity field increases suddenly after a vmware host failure

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894359#comment-15894359
 ] 

ASF GitHub Bot commented on CLOUDSTACK-8910:


Github user SudharmaJain commented on the issue:

https://github.com/apache/cloudstack/pull/892
  
@alexandrelimassantana As suggested I have moved the code snippet to a 
method and also added unit tests. 


> The reserved_capacity field increases suddenly after a vmware host failure
> --
>
> Key: CLOUDSTACK-8910
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8910
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: sudharma jain
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9704) Remove dependency on VmwareContext object to fetch system VM key file

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894319#comment-15894319
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9704:


Github user sateesh-chodapuneedi commented on the issue:

https://github.com/apache/cloudstack/pull/1862
  
Thanks @borisstoyanov 

The 3 test failures listed in results doesn't seem related to the code 
changes in PR. 

```
2017-03-02 17:45:11,699 - CRITICAL - EXCEPTION: 
test_02_list_snapshots_with_removed_data_store: ['Traceback (most recent call 
last):\n', '  File "/usr/lib64/python2.7/unittest/case.py", line 369, in run\n  
  testMethod()\n', '  File 
"/usr/lib/python2.7/site-packages/marvin/lib/decoratorGenerators.py", line 30, 
in test_wrapper\nreturn test(self, *args, **kwargs)\n', '  File 
"/marvin/tests/smoke/test_snapshots.py", line 363, in 
test_02_list_snapshots_with_removed_data_store\nid=snapshot.id\n', '  File 
"/usr/lib/python2.7/site-packages/marvin/lib/base.py", line 1125, in list\n
return(apiclient.listSnapshots(cmd))\n', '  File 
"/usr/lib/python2.7/site-packages/marvin/cloudstackAPI/cloudstackAPIClient.py", 
line 1161, in listSnapshots\nresponse = 
self.connection.marvinRequest(command, response_type=response, 
method=method)\n', '  File 
"/usr/lib/python2.7/site-packages/marvin/cloudstackConnection.py", line 379, in 
marvinRequest\nraise e\n', 'CloudstackAPIException: Execute cmd: 
listsnapshots failed, due to: errorCode: 530, errorText:Unable to locate 
datastore with id 5\n']

2017-03-02 17:45:16,772 - CRITICAL - EXCEPTION: 
test_02_list_snapshots_with_removed_data_store: ['Traceback (most recent call 
last):\n', '  File "/usr/lib64/python2.7/unittest/case.py", line 398, in run\n  
  self.tearDown()\n', '  File "/marvin/tests/smoke/test_snapshots.py", line 
174, in tearDown\nraise Exception("Warning: Exception during cleanup : %s" 
% e)\n', "Exception: Warning: Exception during cleanup : Job failed: 
{jobprocstatus : 0, created : u'2017-03-02T17:45:13+', jobresult : 
{errorcode : 431, errortext : u'Unable to find a virtual machine with specified 
vmId'}, cmd : 
u'org.apache.cloudstack.api.command.admin.vm.DestroyVMCmdByAdmin', userid : 
u'87233b2e-ff35-11e6-be08-06674c01070f', jobstatus : 2, jobid : 
u'43f0ee45-e763-45bc-b777-795c7eaeb26a', jobresultcode : 530, jobinstanceid : 
u'3be27ffe-1884-493b-9566-e616cf2d85d0', jobresulttype : u'object', 
jobinstancetype : u'VirtualMachine', accountid : 
u'872334ae-ff35-11e6-be08-06674c01070f'}\n"]

2017-03-02 17:45:41,985 - CRITICAL - EXCEPTION: 
test_02_list_snapshots_with_removed_data_store: ['Traceback (most recent call 
last):\n', '  File "/usr/lib/python2.7/site-packages/nose/suite.py", line 228, 
in run\nself.tearDown()\n', '  File 
"/usr/lib/python2.7/site-packages/nose/suite.py", line 351, in tearDown\n
self.teardownContext(ancestor)\n', '  File 
"/usr/lib/python2.7/site-packages/nose/suite.py", line 367, in 
teardownContext\ntry_run(context, names)\n', '  File 
"/usr/lib/python2.7/site-packages/nose/util.py", line 471, in try_run\n
return func()\n', '  File "/marvin/tests/smoke/test_snapshots.py", line 160, in 
tearDownClass\nraise Exception("Warning: Exception during cleanup : %s" % 
e)\n', "Exception: Warning: Exception during cleanup : Job failed: 
{jobprocstatus : 0, created : u'2017-03-02T17:45:39+', jobresult : 
{errorcode : 530, errortext : u'Failed to delete template'}, cmd : 
u'org.apache.cloudstack.api.command.user.template.DeleteTemplateCmd', userid : 
u'87233b2e-ff35-11e6-be08-06674c01070f', jobstatus : 2, jobid : 
u'df91fb7f-b9fd-4b9f-8d07-654821c42d69', jobresultcode : 530, jobinstanceid : 
u'5fc32822-46b8-43e9-ac33-8ad5bb00e775', jobresulttype : u'object', 
jobinstancetype : u'Template', accountid : 
u'872334ae-ff35-11e6-be08-06674c01070f'}\n"]

```


> Remove dependency on VmwareContext object to fetch system VM key file
> -
>
> Key: CLOUDSTACK-9704
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9704
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Sateesh Chodapuneedi
>Assignee: Sateesh Chodapuneedi
>
> While remote executing commands/scripts in VR, ACS uses system vm keyfile. 
> ACS is fetching this key file using following code
> {code:java}
> VmwareManager mgr = 
> getServiceContext().getStockObject(VmwareManager.CONTEXT_STOCK_NAME);
> File systemVmKeyFile = mgr.getSystemVMKeyFile();
> {code}
> This is inefficient because dependency on getServiceContext() in above code 
> means a vCenter connection handle which is not required just to fetch a file 
> in name space in management server.



--
This message was sent by 

[jira] [Commented] (CLOUDSTACK-9716) baremetal:rvr:vm deployment gets stuck in starting state (waiting for notification)

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894226#comment-15894226
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9716:


Github user SudharmaJain commented on the issue:

https://github.com/apache/cloudstack/pull/1877
  
@rashmidixit Could you add a marvin test case? It looks with your changes, 
master VR Redundant state will be stuck in unknown state. 


> baremetal:rvr:vm deployment gets stuck in starting state (waiting for 
> notification)
> ---
>
> Key: CLOUDSTACK-9716
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9716
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: Baremetal
>Affects Versions: 4.5.0, 4.6.0, 4.7.0, 4.8.0, 4.9.0
>Reporter: Rashmi Dixit
>Assignee: Rashmi Dixit
>Priority: Critical
> Fix For: 4.9.1.0
>
>
> In normal network, vm deployment is successful (got notification properly). 
> When we change existing the network offering to rvr for the baremetal network 
> then vm deployment gets stuck in starting state(it has created 2 router and 
> oxe booted properly but still waiting for notification)
> 1.create baremetal network
> 2.deploy a vm with above network.
> 3.destroy the vm
> 4.create another network offering based on RVR+barmetal
> 5.change network offering from normal to rvr barmetal 
> 6. deploy a vm
> actual results:
> vm deployement stuck in starting state(it has created 2 router both master 
> and backup and vm got pxe booted properly but CS still waiting for 
> notification due to that vm state still showing in starting state)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894215#comment-15894215
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9814:


Github user yvsubhash commented on a diff in the pull request:

https://github.com/apache/cloudstack/pull/1987#discussion_r104140435
  
--- Diff: server/src/org/apache/cloudstack/region/RegionManagerImpl.java ---
@@ -229,7 +232,7 @@ public boolean deleteUser(DeleteUserCmd cmd) {
  */
 @Override
 public Domain updateDomain(UpdateDomainCmd cmd) {
-return _domainMgr.updateDomain(cmd);
+return _managementService.updateDomain(cmd);
--- End diff --

Instead of changing the method that is getting called, the missing one in 
search query can be added here and it seems the updateDomain method in 
managementserviceimpl is not in use. It can be removed


> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : Sample
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894180#comment-15894180
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9814:


GitHub user niteshsarda opened a pull request:

https://github.com/apache/cloudstack/pull/1987

CLOUDSTACK-9814 : Unable to edit a Sub domain, which has the same name in 
different domains

ISSUE

Unable to edit a Sub domain, which has the same name in different domains.

TROUBLESHOOTING
==
1. Created two sub-domains with same name. Under two different domains.
ROOT
Domain 1 : Sample
AA01
BB01

Domain 2 : Test
AA01

2. Try to edit resource - Click on edit - edit any parameter.

EXPECTED BEHAVIOR
==
It should allow to edit the required parameter and update the value.

ACTUAL BEHAVIOR
==
It throws an error "Failed to update specified domain id with name 
'AA01' since it already exists in system. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack SubDomainIssue

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1987.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 #1987


commit 2d29b4fc48081efe683457c7f4597c643f3fa480
Author: Nitesh Sarda 
Date:   2017-03-03T11:24:48Z

CLOUDSTACK-9814 : Unable to edit a Sub domain, which has the same name in 
different domains




> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : Sample
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894174#comment-15894174
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9814:


Github user niteshsarda closed the pull request at:

https://github.com/apache/cloudstack/pull/1986


> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : Sample
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894147#comment-15894147
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9814:


GitHub user niteshsarda opened a pull request:

https://github.com/apache/cloudstack/pull/1986

CLOUDSTACK-9814 : Unable to edit a Sub domain, which has the same name in 
different domains

ISSUE

Unable to edit a Sub domain, which has the same name in different domains.

TROUBLESHOOTING
==
1. Created two sub-domains with same name. Under two different domains.
ROOT
Domain 1 : India@b582a4cb-031e-49e7-afcf-4281fbf231b4
AA01
BB01

Domain 2 : Test
AA01

2. Try to edit resource - Click on edit - edit any parameter.

EXPECTED BEHAVIOR
==
It should allow to edit the required parameter and update the value.

ACTUAL BEHAVIOR
==
It throws an error "Failed to update specified domain id with name 
'AA01' since it already exists in system. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack CS-50514

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1986.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 #1986


commit 2f75b51f42c9400a7be172e405a4ff13bf4c2722
Author: Nitesh Sarda 
Date:   2017-02-27T17:54:20Z

CLOUDSTACK-9779 : Releasing secondary guest IP fails with error VM nic Ip 
x.x.x.x is mapped to load balancing rule

commit ff97817b907c25aff8ccf9bfd36a1d12966b6d9e
Author: Nitesh Sarda 
Date:   2017-03-03T10:47:58Z

CLOUDSTACK-9814 : Unable to edit a Sub domain, which has the same name in 
different domains




> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : India@b582a4cb-031e-49e7-afcf-4281fbf231b4
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9812) Update "updatePortForwardingRule" pi to include additional parameter to update the end port in case of port range

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894143#comment-15894143
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9812:


Github user mrunalinikankariya closed the pull request at:

https://github.com/apache/cloudstack/pull/1984


> Update "updatePortForwardingRule" pi to include additional parameter to 
> update the end port in case of port range
> -
>
> Key: CLOUDSTACK-9812
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9812
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: mrunalini
>
> - Configure a PF rule Private port : Start port ; 20 ENd POrt 25 || Public 
> Port : Start port 20 ; ENd Port : 25.
> - Trigger UpdatePortForwardingRule api
> - ApI fails with following error : " Unable to update the private port of 
> port forwarding rule as the rule has port range "
> Expected behaviour -
> Port range should get modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[Nitesh Sarda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitesh Sarda updated CLOUDSTACK-9814:
-
Description: 
ISSUE

Unable to edit a Sub domain, which has the same name in different domains.

TROUBLESHOOTING
==
1. Created two sub-domains with same name. Under two different domains.
ROOT
Domain 1 : Sample
AA01
BB01

Domain 2 : Test
AA01

2. Try to edit resource - Click on edit - edit any parameter.

EXPECTED BEHAVIOR
==
It should allow to edit the required parameter and update the value.

ACTUAL BEHAVIOR
==
It throws an error "Failed to update specified domain id with name 'AA01' 
since it already exists in system. 

  was:
ISSUE

Unable to edit a Sub domain, which has the same name in different domains.

TROUBLESHOOTING
==
1. Created two sub-domains with same name. Under two different domains.
ROOT
Domain 1 : India@b582a4cb-031e-49e7-afcf-4281fbf231b4
AA01
BB01

Domain 2 : Test
AA01

2. Try to edit resource - Click on edit - edit any parameter.

EXPECTED BEHAVIOR
==
It should allow to edit the required parameter and update the value.

ACTUAL BEHAVIOR
==
It throws an error "Failed to update specified domain id with name 'AA01' 
since it already exists in system. 


> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : Sample
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9812) Update "updatePortForwardingRule" pi to include additional parameter to update the end port in case of port range

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894144#comment-15894144
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9812:


Github user mrunalinikankariya commented on the issue:

https://github.com/apache/cloudstack/pull/1984
  
Can see two cmmits in same card. so 


> Update "updatePortForwardingRule" pi to include additional parameter to 
> update the end port in case of port range
> -
>
> Key: CLOUDSTACK-9812
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9812
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: mrunalini
>
> - Configure a PF rule Private port : Start port ; 20 ENd POrt 25 || Public 
> Port : Start port 20 ; ENd Port : 25.
> - Trigger UpdatePortForwardingRule api
> - ApI fails with following error : " Unable to update the private port of 
> port forwarding rule as the rule has port range "
> Expected behaviour -
> Port range should get modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9812) Update "updatePortForwardingRule" pi to include additional parameter to update the end port in case of port range

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894141#comment-15894141
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9812:


GitHub user mrunalinikankariya opened a pull request:

https://github.com/apache/cloudstack/pull/1985

CLOUDSTACK-9812:Update "updatePortForwardingRule" api to include additional 
parameter to update the end port in case of port range

Configure a PF rule Private port : Start port ; 20 ENd POrt 25 || Public 
Port : Start port 20 ; ENd Port : 25.
Trigger UpdatePortForwardingRule api
ApI fails with following error : " Unable to update the private port of 
port forwarding rule as the rule has port range "

Solution-
Port range gets modified

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Accelerite/cloudstack cloudstack-9812

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1985.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 #1985


commit c38e01b46e13411638b8a84a02fbad91b31ecbd4
Author: Mrunalini Kankariya 
Date:   2017-03-03T08:24:10Z

CLOUDSTACK-9812:Update updatePortForwardingRule api to include additional 
parameter to update the end port in case of port range




> Update "updatePortForwardingRule" pi to include additional parameter to 
> update the end port in case of port range
> -
>
> Key: CLOUDSTACK-9812
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9812
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: mrunalini
>
> - Configure a PF rule Private port : Start port ; 20 ENd POrt 25 || Public 
> Port : Start port 20 ; ENd Port : 25.
> - Trigger UpdatePortForwardingRule api
> - ApI fails with following error : " Unable to update the private port of 
> port forwarding rule as the rule has port range "
> Expected behaviour -
> Port range should get modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (CLOUDSTACK-9812) Update "updatePortForwardingRule" pi to include additional parameter to update the end port in case of port range

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15894135#comment-15894135
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9812:


Github user yvsubhash commented on the issue:

https://github.com/apache/cloudstack/pull/1984
  
@mrunalinikankariya One of the commits is not related to the issue


> Update "updatePortForwardingRule" pi to include additional parameter to 
> update the end port in case of port range
> -
>
> Key: CLOUDSTACK-9812
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9812
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: mrunalini
>
> - Configure a PF rule Private port : Start port ; 20 ENd POrt 25 || Public 
> Port : Start port 20 ; ENd Port : 25.
> - Trigger UpdatePortForwardingRule api
> - ApI fails with following error : " Unable to update the private port of 
> port forwarding rule as the rule has port range "
> Expected behaviour -
> Port range should get modified



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (CLOUDSTACK-9814) Unable to edit a Sub domain, which has the same name in different domains

[Nitesh Sarda (JIRA)]

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nitesh Sarda updated CLOUDSTACK-9814:
-
Summary: Unable to edit a Sub domain, which has the same name in different 
domains  (was: Unable to edit a Sub domain, which has the same name in two 
different domains)

> Unable to edit a Sub domain, which has the same name in different domains
> -
>
> Key: CLOUDSTACK-9814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9814
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>Reporter: Nitesh Sarda
>
> ISSUE
> 
> Unable to edit a Sub domain, which has the same name in different domains.
> TROUBLESHOOTING
> ==
> 1. Created two sub-domains with same name. Under two different domains.
> ROOT
> Domain 1 : India@b582a4cb-031e-49e7-afcf-4281fbf231b4
> AA01
> BB01
> Domain 2 : Test
> AA01
> 2. Try to edit resource - Click on edit - edit any parameter.
> EXPECTED BEHAVIOR
> ==
> It should allow to edit the required parameter and update the value.
> ACTUAL BEHAVIOR
> ==
> It throws an error "Failed to update specified domain id with name 'AA01' 
> since it already exists in system. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)