- Devel - oVirt List Archives

ovirt-engine has been tagged (ovirt-engine-4.2.8.4)
by Tal Nisan 19 Feb '19

19 Feb '19

1 0

Re: Query regarding initial size value given to rest api for creating QCOW2 disk
by Himani Vaidya 19 Feb '19

19 Feb '19

Hi Nir, Daniel And Devel Guys, We have query regarding initial size attribute that we need specify in create disk API for qcow2 format. As per our discussions with you all it came up that we need initial size to be specified at qcow2 disk creation/restore so that that much size is preallocated. Based on that we specify request body for qcow2 to /ovirt-engine/api/disks as follows:- <disk> <storage_domains> <storage_domain id="aaaa"/> </storage_domains> <name>mydisk</name> <provisioned_size>xxxx</provisioned_size> <initial_size>yyyy<initial_size> <format>cow</format> </disk> Consider provisioned_size = 1 GB (Guest offset)(raw thick disk) Initial_size = > 1GB Initial_size > provisioned_size Also as per disk struct specified in http://ovirt.github.io/ovirt-engine-api-model/4.3/#types/disk Initial_size and provisioned size both are different attributes .Therefore these need to specified differently as per above request body. But unfortunately we saw it fails at write offset greater that provisioned size at data restore time. It doesn't consider initial_size attribute specified in request body only considers provisioned size . Can you please confirm whether for COW format what attributes and actual values(consider 1GB example) are needed in request body of create disk API /ovirt-engine/api/disks ? Thanks Himani Vaidya From: Mohammed Eliyas Shaikh Sent: Thursday, January 31, 2019 8:39 PM To: Daniel Erez <derez(a)redhat.com>; Nir Soffer <nsoffer(a)redhat.com> Cc: pchavva(a)redhat.com; Suchitra Herwadkar <Suchitra.Herwadkar(a)veritas.com>; Abhay Marode <Abhay.Marode(a)veritas.com>; DL-VTAS-ENG-NBU-Midas <DL-VTAS-ENG-NBU-Midas(a)veritas.com>; Himani Vaidya <Himani.Vaidya(a)veritas.com> Subject: RE: Query regarding initial size for QCOW2 file restore Hi Pavan, Can we get direct number of Nir / Daniel to check if they are available for a short call now? Thanks, Mohammed Eliyas. From: Mohammed Eliyas Shaikh Sent: Thursday, January 31, 2019 1:39 PM To: Daniel Erez <derez(a)redhat.com<mailto:derez@redhat.com>>; Nir Soffer <nsoffer(a)redhat.com<mailto:nsoffer@redhat.com>> Cc: pchavva(a)redhat.com<mailto:pchavva@redhat.com>; Suchitra Herwadkar <Suchitra.Herwadkar(a)veritas.com<mailto:Suchitra.Herwadkar@veritas.com>>; Abhay Marode <Abhay.Marode(a)veritas.com<mailto:Abhay.Marode@veritas.com>>; DL-VTAS-ENG-NBU-Midas <DL-VTAS-ENG-NBU-Midas(a)veritas.com<mailto:DL-VTAS-ENG-NBU-Midas@veritas.com>>; Himani Vaidya <Himani.Vaidya(a)veritas.com<mailto:Himani.Vaidya@veritas.com>> Subject: Query regarding initial size for QCOW2 file restore Hi Nir and Daniel, We had a few questions around restoring a qcow2 file to RHV. We plan to support restoring a qcow2 file to RHV. The source of the backups could be from RAW thin/thick or qcow2. When restoring qcow2 we need to provide an initial size. The backup image being restored will have guest data in fragments. When writing these fragments into the qcow2 file we would need to pad them to the qcow2 cluster boundary for every fragment. When providing the initial size to RHV we should have included the amount of padding we would need for every fragment and this would be difficult to get upfront when the qcow2 file is being created at restore time. It will be a function of the guest data fragmentation which would be difficult to get upfront at the start of the restore. We would like to check if there is an easy way around this situation from the RHV side. 1. Can we make the initial size requirement optional when creating a qcow2 file? 2. If not then * Can we write beyond the initial size we provided when creating the file? * Can we use the provisioned size of the virtual disk as the initial size of the qcow2 file (after adding size for headers) and then truncate the file to its actual size after writing the file completely. Though we could run into cases where customers don't have enough space for the provisioned size. Any other ideas to work around this initial size requirement. Thanks, Himani and Mohammed Eliyas.

