Re: [CentOS-devel] SIGs: Possibility to drop EOL content at 7.6.1810 release time
by Sandro Bonazzola
Il giorno ven 2 nov 2018 alle ore 12:33 Niels de Vos <ndevos(a)redhat.com> ha
scritto:
> On Thu, Nov 01, 2018 at 11:01:51AM +0200, Anssi Johansson wrote:
> ...
> > For reference and inspiration, here are some directories from
> > mirror.centos.org, including both up-to-date content and potentially EOL
> > content. SIGs should review the list to make sure these directories can
> > be copied over to 7.6.1810 when that time comes. Making the decisions
> > now would save a bit of time at 7.6.1810 release time.
> >
> ..
>
> > storage/x86_64/gluster-3.10
> > storage/x86_64/gluster-3.12
>
> The above two can be dropped (also for CentOS 6). This includes the
> centos-release-gluster310 and centos-release-gluster-312 packages in
> Extras.
>
>
Can we keep 3.12? It's still consumed by oVirt 4.2.
Adding oVirt devel team, just in case we'll need urgently to rebase on
newer Gluster on CentOS 7.6 GA or block upgrade to CentOS 7.6 from oVirt
side till we figure out how to handle.
> > storage/x86_64/gluster-4.0
> > storage/x86_64/gluster-4.1
> > storage/x86_64/gluster-5
>
> These three are still maintained.
>
> Thanks,
> Niels
> _______________________________________________
> 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>
5 years
[ACTION REQUIRED] oVirt 4.3.0 Beta preparations
by Sandro Bonazzola
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-man...
--
SANDRO BONAZZOLA
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://red.ht/sig>
5 years
ovirt-engine external IDP (Keycloak) integration
by Ravi Shankar Nori
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-KpsSYQ2Z1Y0I8UhUyJ...
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
5 years
Failing compilation of engine to RPM using build-artefacts.sh
by Andrej Krejcir
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
5 years
Fwd: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 719 - Still Failing!
by Eitan Raviv
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_sna...
> "
>
> 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/ar...
> [2]
> https://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/717/ar...
> [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_sna...".
> 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_sna...".
> HTTP response code is 400.
>
> /usr/lib64/python2.7/site-packages/ovirtsdk4/service.py:118: Error
>
5 years
[ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 05-11-2018 ] [ 002_bootstrap.add_dc ]
by Dafna Ron
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/arti...
(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>
5 years
