[ovirt-devel] Re: Ovirt: Upload Disk Snapshots problems with iSCSI storage and Java SDK

2019-05-12 Thread Nir Soffer 
On Thu, May 9, 2019 at 11:46 AM  wrote:

> Hello Nir,
> thanks for your response,
> How ever, I already put initial size when I create the disk.


The disk is just the base volume...

I show the values than the disk contains before create:
> Disk: {
> Name:T_iSCSI_Thin_Disk1_restore,
> Id:null,
> Interface:VIRTIO_SCSI,
> Format:COW,
> WipeAfterDelete: false,
> Shareable: false,
> Sparse: true,
> Boot:true,
> Active:true,
> Sizes:{
>   Initial:4294967296,
>   Actual:null,
>   Total:null,
>   Provisioned: 4294967296
>   }
> }
> After I created the disk(WIth initial Size and provisioned Size,
> previously showed). I create the snapshots, and these snapshot's images are
> created with an actual size with 1Gb(I don't known how I can put an actual
> size to these images). So, I think the problem isn't when I create the
> disk, else it maybe when I create the snapshot-chain.
>

Every layer in the snapshot chain is another disk, and there you can
specify the initial size.

Copying from:
https://github.com/oVirt/ovirt-engine-sdk/blob/master/sdk/examples/upload_disk_snapshots.py

# Add the new snapshot:
snapshot = snapshots_service.add(
types.Snapshot(
description=description,
disk_attachments=[
types.DiskAttachment(
disk=types.Disk(
id=disk_id,
image_id=image_id

# sizes for every snapshot should work here

)
)
]
),
)


>
>
> I don't have a problems when I upload the first image(with size 2Gb) of
> disk than is the "base" of snapshot-chain, else I have a problem when I
> upload a disk Snapshot(other image of snapshot-chain) bigger than 1Gb.
>
> How ever, the same process with NFS storages works correctly.
>

Because on NFS there is no need to allocate storage, the file system does
this for you.
But with block storage you must specify the initial size of the disk.

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EPZWN637XG6EBXHNKOSSNO3SXJHZGI4B/

[ovirt-devel] Re: Build artifacts failed - not enough free space on file system

2019-05-12 Thread Nir Soffer 
On Sun, May 12, 2019 at 8:00 PM Eyal Edri  wrote:

> You s390x build is failing, its the only VM we have.
> I cleaned up the space there. it should work now.
>

It works now:
http://jenkins.ovirt.org/job/standard-manual-runner/250/

I think we had issues with the s390x slave in the past.

I guess this will bite us again in 2-3 months.


