- Devel - oVirt List Archives

ovirt-engine has been tagged (ovirt-engine-4.2.7.5 )
by Tal Nisan 13 Nov '18

13 Nov '18

1 0

[ACTION REQUIRED] oVirt 4.3.0 Beta preparations
by Sandro Bonazzola 12 Nov '18

12 Nov '18

Hi, we'd like to be ready for releasing a first oVirt 4.3.0 beta on November 26th. In order to do that, we need all packages to be ready for it by Sunday November 25th. Maintainers: please ensure your packages can be installed are feature complete with regards to ovirt-4.3.0 target and passed CI testing. An integration testing on the master nightly will be done manually on Friday November 23rd to ensure basic functionalities are working as expected. Please note we don't have any guarantee that CentOS 7.6 will be out by that time. Please check oVirt 4.3 Beta release criteria[1] and help getting ready for it. If you have something that should block the beta release please raise the issue as soon as possible. Thanks, [1] https://www.ovirt.org/develop/release-management/releases/4.3/release-manag… -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig>

3 4

amount of reports by abrt
by Piotr Kliczewski 12 Nov '18

12 Nov '18

I attended a talk about abrt and noticed there are good number of reports [1] generated by issues in ovirt. Thanks, Piotr [1] https://retrace.fedoraproject.org/faf/reports/

3 4

ovirt-engine external IDP (Keycloak) integration
by Ravi Shankar Nori 09 Nov '18

09 Nov '18

Hi All, Please find design document [1] for integrating ovirt-engine with Keycloak using mod_auth_openidc. Engine can be configured to use external IDP to handle user authentication while still supporting Rest API bearer authentication. There are some changes to how clients will obtain tokens to use for bearer authentication. All clients need to request tokens from the external IDP and use it to access engine. When external authentication is enabled admin@internal and all internal profiles for authentication are disabled. Please see the design document for more details. Thanks Ravi [1] https://docs.google.com/document/d/1Wio7bQNeNinx7Luj5t-KpsSYQ2Z1Y0I8UhUyJAZ… Integration Issues that need attention 1. Ovirt-engine Python, Java and Ruby SDKs need to be modified to obtain token from either engine SSO or external OpenID Connect IDP. 2. OVN if we are not using SDK needs to be modified to obtain token from either engine SSO or external OpenID Connect IDP. 3. OVN changes needed to config user admin@internal. admin@internal access will be disabled if external integration is enabled. So OVN needs to be configurable to use another user for REST API access. 4. Ansible is using SDK, if SDK is fixed to use a file the file needs to passed from ansible to SDK. 5. Cloudforms and Satellite are using Ruby SDK, we need to file a bug to fix the issue. The file with the details of external IDP URL and client-id and client-secret needs to be passed to SDK. 6. REST API SDK V3 is not going to work with password and negotiate authentication 7. VM Single Sign-on will not work as we don’t have a password. 8. VM Console needs to work, if VM console is using token and bearer authentication everything should work

3 3

Failing compilation of engine to RPM using build-artefacts.sh
by Andrej Krejcir 08 Nov '18

08 Nov '18