1 0

oVirt 4.3.1 blockers
by Sandro Bonazzola 19 Feb '19

19 Feb '19

Hi, we are building 4.3.1 RC1 today and we still have 21 blocker bugs for this release. Please review all of them since we can't release 4.3.1 next week with known blockers. 1484053 <https://bugzilla.redhat.com/show_bug.cgi?id=1484053> ovirt-engine BLL.Storage ASSIGNED eshenitz(a)redhat.com ebenahar(a)redhat.com Storage create_lease task is not ordered to be cleared and gets s... <https://bugzilla.redhat.com/show_bug.cgi?id=1484053> 1520546 <https://bugzilla.redhat.com/show_bug.cgi?id=1520546> ovirt-engine BLL.Storage NEW bzlotnik(a)redhat.com ebenahar(a)redhat.com Storage LSM with continuous I/O to the VM failed and auto generat... <https://bugzilla.redhat.com/show_bug.cgi?id=1520546> 1528944 <https://bugzilla.redhat.com/show_bug.cgi?id=1528944> ovirt-engine BLL.Virt NEW michal.skrivanek(a)redhat.com mavital(a)redhat.com Virt [UI] - 'Migrate VMs' dialog - 'Select Host Automatically'... <https://bugzilla.redhat.com/show_bug.cgi?id=1528944> 1552344 <https://bugzilla.redhat.com/show_bug.cgi?id=1552344> vdsm Core NEW dchaplyg(a)redhat.com ebenahar(a)redhat.com Storage [Backup restore API][libgfapi] Start VM, with snapshot di... <https://bugzilla.redhat.com/show_bug.cgi?id=1552344> 1557272 <https://bugzilla.redhat.com/show_bug.cgi?id=1557272> ovirt-engine BLL.Virt NEW michal.skrivanek(a)redhat.com mavital(a)redhat.com Virt If VMs are paused while cluster compatiblity level is upg... <https://bugzilla.redhat.com/show_bug.cgi?id=1557272> 1570368 <https://bugzilla.redhat.com/show_bug.cgi?id=1570368> ovirt-engine RestAPI NEW omachace(a)redhat.com ebenahar(a)redhat.com Virt REST-API: GET diskattachments for a vm is missing a logic... <https://bugzilla.redhat.com/show_bug.cgi?id=1570368> 1597019 <https://bugzilla.redhat.com/show_bug.cgi?id=1597019> vdsm Core NEW bzlotnik(a)redhat.com ebenahar(a)redhat.com Storage LSM's diskReplicateFinish failed on libvirtError: interna... <https://bugzilla.redhat.com/show_bug.cgi?id=1597019> 1615974 <https://bugzilla.redhat.com/show_bug.cgi?id=1615974> ovirt-engine-metrics RFEs POST sradco(a)redhat.com isaranov(a)redhat.com Metrics [RFE][Tracker] - Replace fluentd for shipping metrics and... <https://bugzilla.redhat.com/show_bug.cgi?id=1615974> 1636901 <https://bugzilla.redhat.com/show_bug.cgi?id=1636901> ovirt-engine BLL.Virt NEW michal.skrivanek(a)redhat.com mavital(a)redhat.com Virt [UI] - User <UNKNOWN> got disconnected from VM 'VM name' ... <https://bugzilla.redhat.com/show_bug.cgi?id=1636901> 1641617 <https://bugzilla.redhat.com/show_bug.cgi?id=1641617> ovirt-engine BLL.Virt NEW rbarry(a)redhat.com pagranat(a)redhat.com Virt [Executor] Worker blocked vdsm error happens while HE VM ... <https://bugzilla.redhat.com/show_bug.cgi?id=1641617> 1646161 <https://bugzilla.redhat.com/show_bug.cgi?id=1646161> ovirt-engine BLL.Storage NEW sleviim(a)redhat.com ebenahar(a)redhat.com Storage IndexOutOfBoundsException: Index: 0, Size: 0 during impor... <https://bugzilla.redhat.com/show_bug.cgi?id=1646161> 1647491 <https://bugzilla.redhat.com/show_bug.cgi?id=1647491> ovirt-engine BLL.Storage NEW bzlotnik(a)redhat.com ebenahar(a)redhat.com Storage All VMs on the same host crash when a snapshot fail on on... <https://bugzilla.redhat.com/show_bug.cgi?id=1647491> 1649328 <https://bugzilla.redhat.com/show_bug.cgi?id=1649328> ovirt-engine BLL.Virt NEW akrejcir(a)redhat.com pagranat(a)redhat.com Virt no memory deflation/inflation in mom (unchanged balloonIn... <https://bugzilla.redhat.com/show_bug.cgi?id=1649328> 1654679 <https://bugzilla.redhat.com/show_bug.cgi?id=1654679> vdsm Gluster NEW sankarshan(a)redhat.com sasundar(a)redhat.com Gluster Provide upgrade instructions for oVirt 4.3 which is based... <https://bugzilla.redhat.com/show_bug.cgi?id=1654679> 1661888 <https://bugzilla.redhat.com/show_bug.cgi?id=1661888> ovirt-engine Frontend.UserPortal NEW smelamud(a)redhat.com lsvaty(a)redhat.com Virt Cluster compatibility version could not be updated by UI. <https://bugzilla.redhat.com/show_bug.cgi?id=1661888> 1663242 <https://bugzilla.redhat.com/show_bug.cgi?id=1663242> ovirt-ansible-roles General NEW omachace(a)redhat.com lsvaty(a)redhat.com Infra Check for update on host doesn't work with dnf installed <https://bugzilla.redhat.com/show_bug.cgi?id=1663242> 1665072 <https://bugzilla.redhat.com/show_bug.cgi?id=1665072> ovirt-engine Packaging.rpm NEW sbonazzo(a)redhat.com lsvaty(a)redhat.com Metrics [blocked] On engine side add write_syslog collectd output... <https://bugzilla.redhat.com/show_bug.cgi?id=1665072> 1670312 <https://bugzilla.redhat.com/show_bug.cgi?id=1670312> ovirt-imageio Daemon POST derez(a)redhat.com ebenahar(a)redhat.com Storage ovirt-imageio-daemon fails to start after reboot <https://bugzilla.redhat.com/show_bug.cgi?id=1670312> 1672318 <https://bugzilla.redhat.com/show_bug.cgi?id=1672318> vdsm General NEW srakonde(a)redhat.com lsvaty(a)redhat.com Gluster "failed to fetch volume file" when trying to activate hos... <https://bugzilla.redhat.com/show_bug.cgi?id=1672318> 1672859 <https://bugzilla.redhat.com/show_bug.cgi?id=1672859> ovirt-engine BLL.Virt NEW rbarry(a)redhat.com mavital(a)redhat.com Virt Cannot correctly upgrade an hosted engine env from 4.2 to... <https://bugzilla.redhat.com/show_bug.cgi?id=1672859> 1677361 <https://bugzilla.redhat.com/show_bug.cgi?id=1677361> ovirt-engine Setup.Engine POST stirabos(a)redhat.com pmatyas(a)redhat.com Integration Unsupported custom compatibility version check for VMs is... <https://bugzilla.redhat.com/show_bug.cgi?id=1677361> IDProductComponentStatusAssigneeQAContactoVirt TeamSummary -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

