On Jan 6, 2014, at 17:41 , Itamar Heim wrote:
> On 01/06/2014 12:29 AM, Roy Golan wrote:
>> On Mon 06 Jan 2014 12:24:53 AM IST, Roy Golan wrote:
>>> On Fri 03 Jan 2014 04:20:19 PM IST, Michal Skrivanek wrote:
On 3 Jan 2014, at 15:04, Itamar Heim wrote:
> On 01/03/2014 12:22
On 01/06/2014 12:29 AM, Roy Golan wrote:
On Mon 06 Jan 2014 12:24:53 AM IST, Roy Golan wrote:
On Fri 03 Jan 2014 04:20:19 PM IST, Michal Skrivanek wrote:
On 3 Jan 2014, at 15:04, Itamar Heim wrote:
On 01/03/2014 12:22 PM, Sven Kieske wrote:
Hi,
I'm a little surprised by this development te
On Mon 06 Jan 2014 12:24:53 AM IST, Roy Golan wrote:
On Fri 03 Jan 2014 04:20:19 PM IST, Michal Skrivanek wrote:
On 3 Jan 2014, at 15:04, Itamar Heim wrote:
On 01/03/2014 12:22 PM, Sven Kieske wrote:
Hi,
I'm a little surprised by this development technique.
its not a development technique
On Fri 03 Jan 2014 04:20:19 PM IST, Michal Skrivanek wrote:
On 3 Jan 2014, at 15:04, Itamar Heim wrote:
On 01/03/2014 12:22 PM, Sven Kieske wrote:
Hi,
I'm a little surprised by this development technique.
its not a development technique. its a bug in upgrade or export/import of the
change
On 3 Jan 2014, at 15:04, Itamar Heim wrote:
> On 01/03/2014 12:22 PM, Sven Kieske wrote:
>> Hi,
>>
>> I'm a little surprised by this development technique.
>
> its not a development technique. its a bug in upgrade or export/import of the
> change to the much more powerful config file based OsI
On 01/03/2014 12:22 PM, Sven Kieske wrote:
Hi,
I'm a little surprised by this development technique.
its not a development technique. its a bug in upgrade or export/import
of the change to the much more powerful config file based OsInfo
implementation in 3.3.
though i thought we already fix
Hi,
I'm a little surprised by this development technique.
In my world, when you change data formats in a not compatible way
you should also write some sort of transition code to
convert the old data to the new data format for all possible
cases.
And if this is not possible for some reason, at le
On 02.01.2014 20:12, Dan Ferris wrote:> Hi,
>
> Has anyone run across this error:
>
> Cannot run VM. Invalid time zone for given OS type.
>
> The OS type for these VMs is set to Linux Other. They were all exported
> from an Ovirt 3.2 cluster and are being reimported into an Ovirt 3.3
> cluster. N
On 2 Jan 2014, at 20:12, Dan Ferris wrote:
> Hi,
>
> Has anyone run across this error:
>
> Cannot run VM. Invalid time zone for given OS type.
>
> The OS type for these VMs is set to Linux Other.
What was the original TZ in 3.2?
> They were all exported
> from an Ovirt 3.2 cluster and are
9 matches
Mail list logo