[ovirt-devel] [URGENT][ACTION REQUIRED] vdsm-jsonrpc-java is not building on el6 and fc20
Hi, vdsm-jsonrpc-java is not building on el6 and fc20. See: - http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_create-rpms-el6-x86_64_merged/ - http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_create-rpms-fc20-x86_64_merged/ Please fix it as soon as possible, thanks. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm-jsonrpc-java is not building on el6 and fc20
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: devel@ovirt.org, infra in...@ovirt.org Sent: Tuesday, August 19, 2014 10:34:56 AM Subject: [ovirt-devel] [URGENT][ACTION REQUIRED] vdsm-jsonrpc-java is not building on el6 and fc20 Hi, vdsm-jsonrpc-java is not building on el6 and fc20. See: - http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_create-rpms-el6-x86_64_merged/ - http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_master_create-rpms-fc20-x86_64_merged/ Please fix it as soon as possible, thanks. Saggi is aware of this. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [oVirt 3.5 Localization Question #9] ${type} must contain at least one mac range.
Hello,
I would like to check if my interpretation is correct with the following
string which was just pushed today.
*File: *
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/AppErrors
*Resource ID:* ACTION_TYPE_FAILED_MAC_POOL_MUST_HAVE_RANGE
*String: *Cannot ${action} ${type}. ${type} must contain at least one
mac range.
*Question: *Is one mac range referring to one MAC address range?
Thank you,
Yuko
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [oVirt 3.5 Localization Question #11] Skip fencing if host has live lease on storage
Hello, I have another question: *File: * frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/org.ovirt.engine.ui.webadmin.ApplicationConstants *Resource ID:* skipFencingIfSDActive *String: *Skip fencing if host has live lease on storage *Question: *Could anyone please explain to me what live lease is and how it is related to storage? Thank you, Yuko ** ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [oVirt 3.5 Localization Question #11] Skip fencing if host has live lease on storage
On 08/19/2014 06:58 PM, Oved Ourfali wrote: - Original Message - From: Yuko Katabami ykata...@redhat.com To: devel@ovirt.org Sent: Tuesday, August 19, 2014 11:51:00 AM Subject: [ovirt-devel] [oVirt 3.5 Localization Question #11] Skip fencing if host has live lease on storage Hello, I have another question: File: frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/org.ovirt.engine.ui.webadmin.ApplicationConstants Resource ID: skipFencingIfSDActive String: Skip fencing if host has live lease on storage Question: Could anyone please explain to me what live lease is and how it is related to storage? It means that the host is actively accessing the storage. I'd say that it could have been rephrased to: Skip fencing if host has storage connectivity However, the info icon in this dialog provides additional information, which also contains the term live lease. Hi Oved, Thank you for your explanation. I understand it now. I will keep the term live lease for consistency. Kind regards, Yuko Thank you, Yuko ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [Q] VM ticket: how to set infinity expire time
Hi, I didn't find a way how to set infinity expire time. Which value I have to pass to set_expiry()? Thanks! ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [oVirt 3.5 Localization Question #12] Error message that are enclosed in double quotation marks
Hello again,
Sorry for increasing your mail traffic, this is my last question for today.
There are error messages starting with Cannot ${action} ${type}, and
entire message is enclosed in a set of double quotation marks:
Cannot ${action} ${type}. The specified disk snapshots don't belong to
the same Disk.
Cannot ${action} ${type}. SCSI Generic IO is not supported for image disk.
Cannot ${action} ${type}. SCSI device pass-throguh is not supported for
a read-only disk.
(also found typos in pass-throguh = pass-through)
Other similar error messages are not enclosed in double quotation marks.
Are the quotation marks there for separating the message from other text?
Should we keep those quotation marks (or equivalent symbols for each
language) in our translation?
Kind regards,
Yuko
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] vdsClient desktopLogoff bug
On 08/19/2014 11:35 AM, Denis Kirjanov wrote: - Исходное сообщение - От: Vinzenz Feenstra vfeen...@redhat.com Кому: Dan Kenigsberg dan...@redhat.com, Denis Kirjanov k...@itsirius.su Копия: devel@ovirt.org Отправленные: Вторник, 19 Август 2014 г 10:08:48 Тема: Re: [ovirt-devel] vdsClient desktopLogoff bug On 08/18/2014 06:17 PM, Dan Kenigsberg wrote: On Mon, Aug 18, 2014 at 05:48:45PM +0400, Denis Kirjanov wrote: sendkeys would work (ctrl alt backspace), but it's not implemented in my version( (vdsm-cli-0:4.10.2-22.0.el6.noarch) - Исходное сообщение - От: Denis Kirjanov k...@itsirius.su Кому: devel@ovirt.org Отправленные: Понедельник, 18 Август 2014 г 16:07:58 Тема: [ovirt-devel] vdsClient desktopLogoff bug Hi, I'm using RHEV 3.1.0-53. I can successfully invoke the desktopLock command, but the desktopLogoff command returns Virtual machine does not exist. Command looks like the following one: vdsClient -s --truststore path host desktopLogoff true VMID Could you show the relevant parts of vdsm.log for both commands? Desktop Logoff is currently a noop in the guest agent. It'll be implemented sometime later. Ok, I see. Thanks. I'm asking this question since I want to avoid the gdm lock screen window: 1) On a specific event I do the lock screen command to vm 2) I do the logout from the host system 3) I do the login on the host system .The process sets up the vm ticket, queries the ports from the VM manager and _performs the desktopLogin_! 4) Spice session takes place. Here I do expect to see the VM destop, not the lock screen window. I've found that the SSO in the previous scenario works if I do the logout from the VM manually. We basically have RFE's for both the cases. That we should allow not to lock the screen on disconnect and that we have a logout. Both features should be implemented with ovirt 3.6 HTH -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [ACTION REQUIRED] Fedora 19 on master has broken dependencies
Il 19/08/2014 13:08, Dan Kenigsberg ha scritto: On Mon, Aug 18, 2014 at 03:15:21PM +0200, Sandro Bonazzola wrote: Hi, looks like a patch have been merged causing repository closure breakage for VDSM on Fedora 19: Yes, we are talking about sparsify: integrating virt-sparsify into vdsm package: vdsm-4.16.0-204.gitbf3d2b5.fc19.x86_64 from check-custom-fc19 unresolved deps: libguestfs-tools-c = 1:1.26.7-2 package: vdsm-4.16.0-206.gitdd70c9e.fc19.x86_64 from check-custom-fc19 unresolved deps: libguestfs-tools-c = 1:1.26.7-2 Since master is now targeted to oVirt 3.6.0 it may be a good point for deciding if we're going to keep support for Fedora 19 or not for the upcoming oVirt 3.6.0 planning. For reference, Fedora 21 is expected to be released on 2014-11-11 [1], this means Fedora 19 is expected to go End Of Life on 2014-12-11 (one month later F21 release)[2]. I suggest to start provisioning some slaves with Fedora 21 and move master jobs currently running on F19 to F21. Yes, please. The master branch was conciously broken on Fedora 19 (and el6.5) since we want this new features on master. el6.6 is going to have virt-sparsify, but f19 would not. So please, let us start deprecating f19 slaves. ovirt-3.6 won't support it as a valid platform. In order to drop Fedora 19 from master, the following projects need to be branched for 3.5.z: - vdsm-jsonrpc-java - ovirt-reports - ovirt-dwh The following projects may probably not need to be branched but please take a look: - ioprocess - unboundid-ldapsdk I guess we can wait until 3.5.0 will be released before start changing. [1] http://fedoraproject.org/wiki/Releases/21/Schedule [2] https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Infra mailing list in...@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [oVirt 3.5 Localization Question #12] Error message that are enclosed in double quotation marks
- Original Message -
From: Yuko Katabami ykata...@redhat.com
To: devel@ovirt.org
Sent: Tuesday, August 19, 2014 12:18:59 PM
Subject: [ovirt-devel] [oVirt 3.5 Localization Question #12] Error message
that are enclosed in double quotation
marks
Hello again,
Sorry for increasing your mail traffic, this is my last question for today.
There are error messages starting with Cannot ${action} ${type}, and entire
message is enclosed in a set of double quotation marks:
Cannot ${action} ${type}. The specified disk snapshots don't belong to the
same Disk.
Cannot ${action} ${type}. SCSI Generic IO is not supported for image disk.
Cannot ${action} ${type}. SCSI device pass-throguh is not supported for a
read-only disk.
(also found typos in pass-throguh = pass-through)
Other similar error messages are not enclosed in double quotation marks.
Are the quotation marks there for separating the message from other text?
Should we keep those quotation marks (or equivalent symbols for each
language) in our translation?
Hi Yuko
Those quotation marks are redundant and should be removed
Can you please open a BZ describing this plus the typos and send me its BZ ID
I will handle that
Thanks
Eli
Kind regards,
Yuko
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] build RPM error:
Hi: When I build the RPM use “make rpm”, I got the error: error: line 170: Illegal char '$' in: Version: $majorminor.$fix_release ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] [re-posting] [oVirt 3.5 Localization Question #9] ${type} must contain at least one mac range.
I am re-posting this as I could not get any response yesterday, and our
deadline for translation is this Friday.
It would be greatly appreciated if anyone can answer this question.
Thanks in advance,
Yuko
On 08/19/2014 05:43 PM, Yuko Katabami wrote:
Hello,
I would like to check if my interpretation is correct with the
following string which was just pushed today.
*File: *
frontend/webadmin/modules/webadmin/src/main/resources/org/ovirt/engine/ui/frontend/AppErrors
*Resource ID:* ACTION_TYPE_FAILED_MAC_POOL_MUST_HAVE_RANGE
*String: *Cannot ${action} ${type}. ${type} must contain at least one
mac range.
*Question: *Is one mac range referring to one MAC address range?
Thank you,
Yuko
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