1 0

vdsm has been tagged (v4.20.47)
by Milan Zamazal 19 Feb '19

19 Feb '19

1 0

vdsm has been tagged (v4.30.9)
by Milan Zamazal 19 Feb '19

19 Feb '19

6 9

Permissions for Hosted-Engine VM and Storage Domain
by Ravi Shankar Nori 18 Feb '19

18 Feb '19

Hi All, This is in regard to BZ 1511697 - Unable to set permission on all but Hosted-Engine VM and Storage Domain The Issue: --------------- As described in the BZ, inherited permissions for HE VM/SD lets non SUPER_USER admins perform operations on the VM. Currently as far as permissions go there is no way to distinguish between a HE VM/SD and normal VMs/SDs and there is no way to set permissions only for the HE VM/SD. So all admins can perform operation on the HE VM/SD. Proposed Solution: -------------------------- The proposed solution is to prevent operations on a HE VM/SD for all users who do not have SUPER_USER system privilages as per [2]. Moving host to maintenance is allowed for all admins and the HE VM/SD is listed in search queries. Only when performing operations on the VM/SD we check user permissions. This requires documentation change as not all admin users can perform actions on a HE VM/SD. Please let me know if you have any objections to the proposed change before it is merged. Thanks Ravi [1] https://bugzilla.redhat.com/show_bug.cgi?id=1511697 [2] https://gerrit.ovirt.org/#/c/97689/

