[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-01 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-5709:
--

CentOS 6.5 is nor supported yet right??
Also need to review edison's comments from below mail thread to understand the 
actual issue. 

> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Monday, December 23, 2013 6:35 AM
> To: d...@cloudstack.apache.org
> Subject: Re: [VOTE] 3rd round of voting for ASF 4.2.1 RC
> 
> On 23.12.2013 05:42, Abhinandan Prateek wrote:
> > It gives me immense pleasure to inform that the vote to label this 
> > ASF
> > 4.2.1 RC as the GA release has been passed with following stats:
> 
> Can someone check KVM volume snapshots before declaring this GA? It's 
> been consistently broken for me in 4.2.1-SNAPSHOT with NFS as well as 
> GlusterFS shared mount point.
> It was working in 4.2.0 afaicr.

In the ACS release(since 4.0), KVM snapshot only works when CLVM is used as 
primary storage, otherwise, taking snapshot in KVM will fail, as there is no 
formal way to backup snapshot from primary storage to secondary storage.

> 
> I've sent several emails about this as well as bothering people in 
> CLOUDSTACK-5393.
> http://www.mail-archive.com/dev@cloudstack.apache.org/msg20123.html
> 
> HTH
> Lucian
> 
> --
> Sent from the Delta quadrant using Borg technology!
> 
> Nux!
> www.nux.ro


> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

I could downgrade CentOS to an outdated version, but this puts me at risk.
Your colleague Sandhu reported success with NFS in 4.2 branch
https://issues.apache.org/jira/browse/CLOUDSTACK-5393?focusedCommentId=13859469&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13859469

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Wei Zhou (JIRA)

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

Wei Zhou commented on CLOUDSTACK-5709:
--

it is better if you can upload the related agent.log

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

Hello,

agent.log is almost completely mute during the snapshot failure, here's a fresh 
log:

2014-01-02 17:38:40,028 INFO  [cloud.agent.AgentShell] (main:null) Agent started
2014-01-02 17:38:40,029 INFO  [cloud.agent.AgentShell] (main:null) 
Implementation Version is 4.2.1-SNAPSHOT
2014-01-02 17:38:40,031 INFO  [cloud.agent.AgentShell] (main:null) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2014-01-02 17:38:40,033 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to using properties file for storage
2014-01-02 17:38:40,034 INFO  [cloud.agent.AgentShell] (main:null) Defaulting 
to the constant time backoff algorithm
2014-01-02 17:38:40,038 INFO  [cloud.utils.LogUtils] (main:null) log4j 
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2014-01-02 17:38:40,155 INFO  [cloud.agent.Agent] (main:null) id is 4
2014-01-02 17:38:40,185 INFO  [resource.virtualnetwork.VirtualRoutingResource] 
(main:null) VirtualRoutingResource _scriptDir to use: scripts/network/domr/kvm
2014-01-02 17:38:41,044 INFO  [kvm.resource.LibvirtComputingResource] 
(main:null) No libvirt.vif.driver specified. Defaults to BridgeVifDriver.
2014-01-02 17:38:41,082 INFO  [cloud.agent.Agent] (main:null) Agent [id = 4 : 
type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host = 
172.16.203.68 : port = 8250
2014-01-02 17:38:41,094 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connecting to 172.16.203.68:8250
2014-01-02 17:38:41,294 INFO  [utils.nio.NioClient] (Agent-Selector:null) SSL: 
Handshake done
2014-01-02 17:38:41,294 INFO  [utils.nio.NioClient] (Agent-Selector:null) 
Connected to 172.16.203.68:8250
2014-01-02 17:38:41,521 INFO  [cloud.serializer.GsonHelper] 
(Agent-Handler-1:null) Default Builder inited.
2014-01-02 17:38:41,616 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
Proccess agent startup answer, agent id = 0
2014-01-02 17:38:41,616 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) Set 
agent id 0
2014-01-02 17:38:41,623 INFO  [cloud.agent.Agent] (Agent-Handler-2:null) 
Startup Response Received: agent id = 0
2014-01-02 17:38:42,561 INFO  [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Proccess agent ready command, agent id = 4
2014-01-02 17:38:42,562 INFO  [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Set agent id 4
2014-01-02 17:38:42,562 INFO  [cloud.agent.Agent] (agentRequest-Handler-1:null) 
Ready command is processed: agent id = 4
2014-01-02 17:38:42,693 INFO  [cloud.agent.Agent] (agentRequest-Handler-2:null) 
Proccess agent ready command, agent id = 4
2014-01-02 17:38:42,693 INFO  [cloud.agent.Agent] (agentRequest-Handler-2:null) 
Set agent id 4
2014-01-02 17:38:42,694 INFO  [cloud.agent.Agent] (agentRequest-Handler-2:null) 
Ready command is processed: agent id = 4


And here's some more files:

tail -f cloudstack-agent.err cloudstack-agent.out
==> cloudstack-agent.err <==
log4j:WARN No appenders could be found for logger 
(org.apache.commons.httpclient.params.DefaultHttpParams).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.

==> cloudstack-agent.out <==
2014-01-02 17:48:36,812{GMT} INFO  [cloud.agent.AgentShell] (main:) Agent 
started
2014-01-02 17:48:36,814{GMT} INFO  [cloud.agent.AgentShell] (main:) 
Implementation Version is 4.2.1-SNAPSHOT
2014-01-02 17:48:36,816{GMT} INFO  [cloud.agent.AgentShell] (main:) 
agent.properties found at /etc/cloudstack/agent/agent.properties
2014-01-02 17:48:36,818{GMT} INFO  [cloud.agent.AgentShell] (main:) Defaulting 
to using properties file for storage
2014-01-02 17:48:36,819{GMT} INFO  [cloud.agent.AgentShell] (main:) Defaulting 
to the constant time backoff algorithm
2014-01-02 17:48:36,823{GMT} INFO  [cloud.utils.LogUtils] (main:) log4j 
configuration found at /etc/cloudstack/agent/log4j-cloud.xml
2014-01-02 17:48:36,937{GMT} INFO  [cloud.agent.Agent] (main:) id is 4
2014-01-02 17:48:36,967{GMT} INFO  
[resource.virtualnetwork.VirtualRoutingResource] (main:) VirtualRoutingResource 
_scriptDir to use: scripts/network/domr/kvm
2014-01-02 17:48:37,822{GMT} INFO  [kvm.resource.LibvirtComputingResource] 
(main:) No libvirt.vif.driver specified. Defaults to BridgeVifDriver.
2014-01-02 17:48:37,859{GMT} INFO  [cloud.agent.Agent] (main:) Agent [id = 4 : 
type = LibvirtComputingResource : zone = 1 : pod = 1 : workers = 5 : host = 
172.16.203.68 : port = 8250
2014-01-02 17:48:37,871{GMT} INFO  [utils.nio.NioClient] (Agent-Selector:) 
Connecting to 172.16.203.68:8250
2014-01-02 17:48:38,069{GMT} INFO  [utils.nio.NioClient] (Agent-Selector:) SSL: 
Handshake done
2014-01-02 17:48:38,070{GMT} INFO  [utils.nio.NioClient] (Agent-Selector:) 
Connected to 172.16.203.68:8250
2014-01-02 17:48:38,2

[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Wei Zhou (JIRA)

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

Wei Zhou commented on CLOUDSTACK-5709:
--

you can get more information if you change the debug level from INFO to DEBUG 
in log4j-cloud.xml

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

I've changed INFO to DEBUG in this section:


  
  

Let me know if it's not the right place. I'm not familiar at all with java 
stuff. 
It has not changed anything in the verbosity of the logs, I get the same (lack 
of) info.

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Wei Zhou (JIRA)

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

Wei Zhou commented on CLOUDSTACK-5709:
--

try this:

sed -i 's/INFO/DEBUG/g' /etc/cloud/agent/log4j-cloud.xml


> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

Much better, cheers:
http://tmp.nux.ro/jyT-5709/

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Wei Zhou (JIRA)

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

Wei Zhou commented on CLOUDSTACK-5709:
--

Can you run the following command on host to see what will happen?

2014-01-02 19:01:38,488 DEBUG [kvm.storage.KVMStorageProcessor] 
(agentRequest-Handler-4:null) Executing: 
/usr/share/cloudstack-common/scripts/storage/qcow2/managesnapshot.sh -b 
/mnt/1ffa7f05-a7d8-3f0c-be6b-cb05a2e005b0/9640402c-f11c-44ac-81fc-0680f94c9251 
-n 675c6b76-0821-46fc-be28-7956dcee6946 -p 
/mnt/4ee97827-2a63-338a-928c-b57249ba76fc/snapshots/2/10 -t 
675c6b76-0821-46fc-be28-7956dcee6946 

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

Sure:

/usr/share/cloudstack-common/scripts/storage/qcow2/managesnapshot.sh -b 
/mnt/1ffa7f05-a7d8-3f0c-be6b-cb05a2e005b0/9640402c-f11c-44ac-81fc-0680f94c9251 
-n 675c6b76-0821-46fc-be28-7956dcee6946 -p 
/mnt/4ee97827-2a63-338a-928c-b57249ba76fc/snapshots/2/10 -t 
675c6b76-0821-46fc-be28-7956dcee6946 
Failed to backup 675c6b76-0821-46fc-be28-7956dcee6946 for disk 
/mnt/1ffa7f05-a7d8-3f0c-be6b-cb05a2e005b0/9640402c-f11c-44ac-81fc-0680f94c9251 
to /mnt/4ee97827-2a63-338a-928c-b57249ba76fc/snapshots/2/10

/mnt/4ee97827-2a63-338a-928c-b57249ba76fc/snapshots/2/10 exists as a path, but 
it there is nothing mounted there ...



> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Wei Zhou (JIRA)

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

Wei Zhou commented on CLOUDSTACK-5709:
--

What happen if you run "qemu-img convert -f qcow2 -O qcow2 -s 
675c6b76-0821-46fc-be28-7956dcee6946 
/mnt/1ffa7f05-a7d8-3f0c-be6b-cb05a2e005b0/9640402c-f11c-44ac-81fc-0680f94c9251 
/mnt/4ee97827-2a63-338a-928c-b57249ba76fc/snapshots/2/10/675c6b76-0821-46fc-be28-7956dcee6946"?

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-02 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

It errors out with:
convert: invalid option -- 's'

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-03 Thread Wei Zhou (JIRA)

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

Wei Zhou commented on CLOUDSTACK-5709:
--

It looks -s is not valid in redhat 6.
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/sect-Virtualization-Tips_and_tricks-Using_qemu_img.html

It is valid in Ubuntu 12.04 and later
http://manpages.ubuntu.com/manpages/precise/man1/qemu-img.1.html

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-03 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

Right, finally I get it. EL6 KVM does not support this feature. Thanks a lot 
Wei for guiding me!

I found that using the KVM from RedHat's RHEV repo[1] fixes the problem. This 
can be done as a temporary workaround until EL6 backports this feature (if 
ever) or EL7 is launched whose KVM should not have these problems.

I found that using these RPMs[2] the problems go away and I can snapshot 
volumes, turn them into templates, launch templates and so on.


[1] - http://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHEV/SRPMS/
[2] - http://li.nux.ro/download/nux/tmp/kvm-rhev/el6/

> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>Assignee: edison su
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-03 Thread Nux (JIRA)

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

Nux commented on CLOUDSTACK-5709:
-

BTW, using this version of KVM one can perform VM snapshots perfectly, too ie 
virsh snapshot-create-as i-2-15-VM snapshot "snapshot description" --atomic 
(this snapshotts disk AND memory)
virsh snapshot-revert i-2-15-VM snapshot --force



> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>Assignee: edison su
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)


[jira] [Commented] (CLOUDSTACK-5709) Snapshots fail on ACS 4.2.1 SNAPSHOT

2014-01-03 Thread Sudha Ponnaganti (JIRA)

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

Sudha Ponnaganti commented on CLOUDSTACK-5709:
--

Closing this as Nux has confirmed that it is working fine with revised version 
of KVM

-Original Message-
From: Nux! [mailto:n...@li.nux.ro] 
Sent: Friday, January 03, 2014 12:33 AM
To: d...@cloudstack.apache.org
Subject: RE: [VOTE] 3rd round of voting for ASF 4.2.1 RC

On 03.01.2014 07:40, Nux! wrote:
> Guys, this is really confusing!
> First of all I could swear I had this feature working on me previously 
> on a similar setup, second of all why has your colleague Sadhu said 
> this is working[1]?
> Also Andrei Mikhailovsky claims in this same thread the feature is 
> working, though he is facing other issues (launching new VMs from 
> volume backups/snapshots).

Ok, I think I got it. For EL6 (CentOS6) users the workaround is to use a 
patched version of KVM, then all the features start working (btw "VM snapshots" 
could work as well with this!).
The confusion comes from the fact the issue is not present in Ubuntu latest for 
example since they package a newer kvm, so this differs from one distro to 
another.

With the version from RHEV everything worked great and I'll test this soon with 
GlusterFS shared mount point as well.

More here
https://issues.apache.org/jira/browse/CLOUDSTACK-5709?focusedCommentId=13861329&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13861329

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro




> Snapshots fail on ACS 4.2.1 SNAPSHOT
> 
>
> Key: CLOUDSTACK-5709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5709
> Project: CloudStack
>  Issue Type: Bug
>  Security Level: Public(Anyone can view this level - this is the 
> default.) 
>  Components: KVM, Snapshot
>Affects Versions: 4.2.1
> Environment: CentOS 6.5 HV, NFS primary & secondary storage
>Reporter: Nux
>Assignee: edison su
>  Labels: fail, kvm, snapshot
> Fix For: 4.2.1
>
>
> Snapshots fail and get stuck in "Created on primary".
> Logs with Basic Zone install (after the runbook):
> http://tmp.nux.ro/t9P-snapfail.txt
> Logs with the same problem but with Adv zone and Shared Mount Point 
> (glusterfs) as primary storage:
> http://tmp.nux.ro/T94-ACSgluster.txt
> AFAIK this is a 4.2.1 release blocker.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)