Hi, I use a VM with latest CentOS to compile engine to RPM. Steps: - git clone repo from my dev machine to the VM - run ovirt-engine/automation/build-artifacts.sh This used to work, but since about 2 weeks ago the build fails with an error message: + %py_byte_compile /usr/bin/python2 /root/rpmbuild/BUILDROOT/ovirt-engine-4.3.0-0.0.master.20181105130924.git58423b7.el7.x86_64/usr/share/ovirt-engine/ /var/tmp/rpm-tmp.f7B35C: line 82: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.f7B35C (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.f7B35C (%install) Attaching the whole build log and the file '/var/tmp/rpm-tmp.f7B35C'. I'm not sure how to fix this. Can anyone help? Thanks, Andrej

2 1

Fwd: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 719 - Still Failing!
by Eitan Raviv 08 Nov '18

08 Nov '18

Hi, We have a failure on OST/network-suite-master for several days now. My suspicions of the cause are detailed below. Can you have a look? Thanks ---------- Forwarded message --------- From: Eitan Raviv <eraviv(a)redhat.com> Date: Mon, Nov 5, 2018 at 8:39 AM Subject: Re: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 719 - Still Failing! To: Ori Liel <oliel(a)redhat.com> Hi, Can you have a look? Thanks On Thu, Nov 1, 2018 at 10:08 AM Eitan Raviv <eraviv(a)redhat.com> wrote: > Hi Ondra, > > We have above failure on OST network-suite-4.2 [1] due to: > Fault reason is "Request syntactically incorrect.". Fault detail is "For > correct usage, see: > https://192.168.201.4/ovirt-engine/apidoc#services/vm/methods/preview_snaps… > " > > and I see in engine.log [2]: > > javax.xml.bind.UnmarshalException: unexpected element (uri:"", local:"disks") > > at the same time I see in model_4.2 [3] that a change was done to add the disks, but if i am not mistaken the ovirt-engine-sdk pom.xml [4] was not bumped to reflect this change. > > Can you please check? > > Thanks > > [1] > https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/719/arti… > [2] > https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/717/arti… > [3] > https://gerrit.ovirt.org/#/q/project:ovirt-engine-api-model+branch:model_4.2 > [4] https://gerrit.ovirt.org/#/q/project:ovirt-engine-sdk+branch:sdk_4.2 > > > > ---------- Forwarded message --------- > From: Edward Haas <edwardh(a)redhat.com> > Date: Thu, Nov 1, 2018 at 8:35 AM > Subject: Fwd: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build > # 719 - Still Failing! > To: <rhevm-network-staff(a)redhat.com> > > > FYI > > ---------- Forwarded message --------- > From: <jenkins(a)jenkins.phx.ovirt.org> > Date: Thu, Nov 1, 2018 at 6:02 AM > Subject: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # > 719 - Still Failing! > To: <lgoldber(a)redhat.com>, <edwardh(a)redhat.com>, <infra(a)ovirt.org> > > > Project: > http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ > Build: > http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/719/ > Build Number: 719 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #717 > [Marcin Sobczyk] Change logging level for 'schema.inconsistency' > > > Changes for Build #718 > [Ales Musil] master: Update master suite compatibility version > > > Changes for Build #719 > [Ales Musil] master: Update master suite compatibility version > > > > > ----------------- > Failed Tests: > ----------------- > 1 tests failed. > FAILED: > network-suite-4.2.tests.test_mac_pools.test_undo_preview_snapshot_when_mac_used_reassigns_a_new_mac > > Error Message: > Error: Fault reason is "Request syntactically incorrect.". Fault detail is > "For correct usage, see: > https://192.168.201.4/ovirt-engine/apidoc#services/vm/methods/preview_snaps…". > HTTP response code is 400. > > Stack Trace: > system = <lib.system.SDKSystemRoot object at 0x7fc7f91f48d0> > default_cluster = <lib.clusterlib.Cluster object at 0x7fc7f91f4bd0> > ovirtmgmt_vnic_profile = <lib.netlib.VnicProfile object at 0x7fc7f81b3710> > cirros_template = 'Cirros_0_4_0' > > def test_undo_preview_snapshot_when_mac_used_reassigns_a_new_mac( > system, default_cluster, ovirtmgmt_vnic_profile, > cirros_template): > with virtlib.vm_pool(system, size=2) as (vm_0, vm_1): > vm_0.create(vm_name=VM0, > cluster=default_cluster, > template=cirros_template) > vm_0.wait_for_down_status() > > vm_0.run() > vm_0.wait_for_up_status() > > nicless_snapshot = _create_snapshot(vm_0) > > vm_0.create_vnic(NIC_NAME_1, ovirtmgmt_vnic_profile, > MAC_ADDR_1) > vm_0.stop() > vm_0.wait_for_down_status() > > > nicless_snapshot.preview() > > network-suite-4.2/tests/test_mac_pools.py:124: > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ > network-suite-4.2/lib/virtlib.py:243: in preview > snapshot=self.get_sdk_type() > /usr/lib64/python2.7/site-packages/ovirtsdk4/services.py:31091: in > preview_snapshot > return self._internal_action(action, 'previewsnapshot', None, headers, > query, wait) > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:299: in > _internal_action > return future.wait() if wait else future > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:55: in wait > return self._code(response) > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:296: in callback > self._check_fault(response) > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:132: in > _check_fault > self._raise_error(response, body) > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ _ _ > > response = <ovirtsdk4.http.Response object at 0x7fc7f81b3350> > detail = <ovirtsdk4.types.Fault object at 0x7fc7f81b39d0> > > @staticmethod > def _raise_error(response, detail=None): > """ > Creates and raises an error containing the details of the > given HTTP > response and fault. > > This method is intended for internal use by other components > of the > SDK. Refrain from using it directly, as backwards > compatibility isn't > guaranteed. > """ > fault = detail if isinstance(detail, types.Fault) else None > > msg = '' > if fault: > if fault.reason: > if msg: > msg += ' ' > msg = msg + 'Fault reason is "%s".' % fault.reason > if fault.detail: > if msg: > msg += ' ' > msg = msg + 'Fault detail is "%s".' % fault.detail > if response: > if response.code: > if msg: > msg += ' ' > msg = msg + 'HTTP response code is %s.' % response.code > if response.message: > if msg: > msg += ' ' > msg = msg + 'HTTP response message is "%s".' % > response.message > > if isinstance(detail, six.string_types): > if msg: > msg += ' ' > msg = msg + detail + '.' > > class_ = Error > if response is not None: > if response.code in [401, 403]: > class_ = AuthError > elif response.code == 404: > class_ = NotFoundError > > error = class_(msg) > error.code = response.code if response else None > error.fault = fault > > raise error > E Error: Fault reason is "Request syntactically incorrect.". Fault > detail is "For correct usage, see: > https://192.168.201.4/ovirt-engine/apidoc#services/vm/methods/preview_snaps…". > HTTP response code is 400. > > /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:118: Error >

4 7

[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-11-2018 ] [ 002_bootstrap.add_dc ]
by Dafna Ron 06 Nov '18

06 Nov '18

Hi, We failed to add a DC due to computability level in the upgrade suite. The upgrade suite is upgrading 4.2 to master. Eli, can you please check if any fix is needed for upgrade? Link and headline of suspected patches: https://gerrit.ovirt.org/#/c/95190/ - engine: Remove Cluster Levels 3.6 and 4.0 Link to Job: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975 Link to all logs: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/10975/artifa… (Relevant) error snippet from the log: <error> 2018-11-04 06:26:54,619-05 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-1) [1d8362d9] EVENT_ID: USER_VDC_LOGIN(30), User admin@internal-authz connecting from '192.168.201.1' using session 'v2y73+8hVB7ccwgjlAQOAK539eW6UsAysQQHbbiSy+mGDSTjOyZ38bpl9XLrGXSLJAqKyeXSdqfrbAqB4qWZUA==' logged in. 2018-11-04 06:26:54,873-05 WARN [org.ovirt.engine.core.bll.storage.pool.AddEmptyStoragePoolCommand] (default task-1) [4b627395-5dd6-4211-a63e-d78f3728ec6f] Validation of action 'AddEmptyStoragePool' failed for user admin@internal-authz. Reasons: VAR__TYPE__STORAGE__POOL,VAR__ACTION__CREATE,ACTION_TYPE_FAILED_GIVEN_VERSION_NOT_SUPPORTED 2018-11-04 06:26:54,877-05 ERROR [org.ovirt.engine.api.restapi.resource.AbstractBackendResource] (default task-1) [] Operation Failed: [Cannot create Data Center. Selected Compatibility Version is not supported. </error>

2 2

Fwd: [CentOS-devel] Point-release Freeze is Active
by Sandro Bonazzola 02 Nov '18

02 Nov '18

FYI. This shouldn't affect directly oVirt 4.2.7 but further updates to oVIrt deps will need to wait till CentOS 7.6 will be out. ---------- Forwarded message --------- From: Brian Stinson <brian(a)bstinson.com> Date: gio 1 nov 2018 alle ore 16:29 Subject: [CentOS-devel] Point-release Freeze is Active To: <centos-devel(a)centos.org> Hi Folks, As is usual, we freeze the SIG Sign + Push process as part of preparing for a point release. This helps us once CR is ready (it isn't yet, though) so that we can seed it quickly in CBS to build against. The Point-release Freeze does not affect content moving from the testing tags in CBS to buildlogs.c.o, that will continue to show up as it is built. Do note: since we do want to give testers and developers an opportunity to build and test against an upcoming point-release before it goes GA, content coming from buildlogs.centos.org may require enabling the CR repo once it's ready. Any new requests for sign+push (adding new tags to mirror.c.o) during Point-release Freeze will be held until the point release goes GA. If there are any questions, please let us know and discuss here on the list. Cheers! -- Brian Stinson _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org https://lists.centos.org/mailman/listinfo/centos-devel -- 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

