[jira] [Created] (CLOUDSTACK-7726) [Automation][XenServer] Failed to Remove LoadBalancer Rule due to callHostPlugin failure
Chandan Purushothama created CLOUDSTACK-7726: Summary: [Automation][XenServer] Failed to Remove LoadBalancer Rule due to callHostPlugin failure Key: CLOUDSTACK-7726 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7726 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.5.0 === CallHost Plugin Failure while trying to remove the Load Balancing Rule: === 2014-10-13 19:20:06,408 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-45:ctx-fb2667f4) Seq 1-122723089845846136: Executing request 2014-10-13 19:20:06,410 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-89:ctx-0a5fbdf2) callHostPlugin failed for cmd: createFileInDomr with args filepath: /etc/haproxy/haproxy.cfg.new.1413228006238, domrip: 169.254.2.250, filecontents: global log 127.0.0.1:3914 local0 warning maxconn 4096 maxpipes 1024 chroot /var/lib/haproxy user haproxy group haproxy daemon defaults log global modetcp option dontlognull retries 3 option redispatch option forwardfor option forceclose timeout connect5000 timeout client 5 timeout server 5 listen stats_on_public 10.220.166.19:8081 mode http option httpclose stats enable stats uri /admin?stats stats realm Haproxy\ Statistics stats authadmin1:AdMiN123 listen 10_220_166_28- 10.220.166.28: balance roundrobin , due to There was a failure communicating with the plugin. 2014-10-13 19:20:06,410 WARN [c.c.a.m.DirectAgentAttache] (DirectAgent-89:ctx-0a5fbdf2) Seq 1-122723089845846135: Throwable caught while executing command com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: createFileInDomr with args filepath: /etc/haproxy/haproxy.cfg.new.1413228006238, domrip: 169.254.2.250, filecontents: global log 127.0.0.1:3914 local0 warning maxconn 4096 maxpipes 1024 chroot /var/lib/haproxy user haproxy group haproxy daemon defaults log global modetcp option dontlognull retries 3 option redispatch option forwardfor option forceclose timeout connect5000 timeout client 5 timeout server 5 listen stats_on_public 10.220.166.19:8081 mode http option httpclose stats enable stats uri /admin?stats stats realm Haproxy\ Statistics stats authadmin1:AdMiN123 listen 10_220_166_28- 10.220.166.28: balance roundrobin , due to There was a failure communicating with the plugin. at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3670) at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.createFileInVR(CitrixResourceBase.java:575) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.applyConfigToVR(VirtualRoutingResource.java:161) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.applyConfigToVR(VirtualRoutingResource.java:155) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.applyConfig(VirtualRoutingResource.java:179) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.executeRequest(VirtualRoutingResource.java:125) at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:430) at com.cloud.hypervisor.xenserver.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:64) at com.cloud.hypervisor.xenserver.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:87) at com.cloud.hypervisor.xenserver.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:65) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:304) 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
[jira] [Updated] (CLOUDSTACK-7726) [Automation][XenServer] Failed to Remove LoadBalancer Rule due to callHostPlugin failure
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7726: - Attachment: management-server.zip [Automation][XenServer] Failed to Remove LoadBalancer Rule due to callHostPlugin failure Key: CLOUDSTACK-7726 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7726 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Priority: Critical Fix For: 4.5.0 Attachments: management-server.zip === CallHost Plugin Failure while trying to remove the Load Balancing Rule: === 2014-10-13 19:20:06,408 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-45:ctx-fb2667f4) Seq 1-122723089845846136: Executing request 2014-10-13 19:20:06,410 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-89:ctx-0a5fbdf2) callHostPlugin failed for cmd: createFileInDomr with args filepath: /etc/haproxy/haproxy.cfg.new.1413228006238, domrip: 169.254.2.250, filecontents: global log 127.0.0.1:3914 local0 warning maxconn 4096 maxpipes 1024 chroot /var/lib/haproxy user haproxy group haproxy daemon defaults log global modetcp option dontlognull retries 3 option redispatch option forwardfor option forceclose timeout connect5000 timeout client 5 timeout server 5 listen stats_on_public 10.220.166.19:8081 mode http option httpclose stats enable stats uri /admin?stats stats realm Haproxy\ Statistics stats authadmin1:AdMiN123 listen 10_220_166_28- 10.220.166.28: balance roundrobin , due to There was a failure communicating with the plugin. 2014-10-13 19:20:06,410 WARN [c.c.a.m.DirectAgentAttache] (DirectAgent-89:ctx-0a5fbdf2) Seq 1-122723089845846135: Throwable caught while executing command com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for cmd: createFileInDomr with args filepath: /etc/haproxy/haproxy.cfg.new.1413228006238, domrip: 169.254.2.250, filecontents: global log 127.0.0.1:3914 local0 warning maxconn 4096 maxpipes 1024 chroot /var/lib/haproxy user haproxy group haproxy daemon defaults log global modetcp option dontlognull retries 3 option redispatch option forwardfor option forceclose timeout connect5000 timeout client 5 timeout server 5 listen stats_on_public 10.220.166.19:8081 mode http option httpclose stats enable stats uri /admin?stats stats realm Haproxy\ Statistics stats authadmin1:AdMiN123 listen 10_220_166_28- 10.220.166.28: balance roundrobin , due to There was a failure communicating with the plugin. at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:3670) at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.createFileInVR(CitrixResourceBase.java:575) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.applyConfigToVR(VirtualRoutingResource.java:161) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.applyConfigToVR(VirtualRoutingResource.java:155) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.applyConfig(VirtualRoutingResource.java:179) at com.cloud.agent.resource.virtualnetwork.VirtualRoutingResource.executeRequest(VirtualRoutingResource.java:125) at com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:430) at com.cloud.hypervisor.xenserver.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:64) at com.cloud.hypervisor.xenserver.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:87) at com.cloud.hypervisor.xenserver.resource.XenServer620SP1Resource.executeRequest(XenServer620SP1Resource.java:65) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:304) at org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49) at
[jira] [Resolved] (CLOUDSTACK-7666) [Automation] Management server failed to start in latest RPM build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-7666. - Resolution: Not a Problem Commit is already got reverted which caused this issue. [Automation] Management server failed to start in latest RPM build --- Key: CLOUDSTACK-7666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7666 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Assignee: Sanjay Tripathi Priority: Blocker Fix For: 4.5.0 Management server failed to start with latest RPM build with below error Error while decrypting: GPU 2014-10-02 03:21:40,424 INFO [c.c.s.ConfigurationServerImpl] (main:null) Injected public and private keys into systemvm iso with result : null 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Start configuring cluster manager : ClusterManagerImpl 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster node IP : 127.0.0.1 2014-10-02 03:21:40,641 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster manager is configured. 2014-10-02 03:21:40,704 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: GPU 2014-10-02 03:21:51,541 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_66b08393 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_fbbaf2ed 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_1861e2e5 Looks like its regression in below checkin https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=39fe766c2b6fb6edd4c1bf828625b29d9bb87719 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (CLOUDSTACK-7666) [Automation] Management server failed to start in latest RPM build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi reopened CLOUDSTACK-7666: - [Automation] Management server failed to start in latest RPM build --- Key: CLOUDSTACK-7666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7666 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Assignee: Sanjay Tripathi Priority: Blocker Fix For: 4.5.0 Management server failed to start with latest RPM build with below error Error while decrypting: GPU 2014-10-02 03:21:40,424 INFO [c.c.s.ConfigurationServerImpl] (main:null) Injected public and private keys into systemvm iso with result : null 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Start configuring cluster manager : ClusterManagerImpl 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster node IP : 127.0.0.1 2014-10-02 03:21:40,641 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster manager is configured. 2014-10-02 03:21:40,704 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: GPU 2014-10-02 03:21:51,541 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_66b08393 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_fbbaf2ed 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_1861e2e5 Looks like its regression in below checkin https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=39fe766c2b6fb6edd4c1bf828625b29d9bb87719 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7666) [Automation] Management server failed to start in latest RPM build
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjay Tripathi resolved CLOUDSTACK-7666. - Resolution: Fixed [Automation] Management server failed to start in latest RPM build --- Key: CLOUDSTACK-7666 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7666 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Rayees Namathponnan Assignee: Sanjay Tripathi Priority: Blocker Fix For: 4.5.0 Management server failed to start with latest RPM build with below error Error while decrypting: GPU 2014-10-02 03:21:40,424 INFO [c.c.s.ConfigurationServerImpl] (main:null) Injected public and private keys into systemvm iso with result : null 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Start configuring cluster manager : ClusterManagerImpl 2014-10-02 03:21:40,600 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster node IP : 127.0.0.1 2014-10-02 03:21:40,641 INFO [c.c.c.ClusterManagerImpl] (main:null) Cluster manager is configured. 2014-10-02 03:21:40,704 DEBUG [c.c.u.c.DBEncryptionUtil] (main:null) Error while decrypting: GPU 2014-10-02 03:21:51,541 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.CloudStackAccountDaoImpl_EnhancerByCloudStack_66b08393 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.OfferingDaoImpl_EnhancerByCloudStack_fbbaf2ed 2014-10-02 03:21:51,554 INFO [c.c.u.c.ComponentContext] (main:null) Configuring com.cloud.bridge.persist.dao.SMetaDaoImpl_EnhancerByCloudStack_1861e2e5 Looks like its regression in below checkin https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=39fe766c2b6fb6edd4c1bf828625b29d9bb87719 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (CLOUDSTACK-7219) Cannot display Cluster Settings after 4.4 Upgrade
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daan Hoogland closed CLOUDSTACK-7219. - Resolution: Fixed fixed bu Wei's commit as reported by Pierre-Luc Cannot display Cluster Settings after 4.4 Upgrade - Key: CLOUDSTACK-7219 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7219 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: KVM, Management Server Affects Versions: 4.4.0 Environment: CentOS 6, KVM Hypervisor Reporter: Prieur Leary Priority: Blocker Fix For: 4.4.1 Attachments: cluster.png After upgrading MS to 4.4, when you to go: Home - Infrastructure - Clusters - Cluster 1 - Settings It does not display the settings underneath the column heading just, ERROR. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7313) Provisioning vpx in SDX from CS is failing
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajesh Battala resolved CLOUDSTACK-7313. Resolution: Fixed Provisioning vpx in SDX from CS is failing -- Key: CLOUDSTACK-7313 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7313 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Devices Affects Versions: 4.5.0 Reporter: Rajesh Battala Assignee: Rajesh Battala Priority: Critical Fix For: 4.5.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7727) [Automation] [LXC] Various BVT test issues with LXC
Alex Brett created CLOUDSTACK-7727: -- Summary: [Automation] [LXC] Various BVT test issues with LXC Key: CLOUDSTACK-7727 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7727 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Alex Brett Assignee: Alex Brett Fix For: 4.5.0 Various tests should skip when running with LXC due to the limitations it imposes. The limitations list from https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Enhancements is: * No Console access * No Live migration * No migration across clusters * No snapshot support * No upload/download volume support * No template creation from ROOT volume * No ISO support for create Vm This ticket is to modify the BVT tests to skip where appropriate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7728) Network with egress policy allow, VR reboot missed default rule
Jayapal Reddy created CLOUDSTACK-7728: - Summary: Network with egress policy allow, VR reboot missed default rule Key: CLOUDSTACK-7728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.1 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Repro steps: 1. Create isolated network with default egress policy allow. 2. Deploy VM in network so that VR got created. 3. VR comes up with iptables rules to allow all egress traffic. 4. Reboot VR. After reboot iptables rule to allow egress traffic is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7729) listVMSnapshot API not returning parent id in response
Damodar Reddy T created CLOUDSTACK-7729: --- Summary: listVMSnapshot API not returning parent id in response Key: CLOUDSTACK-7729 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7729 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 Reporter: Damodar Reddy T Assignee: Damodar Reddy T listVMSnapshot API not returning parent id in response. Documentation says listVMSnapshot returns parent id as well as parent name. BUT only parent name is getting in the response. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7730) Failed to create two icmp firewall rules
Jayapal Reddy created CLOUDSTACK-7730: - Summary: Failed to create two icmp firewall rules Key: CLOUDSTACK-7730 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7730 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.4.0 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 1. Add firewall ingress/egress with proto icmp, icmp type and code. 2. Add another icmp rule with different type and code. On adding second rule getting the following error. There is already a firewall rule specified with protocol = icmp with no ports This regression from the fix CLOUDSTACK-2694 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7527) XenServer heartbeat-script: make it reboot faster (when fencing)
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172370#comment-14172370 ] Malcolm Crossley commented on CLOUDSTACK-7527: -- Can you at least sync the disks before echoing b to /proc/sysrq-trigger You can do this with a echo s /proc/sysrq-trigger Also if you want to capture some state of the host you could trigger a crash instead which will run the Xenserver crashdump analyser. This will result in kernel dmesg ring and Xen dmesg ring being preserved. To trigger a crash: echo c proc/sysrq-trigger I would not trigger a crashdump by default because it won't be clear that Cloudstack initiated the crash. XenServer heartbeat-script: make it reboot faster (when fencing) Key: CLOUDSTACK-7527 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7527 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: XenServer Affects Versions: 4.3.0, 4.4.0 Reporter: Remi Bergsma Assignee: Daan Hoogland Priority: Minor xenheartbeat.sh: I've seen the 'reboot' command hang, even though it has the force option specified (last line of the script). Wouldn't it be better to invoke it like this: echo b /proc/sysrq-trigger Tested it, starts boot sequence immediately. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172921#comment-14172921 ] ASF subversion and git services commented on CLOUDSTACK-7532: - Commit 42f628c61c4070f891b16c1a81d2985bcf8b9281 in cloudstack's branch refs/heads/4.5 from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=42f628c ] CLOUDSTACK-7532: Template status is not shown in UI/API response for non-default account users. Show it if the owner of the template is the caller [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7732) [Automation] - Automate organization States Test Cases relating to enabling/disabling of zone,pod,host and cluster.
Sangeetha Hariharan created CLOUDSTACK-7732: --- Summary: [Automation] - Automate organization States Test Cases relating to enabling/disabling of zone,pod,host and cluster. Key: CLOUDSTACK-7732 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7732 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Test Affects Versions: 4.5.0 Reporter: Sangeetha Hariharan Fix For: 4.5.0 [Automation] - Automate organization States Test Cases relating to enabling/disabling of zone,pod,host and cluster -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172930#comment-14172930 ] ASF subversion and git services commented on CLOUDSTACK-7532: - Commit 3b442acdd7977d09de60dfe61eaf6f148df1af4b in cloudstack's branch refs/heads/master from [~nitinme] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3b442ac ] CLOUDSTACK-7532: Template status is not shown in UI/API response for non-default account users. Show it if the owner of the template is the caller (cherry picked from commit 42f628c61c4070f891b16c1a81d2985bcf8b9281) [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172934#comment-14172934 ] Nitin Mehta commented on CLOUDSTACK-7532: - Issue - Template status is not shown in UI/API response for non-default account users Fix - Show status if the owner of the template is the caller or a root admin QA notes - test that status is coming through the API and the UI. test the status is coming when download is in progres, completed or in error and is shown only to the owner and root admin in all these cases. [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta resolved CLOUDSTACK-7532. - Resolution: Fixed [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nitin Mehta updated CLOUDSTACK-7532: Comment: was deleted (was: [~nvnp_sanjeev] - If there is a UI bug as well please open it separately) [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7532) [Templates] Template status is not shown in UI/API response for non-default account users
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14172984#comment-14172984 ] Nitin Mehta commented on CLOUDSTACK-7532: - If there is a UI bug as well please open it separately [Templates] Template status is not shown in UI/API response for non-default account users - Key: CLOUDSTACK-7532 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7532 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: API, Template Affects Versions: 4.5.0 Environment: Latest build from master with commit: c33fea2cd27664db32c1173e98511470bf0a0724 Reporter: Sanjeev N Assignee: Nitin Mehta Priority: Critical Labels: api, templates Fix For: 4.5.0 Attachments: template_status.PNG [Templates] Template status is not shown in UI/API response for non-default account users Steps to Reproduce: === 1.Bring up CS with latest build 2.Create one account under root domain 3.Register template using the account created above 4.After the template download is completed verify the template status using the account created at step2 Expected Result: == In UI/API response status field should be there and it should be set to Download Complete after the successful template download. Actual Behavior: Status is shown only for the default admin user. But it is not showed to other account users. Impact: == Marvin tests which use template register would fail because of the status filed missing. Following is the code from base.py where the tests are failing: elif 'Downloaded' in template.status: time.sleep(interval) becasue template.status is NoneType API: http://10.147.40.10:8080/client/api?command=listTemplatessessionkey=SgRK4kwpxxjg3Jx%2FwePLoS0aK3c%3Dtemplatefilter=selfid=550ad6ac-38d2-11e4-a56e-d4ae527ccfaa_=1410351906876 API Response: === listtemplatesresponse cloud-stack-version=4.5.0-SNAPSHOTcount1/counttemplateid550ad6ac-38d2-11e4-a56e-d4ae527ccfaa/idnameCentOS 5.6(64-bit) no GUI (XenServer)/namedisplaytextCentOS 5.6(64-bit) no GUI (XenServer)/displaytextispublictrue/ispubliccreated2014-09-10T15:59:38+0530/createdisreadytrue/isreadypasswordenabledfalse/passwordenabledformatVHD/formatisfeaturedtrue/isfeaturedcrossZonestrue/crossZonesostypeid572126ea-38d2-11e4-a56e-d4ae527ccfaa/ostypeidostypenameCentOS 5.6 (64-bit)/ostypenameaccountsystem/accountzoneid680f7c3a-a9ee-4ed3-b594-981d56f8da4b/zoneidzonenamez2/zonenamesize21474836480/sizetemplatetypeBUILTIN/templatetypehypervisorXenServer/hypervisordomainROOT/domaindomainid54e9d4e4-38d2-11e4-a56e-d4ae527ccfaa/domainidisextractabletrue/isextractablechecksum905cec879afd9c9d22ecc8036131a180/checksumsshkeyenabledfalse/sshkeyenabledisdynamicallyscalabletrue/isdynamicallyscalable/template/listtemplatesresponse In the above API response status field is missing. This bug is easily reproducible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-6177) CS does XS master switch, which may cause weird XS behavior
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu resolved CLOUDSTACK-6177. Resolution: Fixed fixed by commit b79f949e1bd9d62b3ebcce424608cb4b22e69897 Author: Anthony Xu anthony...@citrix.com Date: Tue Jan 21 17:55:09 2014 -0800 CLOUDSTACK-5923: CS doesn't do master switch for XS any more, CS will depend on XS HA to do master switch, XS HA needs to be enabled. Conflicts: plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/discoverer/XcpServerDiscoverer.java plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/CitrixResourceBase.java plugins/hypervisors/xen/src/com/cloud/hypervisor/xen/resource/XenServerConnectionPool.java CS does XS master switch, which may cause weird XS behavior --- Key: CLOUDSTACK-6177 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6177 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Hypervisor Controller Affects Versions: 4.3.0 Environment: XS 6.2 with CS 4.3.0 Reporter: Anthony Xu Assignee: Anthony Xu Priority: Critical Fix For: 4.4.0 When XS master is down, CS uses pool-emergency-transition-to-master and pool-recover-slaves API to choose a new master, this API is not safe, and should be only used in emergent situation, this API may cause XS use a little bit old(5 minutes old) version of XS DB, some of object may be missing in the old XS DB, which may cause weird behavior, you may not be able to start VM. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7229) move vmsync outof ping command
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu updated CLOUDSTACK-7229: --- Issue Type: Improvement (was: Bug) move vmsync outof ping command -- Key: CLOUDSTACK-7229 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7229 Project: CloudStack Issue Type: Improvement Security Level: Public(Anyone can view this level - this is the default.) Reporter: Anthony Xu Assignee: Anthony Xu Cs does vmsync in ping command, if there are many hosts and many vms, it takes sometime to handle vmsync, which may cause host ping timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-5834) [upgrade]Error while collecting disk stats from : You gave an invalid object reference. The object may have recently been deleted
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu resolved CLOUDSTACK-5834. Resolution: Fixed Fix Version/s: 4.5.0 fixed by commit 0fe1d4bb27de83f3fff4e22d0bb501bc2451e62f Author: Anthony Xu anthony...@citrix.com Date: Mon Aug 4 12:19:16 2014 -0700 got VBD statistics from RRD [upgrade]Error while collecting disk stats from : You gave an invalid object reference. The object may have recently been deleted -- Key: CLOUDSTACK-5834 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5834 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server, XenServer Affects Versions: 4.3.0 Reporter: prashant kumar mishra Assignee: Anthony Xu Fix For: 4.4.0, 4.5.0 Attachments: MS_XEN_log_DB.rar Steps == 1-prepare ACS 4.2 setup with xen6.2 host 2-upgrade CS to 4.3 and upgrade xen 6.2 to xen6.2sp1 After upgrade i am seeing error message in log whenever VmStatsCollector is running. Logs == 2014-01-08 13:15:08,182 DEBUG [c.c.s.StatsCollector] (StatsCollector-2:ctx-aa75b506) VmStatsCollector is running... 2014-01-08 13:15:08,207 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-141:ctx-74d0d04a) Seq 1-498139202: Executing request 2014-01-08 13:15:08,358 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-141:ctx-74d0d04a) Vm cpu utilization 0.0 2014-01-08 13:15:08,359 DEBUG [c.c.h.x.r.CitrixResourceBase] (DirectAgent-141:ctx-74d0d04a) Vm cpu utilization 0.00453125 2014-01-08 13:15:08,369 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-141:ctx-74d0d04a) Error while collecting disk stats from : You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given. at com.xensource.xenapi.Types.checkResponse(Types.java:209) at com.xensource.xenapi.Connection.dispatch(Connection.java:368) at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool.java:909) at com.xensource.xenapi.VBDMetrics.getIoReadKbs(VBDMetrics.java:210) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.getVmStats(CitrixResourceBase.java:2784) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:2684) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:493) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266) 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) 2014-01-08 13:15:08,371 DEBUG [c.c.a.m.DirectAgentAttache] (DirectAgent-141:ctx-74d0d04a) Seq 1-498139202: Response Received: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-5357) Xenserver - Failed to create snapshot due to unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) when seconda
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu updated CLOUDSTACK-5357: --- Fix Version/s: (was: 4.4.0) Xenserver - Failed to create snapshot due to unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) when secondary store was unavaiable for 1 and 1/2 hours and then brought up.. -- Key: CLOUDSTACK-5357 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5357 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: Build from 4.3 Reporter: Sangeetha Hariharan Assignee: Anthony Xu Priority: Minor Attachments: Snaposhotfailures.rar Xenserver - Failed to create snapshot due to unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) when secondary store was unavaiable for 1 and 1/2 hours and then brought up. Set up: Advanced Zone with 2 Xenserver 6.2 hosts: Steps to reproduce the problem: 1. Deploy 5 Vms in each of the hosts with 10 GB ROOT volume size , so we start with 10 Vms. 2. Start concurrent hourly snapshots for ROOT volumes of all the Vms. 3. Shutdown the Secondary storage server when the snapshots are in the progress. 4. Bring the Secondary storage server up after 1and 1/2 hour. After the secondary store was brought up , we see the snapshot process continue to be active ( I see the copy command that was halted when the secondary store was down , starts progressing when server is drought up online). I also see that the snapshot process has been completed on the secondary store. But management server throws the following exception and leaves behind the snapshot in CreatedOnPrimary state in DB. 2013-12-03 19:24:36,296 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-252:ctx-8ca50e48) unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) due to You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given. at com.xensource.xenapi.Types.checkResponse(Types.java:209) at com.xensource.xenapi.Connection.dispatch(Connection.java:368) at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool .java:909) at com.xensource.xenapi.Task.destroy(Task.java:616) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.cloudVDIcopy(CitrixResourceBase.java:3920) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.backupSnapshot(XenServerStorageProcessor.java:1268 ) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java: 90) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHan dlerBase.java:50) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:613) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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:10 3) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.ja va:178) at
[jira] [Resolved] (CLOUDSTACK-5357) Xenserver - Failed to create snapshot due to unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) when second
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anthony Xu resolved CLOUDSTACK-5357. Resolution: Won't Fix if late snapshot works. I didn't see anything wrong here Xenserver - Failed to create snapshot due to unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) when secondary store was unavaiable for 1 and 1/2 hours and then brought up.. -- Key: CLOUDSTACK-5357 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5357 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Management Server Affects Versions: 4.3.0 Environment: Build from 4.3 Reporter: Sangeetha Hariharan Assignee: Anthony Xu Priority: Minor Attachments: Snaposhotfailures.rar Xenserver - Failed to create snapshot due to unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) when secondary store was unavaiable for 1 and 1/2 hours and then brought up. Set up: Advanced Zone with 2 Xenserver 6.2 hosts: Steps to reproduce the problem: 1. Deploy 5 Vms in each of the hosts with 10 GB ROOT volume size , so we start with 10 Vms. 2. Start concurrent hourly snapshots for ROOT volumes of all the Vms. 3. Shutdown the Secondary storage server when the snapshots are in the progress. 4. Bring the Secondary storage server up after 1and 1/2 hour. After the secondary store was brought up , we see the snapshot process continue to be active ( I see the copy command that was halted when the secondary store was down , starts progressing when server is drought up online). I also see that the snapshot process has been completed on the secondary store. But management server throws the following exception and leaves behind the snapshot in CreatedOnPrimary state in DB. 2013-12-03 19:24:36,296 WARN [c.c.h.x.r.CitrixResourceBase] (DirectAgent-252:ctx-8ca50e48) unable to destroy task(com.xe nsource.xenapi.Task@67d312d6) on host(23af93a0-93ff-40cb-ba11-a11d1b884d37) due to You gave an invalid object reference. The object may have recently been deleted. The class parameter gives the type of reference given, and the handle parameter echoes the bad value given. at com.xensource.xenapi.Types.checkResponse(Types.java:209) at com.xensource.xenapi.Connection.dispatch(Connection.java:368) at com.cloud.hypervisor.xen.resource.XenServerConnectionPool$XenServerConnection.dispatch(XenServerConnectionPool .java:909) at com.xensource.xenapi.Task.destroy(Task.java:616) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.cloudVDIcopy(CitrixResourceBase.java:3920) at com.cloud.hypervisor.xen.resource.XenServerStorageProcessor.backupSnapshot(XenServerStorageProcessor.java:1268 ) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.execute(StorageSubsystemCommandHandlerBase.java: 90) at com.cloud.storage.resource.StorageSubsystemCommandHandlerBase.handleStorageCommands(StorageSubsystemCommandHan dlerBase.java:50) at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:613) at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:59) at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:106) at com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216) 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:10 3) 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$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.ja va:178)
[jira] [Updated] (CLOUDSTACK-7734) CLONE - addHost fails for XenServer with vSwitch networking
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Xu updated CLOUDSTACK-7734:
---
Fix Version/s: (was: 4.4.0)
4.5.0
CLONE - addHost fails for XenServer with vSwitch networking
---
Key: CLOUDSTACK-7734
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7734
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Anthony Xu
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.5.0
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use
bridge works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143,
via: 1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup
agent 1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due
to Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link
for 1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect
to listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event
= AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other
nodes of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:773)
at
[jira] [Created] (CLOUDSTACK-7734) CLONE - addHost fails for XenServer with vSwitch networking
Anthony Xu created CLOUDSTACK-7734:
--
Summary: CLONE - addHost fails for XenServer with vSwitch
networking
Key: CLOUDSTACK-7734
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7734
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: XenServer
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Anthony Xu
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.4.0
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use bridge
works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143, via:
1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup agent
1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due to
Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link for
1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect to
listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event =
AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other nodes
of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect due
to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:773)
at
com.cloud.resource.ResourceManagerImpl.discoverHosts(ResourceManagerImpl.java:586)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
[jira] [Updated] (CLOUDSTACK-7734) CLONE - addHost fails for XenServer with vSwitch networking
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Xu updated CLOUDSTACK-7734:
---
Component/s: (was: XenServer)
Doc
CLONE - addHost fails for XenServer with vSwitch networking
---
Key: CLOUDSTACK-7734
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7734
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Anthony Xu
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.5.0
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use
bridge works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143,
via: 1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup
agent 1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due
to Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link
for 1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect
to listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event
= AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other
nodes of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:773)
at
[jira] [Commented] (CLOUDSTACK-7734) CLONE - addHost fails for XenServer with vSwitch networking
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173072#comment-14173072
]
Anthony Xu commented on CLOUDSTACK-7734:
add doc,
user need to add host to XS pool first, then add it to CS in 4.5
CLONE - addHost fails for XenServer with vSwitch networking
---
Key: CLOUDSTACK-7734
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7734
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Anthony Xu
Priority: Critical
Fix For: 4.5.0
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use
bridge works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143,
via: 1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup
agent 1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due
to Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link
for 1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect
to listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event
= AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other
nodes of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
at
[jira] [Updated] (CLOUDSTACK-7734) CLONE - addHost fails for XenServer with vSwitch networking
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Xu updated CLOUDSTACK-7734:
---
Assignee: (was: Anthony Xu)
CLONE - addHost fails for XenServer with vSwitch networking
---
Key: CLOUDSTACK-7734
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7734
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: Doc
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Anthony Xu
Priority: Critical
Fix For: 4.5.0
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use
bridge works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143,
via: 1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup
agent 1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due
to Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link
for 1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect
to listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event
= AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other
nodes of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
at
com.cloud.resource.ResourceManagerImpl.discoverHostsFull(ResourceManagerImpl.java:773)
at
[jira] [Commented] (CLOUDSTACK-6496) addHost fails for XenServer with vSwitch networking
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173075#comment-14173075
]
Anthony Xu commented on CLOUDSTACK-6496:
filed doc bug
https://issues.apache.org/jira/browse/CLOUDSTACK-7734
mark this one as resolved.
addHost fails for XenServer with vSwitch networking
---
Key: CLOUDSTACK-6496
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6496
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: XenServer
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Doug Clark
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.4.0
Attachments: management-server.log
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use
bridge works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143,
via: 1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup
agent 1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due
to Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link
for 1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect
to listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event
= AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other
nodes of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
[jira] [Resolved] (CLOUDSTACK-6496) addHost fails for XenServer with vSwitch networking
[
https://issues.apache.org/jira/browse/CLOUDSTACK-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anthony Xu resolved CLOUDSTACK-6496.
Resolution: Not a Problem
Fix Version/s: (was: 4.4.0)
4.5.0
addHost fails for XenServer with vSwitch networking
---
Key: CLOUDSTACK-6496
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6496
Project: CloudStack
Issue Type: Bug
Security Level: Public(Anyone can view this level - this is the
default.)
Components: XenServer
Affects Versions: Future, 4.4.0
Environment: MS: ACS Master
(http://jenkins.buildacloud.org/job/package-rhel63-master/2647)
XenServer 6.2
Reporter: Doug Clark
Assignee: Anthony Xu
Priority: Critical
Fix For: 4.5.0
Attachments: management-server.log
Attempt to add a XenServer host (with the default vSwitch networking) to a
Basic Networking Zone fails. Adding a XenServer host configured to use
bridge works ok.
From MS log (attached):
{noformat}
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Failed to configure brige firewall
2014-04-24 13:41:07,361 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-1:ctx-3e360a0c) Check host 10.81.40.102 for CSP is installed or
not and check network mode for bridge
2014-04-24 13:41:07,361 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: Response Received:
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (DirectAgent-1:ctx-3e360a0c)
Seq 1-7133701809754865665: Processing: { Ans: , MgmtId: 275410316893143,
via: 1, Ver: v1, Flags: 110, [{com.cloud.agent.api.Set
upAnswer:{_reconnect:true,result:false,details:Failed to configure
brige firewall,wait:0}}] }
2014-04-24 13:41:07,363 DEBUG [c.c.a.t.Request] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Seq 1-7133701809754865665: Received: { Ans: ,
MgmtId: 275410316893143, via: 1, Ver: v1, Flags: 110,
{ SetupAnswer } }
2014-04-24 13:41:07,363 WARN [c.c.h.x.d.XcpServerDiscoverer]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to setup
agent 1 due to Failed to configure brige firewall
2014-04-24 13:41:07,364 INFO [c.c.u.e.CSExceptionErrorCode]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Could not find
exception: com.cloud.exception.ConnectionException in error code list for
exceptions
2014-04-24 13:41:07,364 WARN [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Monitor
XcpServerDiscoverer says there is an error in the connect process for 1 due
to Reini
tialize agent after setup.
2014-04-24 13:41:07,364 INFO [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Host 1 is
disconnecting with event AgentDisconnected
2014-04-24 13:41:07,364 DEBUG [c.c.a.m.AgentAttache]
(DirectAgent-1:ctx-3e360a0c) Seq 1-7133701809754865665: No more commands found
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) The next status of
agent 1is Alert, current status is Connecting
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Deregistering link
for 1 with state Alert
2014-04-24 13:41:07,366 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Remove Agent : 1
{noformat}
...snip...
{noformat}
2014-04-24 13:41:07,460 DEBUG [c.c.a.m.AgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Sending Disconnect
to listener: com.cloud.network.router.VirtualNetworkApplianceManagerImpl
2014-04-24 13:41:07,460 DEBUG [c.c.h.Status] (catalina-exec-2:ctx-407da4e1
ctx-e02434c0 ctx-a13beb18) Transition:[Resource state = Enabled, Agent event
= AgentDisconnected, Host id = 1, name = xrtuk-09-03]
2014-04-24 13:41:07,766 DEBUG [c.c.a.m.ClusteredAgentManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Notifying other
nodes of to disconnect
2014-04-24 13:41:07,770 WARN [c.c.r.ResourceManagerImpl]
(catalina-exec-2:ctx-407da4e1 ctx-e02434c0 ctx-a13beb18) Unable to connect
due to
com.cloud.exception.ConnectionException: Reinitialize agent after setup.
at
com.cloud.hypervisor.xen.discoverer.XcpServerDiscoverer.processConnect(XcpServerDiscoverer.java:657)
at
com.cloud.agent.manager.AgentManagerImpl.notifyMonitorsOfConnection(AgentManagerImpl.java:514)
at
com.cloud.agent.manager.AgentManagerImpl.handleDirectConnectAgent(AgentManagerImpl.java:1428)
at
com.cloud.resource.ResourceManagerImpl.createHostAndAgent(ResourceManagerImpl.java:1767)
at
[jira] [Updated] (CLOUDSTACK-7733) Admin/Regular User is not allowed to stop/start Vms that are running on disabled hosts.
[
https://issues.apache.org/jira/browse/CLOUDSTACK-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sangeetha Hariharan updated CLOUDSTACK-7733:
Priority: Critical (was: Major)
Admin/Regular User is not allowed to stop/start Vms that are running on
disabled hosts.
---
Key: CLOUDSTACK-7733
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7733
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
Environment: Build from master
Reporter: Sangeetha Hariharan
Priority: Critical
Steps to reproduce the problem:
Deploy a Vm in a host say host1 using a service offering that has hosttags
that matches with host1.
Disable host.
As admin , stop this VM.
Now try to start the VM.
This fails with job failed due to exception Unable to create a deployment
for VM[User|i-20-63-VM
{jobprocstatus : 0, created : u'2014-10-15T08:21:04-0400', jobresult :
{errorcode : 530, errortext : u'Job failed due to exception Unable to create
a deployment for VM[User|i-20-63-VM]'}, cmd :
u'org.apache.cloudstack.api.command.admin.vm.StartVMCmdByAdmin', userid :
u'f3d01d86-93bb-4ec7-a249-f1dc59ba33a1', jobstatus : 2, jobid :
u'fbe3432d-f90c-49d7-a5ea-f1e65e88aae7', jobresultcode : 530, jobinstanceid :
u'c9987836-8d76-4a55-bdce-6ef81c4cf51d', jobresulttype : u'object',
jobinstancetype : u'VirtualMachine', accountid :
u'54b7a442-2b1f-4df9-b3cc-14a4d8537a74'}
Management server logs indicating that Vms cannot be started on the last host
Id , when the host is disabled:
2014-10-15 09:37:24,480 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-79:ctx-746fc
d6f job-558/job-559 ctx-246fb1a1) Trying to allocate a host and storage pools
from dc:1, pod:1,clus
ter:2, requested cpu: 100, requested ram: 134217728
2014-10-15 09:37:24,480 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-79:ctx-746fcd6f job-558/job-559 ctx-246fb1a1) Is ROOT
volume READY (pool already allocated)?: Yes
2014-10-15 09:37:24,480 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-79:ctx-746fcd6f job-558/job-559 ctx-246fb1a1) This VM has
last host_id specified, trying to choose the same host: 4
2014-10-15 09:37:24,484 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-79:ctx-746fcd6f job-558/job-559 ctx-246fb1a1) The last
host of this VM is not UP or is not enabled, host status is: Up, host
resource state is: Disabled
2014-10-15 09:37:24,484 DEBUG [c.c.d.DeploymentPlanningManagerImpl]
(Work-Job-Executor-79:ctx-746fcd6f job-558/job-559 ctx-246fb1a1) Cannot
choose the last host to deploy this VM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7736) UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter().
Jessica Wang created CLOUDSTACK-7736: Summary: UI - listView widget - select view dropdown on top of listView - prefilter() - include original args.context when passing it to prefilter(). Key: CLOUDSTACK-7736 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7736 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: UI Reporter: Jessica Wang Assignee: Jessica Wang -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (CLOUDSTACK-7737) [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering
Chandan Purushothama created CLOUDSTACK-7737: Summary: [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering Key: CLOUDSTACK-7737 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7737 Project: CloudStack Issue Type: Bug Security Level: Public (Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 Deployed VM has the following memory configuration on the VM: [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem MemTotal: 363416 kB MemFree: 81864 kB [root@Atoms-VM-2 ~]# Which is around 354.8984375 MB But the Service Offering specified specifies 512 MB as shown below: mysql select id,name,instance_name,state,service_offering_id from vm_instance where id=59 \G *** 1. row *** id: 59 name: Atoms-VM-2 instance_name: i-36-59-VM state: Running service_offering_id: 1 1 row in set (0.00 sec) mysql select * from service_offering where id=1 \G *** 1. row *** id: 1 cpu: 1 speed: 500 ram_size: 512 nw_rate: NULL mc_rate: NULL ha_enabled: 0 limit_cpu_use: 0 host_tag: NULL default_use: 0 vm_type: NULL sort_key: 0 is_volatile: 0 deployment_planner: NULL 1 row in set (0.00 sec) mysql -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-7737) [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chandan Purushothama updated CLOUDSTACK-7737: - Description: Deployed VM has the following memory configuration on the VM: [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem MemTotal: 363416 kB MemFree: 81864 kB [root@Atoms-VM-2 ~]# Which is around 354.8984375 MB But the Service Offering specified specifies 512 MB as shown below: mysql select id,name,instance_name,state,service_offering_id from vm_instance where id=59 \G id: 59 name: Atoms-VM-2 instance_name: i-36-59-VM state: Running service_offering_id: 1 1 row in set (0.00 sec) mysql select * from service_offering where id=1 \G id: 1 cpu: 1 speed: 500 ram_size: 512 nw_rate: NULL mc_rate: NULL ha_enabled: 0 limit_cpu_use: 0 host_tag: NULL default_use: 0 vm_type: NULL sort_key: 0 is_volatile: 0 deployment_planner: NULL 1 row in set (0.00 sec) mysql was: Deployed VM has the following memory configuration on the VM: [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem MemTotal: 363416 kB MemFree: 81864 kB [root@Atoms-VM-2 ~]# Which is around 354.8984375 MB But the Service Offering specified specifies 512 MB as shown below: mysql select id,name,instance_name,state,service_offering_id from vm_instance where id=59 \G *** 1. row *** id: 59 name: Atoms-VM-2 instance_name: i-36-59-VM state: Running service_offering_id: 1 1 row in set (0.00 sec) mysql select * from service_offering where id=1 \G *** 1. row *** id: 1 cpu: 1 speed: 500 ram_size: 512 nw_rate: NULL mc_rate: NULL ha_enabled: 0 limit_cpu_use: 0 host_tag: NULL default_use: 0 vm_type: NULL sort_key: 0 is_volatile: 0 deployment_planner: NULL 1 row in set (0.00 sec) mysql [Automation] [HyperV] Deployed VM is not respecting the memory configuration specified in the service offering -- Key: CLOUDSTACK-7737 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7737 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Automation Affects Versions: 4.5.0 Reporter: Chandan Purushothama Assignee: Devdeep Singh Priority: Critical Fix For: 4.5.0 Deployed VM has the following memory configuration on the VM: [root@Atoms-VM-2 ~]# cat /proc/meminfo | grep Mem MemTotal: 363416 kB MemFree: 81864 kB [root@Atoms-VM-2 ~]# Which is around 354.8984375 MB But the Service Offering specified specifies 512 MB as shown below: mysql select id,name,instance_name,state,service_offering_id from vm_instance where id=59 \G id: 59 name: Atoms-VM-2 instance_name: i-36-59-VM state: Running service_offering_id: 1 1 row in set (0.00 sec) mysql select * from service_offering where id=1 \G id: 1 cpu: 1 speed: 500 ram_size: 512 nw_rate: NULL mc_rate: NULL ha_enabled: 0 limit_cpu_use: 0 host_tag: NULL default_use: 0 vm_type: NULL sort_key: 0 is_volatile: 0 deployment_planner: NULL 1 row in set (0.00 sec) mysql -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7728) Network with egress policy allow, VR reboot missed default rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173323#comment-14173323 ] ASF subversion and git services commented on CLOUDSTACK-7728: - Commit 7cd34385801514b8c0ce51bc0d2ea036713c285c in cloudstack's branch refs/heads/master from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7cd3438 ] CLOUDSTACK-7728: Fixed adding icmp rules with different types and codes Network with egress policy allow, VR reboot missed default rule --- Key: CLOUDSTACK-7728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.1 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Repro steps: 1. Create isolated network with default egress policy allow. 2. Deploy VM in network so that VR got created. 3. VR comes up with iptables rules to allow all egress traffic. 4. Reboot VR. After reboot iptables rule to allow egress traffic is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7728) Network with egress policy allow, VR reboot missed default rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173324#comment-14173324 ] ASF subversion and git services commented on CLOUDSTACK-7728: - Commit 55e11cddca1f9db3a3fe29404b4eff634da60bcb in cloudstack's branch refs/heads/master from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=55e11cd ] CLOUDSTACK-7728: Fixed adding iptables rules for egress allow on VR reboot Network with egress policy allow, VR reboot missed default rule --- Key: CLOUDSTACK-7728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.1 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Repro steps: 1. Create isolated network with default egress policy allow. 2. Deploy VM in network so that VR got created. 3. VR comes up with iptables rules to allow all egress traffic. 4. Reboot VR. After reboot iptables rule to allow egress traffic is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7536) user vm can get a gateway ip in case of shared network.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173321#comment-14173321 ] ASF subversion and git services commented on CLOUDSTACK-7536: - Commit 6967c6c229d0153bae6fd87e0d87d6669518df29 in cloudstack's branch refs/heads/master from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6967c6c ] CLOUDSTACK-7536 user vm can get a gateway ip when gateway ip is a part of the guest ip range. Signed-off-by: Jayapal jaya...@apache.org user vm can get a gateway ip in case of shared network. --- Key: CLOUDSTACK-7536 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7536 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: Bharat Kumar Assignee: Bharat Kumar Fix For: 4.5.0 steps to reproduce. 1.) create a shared network with the following details. gateway 10.136.10.1 netmask 255.255.255.0 guest ip range 10.136.10.1 to 10.136.10.20 (note that the gateway ip is a part of the guest ip range.) 2.) deploy a vm the gateway ip gets allocated to a uservm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7728) Network with egress policy allow, VR reboot missed default rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173327#comment-14173327 ] ASF subversion and git services commented on CLOUDSTACK-7728: - Commit f488a8f72cfa60ed9f6540f1d6ec1cb3b44579fa in cloudstack's branch refs/heads/4.5 from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f488a8f ] CLOUDSTACK-7728: Fixed adding icmp rules with different types and codes Network with egress policy allow, VR reboot missed default rule --- Key: CLOUDSTACK-7728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.1 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Repro steps: 1. Create isolated network with default egress policy allow. 2. Deploy VM in network so that VR got created. 3. VR comes up with iptables rules to allow all egress traffic. 4. Reboot VR. After reboot iptables rule to allow egress traffic is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7536) user vm can get a gateway ip in case of shared network.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173326#comment-14173326 ] ASF subversion and git services commented on CLOUDSTACK-7536: - Commit 080bc2e2e936453078c33341453db99e62fb131f in cloudstack's branch refs/heads/4.5 from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=080bc2e ] CLOUDSTACK-7536 user vm can get a gateway ip when gateway ip is a part of the guest ip range. Signed-off-by: Jayapal jaya...@apache.org user vm can get a gateway ip in case of shared network. --- Key: CLOUDSTACK-7536 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7536 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: Bharat Kumar Assignee: Bharat Kumar Fix For: 4.5.0 steps to reproduce. 1.) create a shared network with the following details. gateway 10.136.10.1 netmask 255.255.255.0 guest ip range 10.136.10.1 to 10.136.10.20 (note that the gateway ip is a part of the guest ip range.) 2.) deploy a vm the gateway ip gets allocated to a uservm. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7728) Network with egress policy allow, VR reboot missed default rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173328#comment-14173328 ] ASF subversion and git services commented on CLOUDSTACK-7728: - Commit e257c13f167791c17967ad0d37a545ccbd145efd in cloudstack's branch refs/heads/4.5 from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e257c13 ] CLOUDSTACK-7728: Fixed adding iptables rules for egress allow on VR reboot Network with egress policy allow, VR reboot missed default rule --- Key: CLOUDSTACK-7728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.1 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Repro steps: 1. Create isolated network with default egress policy allow. 2. Deploy VM in network so that VR got created. 3. VR comes up with iptables rules to allow all egress traffic. 4. Reboot VR. After reboot iptables rule to allow egress traffic is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7729) listVMSnapshot API not returning parent id in response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173343#comment-14173343 ] ASF subversion and git services commented on CLOUDSTACK-7729: - Commit 7fe3c45142172e003fda340f779567f73525ffd8 in cloudstack's branch refs/heads/master from [~damoder.reddy] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=7fe3c45 ] CLOUDSTACK-7729: listVMSnapshot API not returning parent id in response listVMSnapshot API not returning parent id in response -- Key: CLOUDSTACK-7729 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7729 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 Reporter: Damodar Reddy T Assignee: Damodar Reddy T listVMSnapshot API not returning parent id in response. Documentation says listVMSnapshot returns parent id as well as parent name. BUT only parent name is getting in the response. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (CLOUDSTACK-7729) listVMSnapshot API not returning parent id in response
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Damodar Reddy T resolved CLOUDSTACK-7729. - Resolution: Fixed listVMSnapshot API not returning parent id in response -- Key: CLOUDSTACK-7729 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7729 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 Reporter: Damodar Reddy T Assignee: Damodar Reddy T listVMSnapshot API not returning parent id in response. Documentation says listVMSnapshot returns parent id as well as parent name. BUT only parent name is getting in the response. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CLOUDSTACK-7728) Network with egress policy allow, VR reboot missed default rule
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173359#comment-14173359 ] ASF subversion and git services commented on CLOUDSTACK-7728: - Commit 53ee4cd794eb18458ee77b49f15af8277e777a42 in cloudstack's branch refs/heads/4.5 from Jayapal [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=53ee4cd ] CLOUDSTACK-7728: Removed duplicate import Network with egress policy allow, VR reboot missed default rule --- Key: CLOUDSTACK-7728 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7728 Project: CloudStack Issue Type: Bug Security Level: Public(Anyone can view this level - this is the default.) Components: Network Controller Affects Versions: 4.2.1 Reporter: Jayapal Reddy Assignee: Jayapal Reddy Fix For: 4.5.0 Repro steps: 1. Create isolated network with default egress policy allow. 2. Deploy VM in network so that VR got created. 3. VR comes up with iptables rules to allow all egress traffic. 4. Reboot VR. After reboot iptables rule to allow egress traffic is missed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