1 0

Reminder: please build packaged for 4.3.1 RC today
by Sandro Bonazzola 18 Feb '19

18 Feb '19

We are composing 4.3.1 RC tomorrow morning (11:00 CET timezone), please build your packages before that time and be sure to update the releng-tools configuration files for the release including your builds. Thanks, -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

2 1

[ OST Failure Report ] [ oVirt Master) ] [ 17-02-2019 ]
by Galit Rosenthal 18 Feb '19

18 Feb '19

Hi, CQ is failing on 'upgrade-from-release-suite-master' It seems like something has happened with rh-postgresql95-postgresql The log from the engine: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12918/artifa… Can someone please take a look at the issue? Thanks Galit Error: 2019-02-16 16:28:06,874-0500 DEBUG otopi.plugins.otopi.services.systemd systemd.state:130 starting service rh-postgresql95-postgresql 2019-02-16 16:28:06,874-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:813 execute: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service'), executable='None', cwd='None', env=None 2019-02-16 16:28:07,913-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.executeRaw:863 execute-result: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service'), rc=1 2019-02-16 16:28:07,914-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:921 execute-output: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service') stdout: 2019-02-16 16:28:07,914-0500 DEBUG otopi.plugins.otopi.services.systemd plugin.execute:926 execute-output: ('/usr/bin/systemctl', 'start', 'rh-postgresql95-postgresql.service') stderr: Job for rh-postgresql95-postgresql.service failed because the control process exited with error code. See "systemctl status rh-postgresql95-postgresql.service" and "journalctl -xe" for details. 2019-02-16 16:28:07,915-0500 DEBUG otopi.transaction transaction.abort:119 aborting 'File transaction for '/var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf'' 2019-02-16 16:28:07,916-0500 DEBUG otopi.context context._executeMethod:143 method exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/otopi/context.py", line 133, in _executeMethod method['method']() File "/usr/share/ovirt-engine/setup/bin/../plugins/ovirt-engine-setup/ovirt-engine/provisioning/postgres.py", line 201, in _misc self._provisioning.provision() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 498, in provision self.restartPG() File "/usr/share/ovirt-engine/setup/ovirt_engine_setup/engine_common/postgres.py", line 399, in restartPG state=state, File "/usr/share/otopi/plugins/otopi/services/systemd.py", line 141, in state service=name, RuntimeError: Failed to start service 'rh-postgresql95-postgresql' 2019-02-16 16:28:07,918-0500 ERROR otopi.context context._executeMethod:152 Failed to execute stage 'Misc configuration': Failed to start service 'rh-postgresql95-postgresql' 2019-02-16 16:28:07,958-0500 DEBUG otopi.plugins.otopi.debug.debug_failure.debug_failure debug_failure._notification:100 tcp connections: id uid local foreign state pid exe [CQ]: 97705, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause A system test invoked by the "ovirt-master" change queue including change 97705,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 97719,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 97719,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/97705/6 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97719/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12916/ _______________________________________________ Infra mailing list -- infra(a)ovirt.org To unsubscribe send an email to infra-leave(a)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/infra@ovirt .org/message/LSBTLNTO6PE723XG5TELUHPXFLZEHODK/ -- GALIT ROSENTHAL SOFTWARE ENGINEER Red Hat <https://www.redhat.com/> galit(a)gmail.com T: 972-9-7692230 <https://red.ht/sig>