Fwd: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs
by Sandro Bonazzola 01 Nov '18

01 Nov '18

FYI ---------- Forwarded message --------- From: Ben Cotton <bcotton(a)redhat.com> Date: mer 17 ott 2018 alle ore 15:29 Subject: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs To: <devel(a)lists.fedoraproject.org>, <devel-announce(a)lists.fedoraproject.org > https://fedoraproject.org/wiki/Changes/nfs.conf == Summary == Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure NFS daemons. == Owner == * Name: Steve Dickson * Email: steved(a)redhat.com == Detailed Description == Since the beginning /etc/sysconfig/nfs has been used to configure the NFS server daemons by supply command line arguments to the daemons or commands via SysVinit scripts. Then systemd(1) came along and the idea of daemons self-configuration was started. Meaning daemons and commands would get their configurations from a file, not the command line like with SysVinit scripts. Back in late 2016, Neil Brown from SuSe, implemented this changed. He built into each daemon the ability to read from one central file, /etc/nfs.conf. See nfs.conf(5) for details. After this work made it upstream, I a wrote patch that added back the ability to use /etc/sysconfig/nfs to maintain backwards compatibility which has lasted for the last few Fedora releases. I think at this point, the timing is right to introduce this single file configuration to Fedora 30. == Benefit to Fedora == * Having a single file configuration will help IT automation systems like Ansible configure NFS servers. * This change also simplifies the systemd scrips. * Having two ways of configuring NFS is not desirable. The only reason there has been no problems is because nobody know about /etc/nfs.conf * There is a new command, nfsconf(8), that checks the correctness of /etc/nfs.conf == Scope == * Proposal owners: Steve Dickson <steved(a)redhat.com> * Other developers: Justin Mitchell <jumitche(a)redhat.com> * Release engineering: [https://pagure.io/releng/issue/7864 #7864 F30: Deprecating /etc/sysconfig/nfs] ** List of deliverables: nfs-utils-2.3.3-1.fc30 * Policies and guidelines: The guidelines to use /etc/nfs.conf are already being install with nfs.conf(5) and nfsconf(8) manpages * Trademark approval: No trademarks are being changed so no approval is needed. == Upgrade/compatibility impact == In [https://bugzilla.redhat.com/show_bug.cgi?id=1619270 BZ1619270] a python script that will convert a sysconfig/nfs config into nfs.conf config. There are a couple thoughts on how to use it. On clean installs, when sysconfig/nfs does not exist, sysconfig/nfs wil still be installed with directions to use nfs.conf to do the configuration. When sysconfig/nfs does exist, the configuration will '''not''' be overwritten, but the systemd scripts will not use the file to configure NFS. The two thoughts on how to use python script: # Have the upgrade run the script and maybe throw out a message that the configuration has now been moved to nfs.conf # Throw a message indicating the NFS configuration has changed and then have the admin run the script The first thought is probably the cleanest but changing configurations behind admin's back is not very nice... I am very open on how to use this script. == How To Test == With the new nfsconf(8) command, the nfs.conf can be tested for correctness, other than that, we should do the same testing as we do today == User Experience == After the initial shock, I think users will embrace the new configuration. Being able to configure NFS via IT automation systems (aka Ansible) is a step in the right direction. Having a command to check the correctness of the configuration will be welcome. == Dependencies == There are no dependencies that I know of. == Contingency Plan == * Contingency mechanism: Revert the commit that removed support for /etc/sysconfig/nfs. * Contingency deadline: 2019-03-05 (Beta Freeze) * Blocks release? No * Blocks product? No == Documentation == There are two man pages, nfs.conf(5) and nfsconf(8). == Release Notes == The new way of configuring NFS should be release noted. -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis _______________________________________________ devel mailing list -- devel(a)lists.fedoraproject.org To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…>

2 1

Query regarding OST test suite execution
by viraj shirsat 31 Oct '18

31 Oct '18

Hi , Good Morning :) This is regarding OST tool setup i need some help on the same. Please find below details. My Setup : 1> Setup one open source ovirt engine 2> Setup one node and added the same on ovrit engine 3> Setup one VM for OST tool with following dependencies. 1.Setup LAGO 2.Git Clone OST 3.Install MOCK *Please let me know if i am missing anything* Query : I am trying to run the OST from local machine but i am not able to figure sequence of the steps to execute . Can i get an sample sequence steps how to run any test suite(any). Error : [root@localhost lago]# lago status Unable to find workdir in /jenkins/jobs/confs/projects/lago What is workdir here, m i missing some thing ? Waiting for your reply :) Thanks in Advance Viraj

2 1