Re: [vdsm] Q on 'git push' to vdsm gerrit
On 09/23/2012 11:59 PM, Alon Bar-Lev wrote: Try to branch and re-push, remove your own commits from master so you won't have future problems. I am not following here. Can you elaborate pls ? I am not a gerrit expert, so may be I am missing something. FYI - I am not doing git push from vdsm master branch, in my local git repo, I have a different branch and pushing my patches to gerrit from that branch, did you mean this ? thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Q on 'git push' to vdsm gerrit
- Original Message - From: Deepak C Shetty deepa...@linux.vnet.ibm.com To: Alon Bar-Lev alo...@redhat.com Cc: VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Monday, September 24, 2012 12:19:19 PM Subject: Re: [vdsm] Q on 'git push' to vdsm gerrit On 09/23/2012 11:59 PM, Alon Bar-Lev wrote: Try to branch and re-push, remove your own commits from master so you won't have future problems. I am not following here. Can you elaborate pls ? I am not a gerrit expert, so may be I am missing something. FYI - I am not doing git push from vdsm master branch, in my local git repo, I have a different branch and pushing my patches to gerrit from that branch, did you mean this ? thanx, deepak So that's is fine. If you push the branch again what message do you get? Alon. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] Q on 'git push' to vdsm gerrit
On 09/24/2012 03:54 PM, Alon Bar-Lev wrote: - Original Message - From: Deepak C Shetty deepa...@linux.vnet.ibm.com To: Alon Bar-Lev alo...@redhat.com Cc: VDSM Project Development vdsm-devel@lists.fedorahosted.org Sent: Monday, September 24, 2012 12:19:19 PM Subject: Re: [vdsm] Q on 'git push' to vdsm gerrit On 09/23/2012 11:59 PM, Alon Bar-Lev wrote: Try to branch and re-push, remove your own commits from master so you won't have future problems. I am not following here. Can you elaborate pls ? I am not a gerrit expert, so may be I am missing something. FYI - I am not doing git push from vdsm master branch, in my local git repo, I have a different branch and pushing my patches to gerrit from that branch, did you mean this ? thanx, deepak So that's is fine. If you push the branch again what message do you get? Will try let you know, working on the next version of patchset. In the meanwhile, I wanted to understand what the issue was behind me getting the error, hence had sent out this mail :) thanx, deepak ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] how engine get files from node？
On 09/21/2012 08:14 PM, Laszlo Hornyak wrote: - Original Message - From: Sheldon shao...@linux.vnet.ibm.com To: vdsm-devel@lists.fedorahosted.org Sent: Friday, September 21, 2012 11:42:05 AM Subject: [vdsm] how engine get files from node？ Hi all, I have submitted a patch about watchdog device http://gerrit.ovirt.org/#/c/7535/ If we set 'dump' action for watchdog, qemu will generate a dump file. And I have get some feedback, how engine get these files? When adding the host (if installation is enabled) the engine does some ssh/scp to the new host, but this can be turned off. Also, the guideline is to have a single interface with the host, and after installation the engine does not try to communicate with vdsm in any other way than the xmlrpc interface. do you means ssh/scp may not be available on host, So a xmlrpc interface should be added to get the files on host? scp? or Will vdsm support new API to list and get these files? IMO, The new API should list and get not only dump files, but also other kinds of files. -- Sheldon Feng shao...@linux.vnet.ibm.com IBM Linux Technology Center ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel -- Sheldon Feng(冯少合)shao...@linux.vnet.ibm.com IBM Linux Technology Center ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] sanlock issues
- Original Message - From: Saggi Mizrahi smizr...@redhat.com To: vdsm-devel vdsm-de...@fedorahosted.org Cc: ybronhei ybron...@redhat.com, Federico Simoncelli fsimo...@redhat.com, Barak Azulay bazu...@redhat.com Sent: Sunday, September 23, 2012 1:17:01 PM Subject: sanlock issues If you are trying to run sanlock on fedora and you get this error: Sep 23 11:26:56 dhcp-XX-XX.tlv.redhat.com sanlock[7083]: 2012-09-23 11:26:56+0200 37014 [7083]: wdmd connect failed for watchdog handling You need to do this: # unload softdog if it's running rmmod softdog # Check if there are residual watchdog files under /dev and remove them rm /dev/watchdog* # reload the softdog module modprobe softdog # make sure the file is named /dev/watchdog mv /dev/watchdog? /dev/watchdog # set the proper selinux context restorecon /dev/watchdog # restart wdmd systemctl restart wdmd.service # restart sanlock systemctl restart sanlock.service # Profit! fortune There are several things involved here. Were multiple watchdog modules loaded? Why? Is the hardware watchdog loaded after sanlock (which itself loads the softdog)? Is sanlock loading the softdog even if there in an hardware watchdog present? It might also be an udev issue with the device naming. You shouldn't need to relabel the device (another udev issue?). I doubt that this workaround would survive a reboot (did you check?) BTW. fedora 17 or 18? -- Federico ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] sanlock issues
* Saggi Mizrahi smizr...@redhat.com [2012-09-23 06:17]: If you are trying to run sanlock on fedora and you get this error: Sep 23 11:26:56 dhcp-XX-XX.tlv.redhat.com sanlock[7083]: 2012-09-23 11:26:56+0200 37014 [7083]: wdmd connect failed for watchdog handling You need to do this: # unload softdog if it's running rmmod softdog # Check if there are residual watchdog files under /dev and remove them I'd be interested in seeing a file listing: ls -al /dev/watchdog* and comparing that to what you have after you do all of the cleanup below. I know the major change from F16 and f17 w.r.t /dev/ is that f17 kernels are using udevtmpfs which is responsible only for creation of files in /dev; it punts the acls and permissions to udev and systemd. In f16, udev ( release 182) would force the creation of nodes in /dev which helped if the wrong misc device was created by other programs or scripts. Now, with udevtmpfs, if a file is already present in /dev, udevtmpfs won't update/change the file. rm /dev/watchdog* # reload the softdog module modprobe softdog # make sure the file is named /dev/watchdog mv /dev/watchdog? /dev/watchdog # set the proper selinux context restorecon /dev/watchdog # restart wdmd systemctl restart wdmd.service # restart sanlock systemctl restart sanlock.service # Profit! fortune ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ry...@us.ibm.com ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