2 1

new easy way to open issues for ovirt.org and documentation
by Greg Sheremeta 18 Feb '19

18 Feb '19

Hi, I created some footer links on ovirt.org to make it super easy to open GitHub issues. We often get questions about where to report documentation issues and things like that -- hopefully this eases the pain. When you are visiting any page on ovirt.org and you see a problem or have an idea for enhancement, simply scroll down and click 'Report an issue on GitHub'. [image: Selection_393.png] Full demo (2 minutes): https://www.youtube.com/watch?v=TbORKknLVL4 (and, of course, if you're so inclined, the Edit link starts a PR for you ...) Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig>

2 2

[VDSM] Flaky protocol detector test
by Nir Soffer 17 Feb '19

17 Feb '19

Recently this test cause too many random failures. I guess this is the known issue with handling SUBSCRIBE in protocol detector. I posted https://gerrit.ovirt.org/c/97099/ To mark it as broken until we have time to dig deeper ====================================================================== FAIL: test_detect_slow_client_concurrency(True) (protocoldetector_test.AcceptorTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/testlib.py", line 142, in wrapper return f(self, *args) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py", line 167, in test_detect_slow_client_concurrency self.check_concurrently(self.check_slow_client, use_ssl) File "/home/jenkins/workspace/vdsm_standard-check-patch/vdsm/tests/protocoldetector_test.py", line 266, in check_concurrently self.assertTrue(all(done)) AssertionError: False is not true -------------------- >> begin captured logging << -------------------- 2019-01-19 20:47:16,021 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Creating socket (host='127.0.0.1', port=0, family=2, socketype=1, proto=6) (protocoldetector:225) 2019-01-19 20:47:16,022 INFO (MainThread) [vds.MultiProtocolAcceptor] Listening at 127.0.0.1:46009 (protocoldetector:183) 2019-01-19 20:47:16,023 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding detector <protocoldetector_test.Echo object at 0x7f1bb77f8dd0> (protocoldetector:210) 2019-01-19 20:47:16,024 DEBUG (MainThread) [vds.MultiProtocolAcceptor] Adding detector <protocoldetector_test.Uppercase object at 0x7f1bb77f8c90> (protocoldetector:210) 2019-01-19 20:47:16,031 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51950 (protocoldetector:61) 2019-01-19 20:47:16,047 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51952 (protocoldetector:61) 2019-01-19 20:47:16,048 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51954 (protocoldetector:61) 2019-01-19 20:47:16,065 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51956 (protocoldetector:61) 2019-01-19 20:47:16,068 INFO (Thread-61) [ProtocolDetector.AcceptorImpl] Accepted connection from 127.0.0.1:51958 (protocoldetector:61) 2019-01-19 20:47:16,069 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,097 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,099 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,107 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,109 DEBUG (Thread-61) [ProtocolDetector.Detector] Using required_size=9 (protocoldetector:89) 2019-01-19 20:47:16,574 INFO (Thread-61) [ProtocolDetector.Detector] Detected protocol echo from 127.0.0.1:51950 (protocoldetector:125) 2019-01-19 20:47:17,570 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) 2019-01-19 20:47:17,571 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) 2019-01-19 20:47:17,576 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) 2019-01-19 20:47:17,578 DEBUG (Thread-61) [ProtocolDetector.Detector] Timed out while waiting for data (protocoldetector:94) --------------------- >> end captured logging << ---------------------

2 7