[ 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, 5 months
Fwd: [CentOS-devel] Point-release Freeze is Active
by Sandro Bonazzola
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>
5 years, 5 months
Fwd: Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs
by Sandro Bonazzola
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=70...>
5 years, 5 months