>
> On Sun, May 12, 2019 at 6:44 PM Nir Soffer  wrote:
>
>> On Sun, May 12, 2019 at 6:32 PM Nir Soffer  wrote:
>>
>>> On Sun, May 12, 2019 at 6:20 PM Nir Soffer  wrote:
>>>
 I had this failure in yum install:

 [2019-05-12T14:54:55.706Z] Error Summary
 [2019-05-12T14:54:55.706Z] -
 [2019-05-12T14:54:55.706Z] Disk Requirements:
 [2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
 filesystem.

 Build:

 https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline

 Trying build again, hopefully will get a slave with more space...

>>>
>>> Unfortunately, I got the same slave again:
>>>
>>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/248/pipeline
>>>
>>
>> Another failure:
>> https://jenkins.ovirt.org/job/standard-manual-runner/249/
>>
>>
>>>
>>> This blocks urgent bug:
>>> https://bugzilla.redhat.com/1700623
>>>
>>> Nir
>>>
>>>
>>>

 Nir

>>>
>
> --
>
> Eyal edri
>
>
> MANAGER
>
> CONTINUOUS PRODUCTIZATION
>
> SYSTEM ENGINEERING
>
> Red Hat 
> 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JEO6NQQ3RQZXK34PODJ2EWUWQKBYKP2N/

[ovirt-devel] Re: Build artifacts failed - not enough free space on file system

2019-05-12 Thread Eyal Edri 
You s390x build is failing, its the only VM we have.
I cleaned up the space there. it should work now.

On Sun, May 12, 2019 at 6:44 PM Nir Soffer  wrote:

> On Sun, May 12, 2019 at 6:32 PM Nir Soffer  wrote:
>
>> On Sun, May 12, 2019 at 6:20 PM Nir Soffer  wrote:
>>
>>> I had this failure in yum install:
>>>
>>> [2019-05-12T14:54:55.706Z] Error Summary
>>> [2019-05-12T14:54:55.706Z] -
>>> [2019-05-12T14:54:55.706Z] Disk Requirements:
>>> [2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
>>> filesystem.
>>>
>>> Build:
>>>
>>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline
>>>
>>> Trying build again, hopefully will get a slave with more space...
>>>
>>
>> Unfortunately, I got the same slave again:
>>
>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/248/pipeline
>>
>
> Another failure:
> https://jenkins.ovirt.org/job/standard-manual-runner/249/
>
>
>>
>> This blocks urgent bug:
>> https://bugzilla.redhat.com/1700623
>>
>> Nir
>>
>>
>>
>>>
>>> Nir
>>>
>>

-- 

Eyal edri


MANAGER

CONTINUOUS PRODUCTIZATION

SYSTEM ENGINEERING

Red Hat 

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/DOY7XJZF7EH2F3RMMBEAVJK775ZQAZOW/

[ovirt-devel] Re: Build artifacts failed - not enough free space on file system

2019-05-12 Thread Nir Soffer 
On Sun, May 12, 2019 at 6:32 PM Nir Soffer  wrote:

> On Sun, May 12, 2019 at 6:20 PM Nir Soffer  wrote:
>
>> I had this failure in yum install:
>>
>> [2019-05-12T14:54:55.706Z] Error Summary
>> [2019-05-12T14:54:55.706Z] -
>> [2019-05-12T14:54:55.706Z] Disk Requirements:
>> [2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
>> filesystem.
>>
>> Build:
>>
>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline
>>
>> Trying build again, hopefully will get a slave with more space...
>>
>
> Unfortunately, I got the same slave again:
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/248/pipeline
>

Another failure:
https://jenkins.ovirt.org/job/standard-manual-runner/249/


>
> This blocks urgent bug:
> https://bugzilla.redhat.com/1700623
>
> Nir
>
>
>
>>
>> Nir
>>
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/6QOOFU3T5A3MJ4KFKHVIVWXN364NRBP3/

[ovirt-devel] Re: Build artifacts failed - not enough free space on file system

2019-05-12 Thread Nir Soffer 
On Sun, May 12, 2019 at 6:20 PM Nir Soffer  wrote:

> I had this failure in yum install:
>
> [2019-05-12T14:54:55.706Z] Error Summary
> [2019-05-12T14:54:55.706Z] -
> [2019-05-12T14:54:55.706Z] Disk Requirements:
> [2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
> filesystem.
>
> Build:
>
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline
>
> Trying build again, hopefully will get a slave with more space...
>

Unfortunately, I got the same slave again:
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/248/pipeline

This blocks urgent bug:
https://bugzilla.redhat.com/1700623

Nir



>
> Nir
>
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/LOVTBBAIYIFSVCD6ZQOWBBEMVVTVUF6F/

[ovirt-devel] Build artifacts failed - not enough free space on file system

2019-05-12 Thread Nir Soffer 
I had this failure in yum install:

[2019-05-12T14:54:55.706Z] Error Summary
[2019-05-12T14:54:55.706Z] -
[2019-05-12T14:54:55.706Z] Disk Requirements:
[2019-05-12T14:54:55.706Z]At least 70MB more space needed on the /
filesystem.

Build:
https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runner/detail/standard-manual-runner/247/pipeline

Trying build again, hopefully will get a slave with more space...

Nir
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/L23JNC4GTNBZDOUTYYC3L53PGSZJ42P4/

[ovirt-devel] manipulating VM configuration via Python SDK disables serial console

2019-05-12 Thread Denis Karpov 
Hello,

I have hit what seems to be a bug in oVIrt Python SDK, when deploying
OpenStack 14 (Rocky) in configuration virtualized controllers, oVirt VMs;
Ironic oVirt driver is used in this case, which uses oVirt Python SDK to
talk to manipulate VMs.

The driver seem to work in such a way that at certain stages it retrieves a
VM configuration and updates it (e.g. changes the boot device). However
during such  update some other changes in configuration of the VM happen:
e.g. if the VM had VirtIO serial console enabled, after the update that
serial console becomes disabled. Perhaps when a VMs config is updated some
XML fields of its configuration are not written back as they should be?

We have noticed that since the OpenStack deployment fails on controllers if
it cannot output to the serial console.
I would appreciate any help/workaround for this issue.

Thanks, Denis
___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/3KCSDMLE2TYCO4KFCOAWAHPGHEJWVCEI/

[ovirt-devel] Re: [CQ]: 99533,1 (ovirt-vmconsole) failed "ovirt-4.2" system tests

2019-05-12 Thread Galit Rosenthal 
Hi Eyal,

Image created.
Need now to Update OST with new image.

Regards,
Galit

On Sun, May 12, 2019 at 8:29 AM Eyal Edri  wrote:

> OK,
> Can we do the same today?
> I assume CentOS issued a new Image by now that we can use.
>
> On Sun, May 12, 2019 at 8:23 AM Galit Rosenthal 
> wrote:
>
>> Eyal,
>>
>> We had the same issue in February 2019
>> Then, we've created a new updated image.
>>
>> this is a bug that was opened related to this issue, but it was closed.
>> https://bugzilla.redhat.com/show_bug.cgi?id=1518599#c9
>>
>>
>> Regards,
>> Galit
>>
>> On Sat, May 11, 2019 at 4:48 PM Eyal Edri  wrote:
>>
>>> Adding Galit.
>>> Not sure why it requires new image, can you elaborate?
>>>
>>>
>>> On Fri, May 10, 2019, 17:10 Dafna Ron  wrote:
>>>
 we may need new lago images as I think the selinux conf is overwritten
 when we upgrade newer packages.


 http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4323/testReport/junit/(root)/001_upgrade_engine/running_tests___upgrade_from_prevrelease_suite_el7_x86_64___test_initialize_engine/

 On Fri, May 10, 2019 at 2:25 PM oVirt Jenkins 
 wrote:

> Change 99533,1 (ovirt-vmconsole) is probably the reason behind recent
> system
> test failures in the "ovirt-4.2" change queue and needs to be fixed.
>
> This change had been removed from the testing queue. Artifacts build
> from this
> change will not be released until it is fixed.
>
> For further details about the change see:
> https://gerrit.ovirt.org/#/c/99533/1
>
> For failed test results see:
> http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4323/
> ___
> Infra mailing list -- in...@ovirt.org
> To unsubscribe send an email to infra-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
> https://lists.ovirt.org/archives/list/in...@ovirt.org/message/NI7TPHGBKRGWIFH4XHDKA72C74VS4DP7/
>
 ___
 Infra mailing list -- in...@ovirt.org
 To unsubscribe send an email to infra-le...@ovirt.org
 Privacy Statement: https://www.ovirt.org/site/privacy-policy/
 oVirt Code of Conduct:
 https://www.ovirt.org/community/about/community-guidelines/
 List Archives:
 https://lists.ovirt.org/archives/list/in...@ovirt.org/message/VDWLW6XCGNAGQ6NEXIULKKMXESQWCNY5/

>>>
>>
>> --
>>
>> GALIT ROSENTHAL
>>
>> SOFTWARE ENGINEER
>>
>> Red Hat
>>
>> 
>>
>> ga...@redhat.comT: 972-9-7692230
>> 
>>
>
>
> --
>
> Eyal edri
>
>
> MANAGER
>
> CONTINUOUS PRODUCTIZATION
>
> SYSTEM ENGINEERING
>
> Red Hat 
> 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ #cp-devel)
>


-- 

GALIT ROSENTHAL

SOFTWARE ENGINEER

Red Hat



ga...@redhat.comT: 972-9-7692230

___
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CPPLLYZ3RCSJ7H2FX6466CUS6O7YO4VZ/