Is it possible to lose configs after updating CentOS?

Question

CentOS

I want to update CentOS via yum update, tell me if it is possible to lose configs and disrupt the web server as a result of the update?
Here is the list of updated packages:

================================================= ================================================= ============================
Package
==================== ================================================= ================================================= =========
Installing:
kernel
kernel-devel
Updating:
ImageMagick
atomic-release
b43-openfwwf
bash
bind
bind-libs
bind-utils
binutils
cairo
centos-release
chkconfig
clamav
clamav-db
clamd
coreutils
coreutils-libs
cronie
cronie- anacron
cups-libs
curl
db4
db4-cxx
db4-devel
db4-utils
dejavu-fonts-common
dejavu-lgc-sans-mono-fonts
dejavu-sans-fonts
dejavu-sans-mono-fonts
device-mapper
device-mapper-libs
dhclient
dhcp-common
dovecot
dracut
dracut-kernel
e2fsprogs
e2fsprogs-libs
efibootmgr
elfutils-libelf
elfutils-libs
ethtool
fail2ban
gawk
gdbm
gdbm-devel
gdk-pixbuf2
ghostscript
glibc
glibc-common
glibc-devel
glibc-headers
gnutls
the grep
grub
hwdata
initscripts
iproute the
iptables
iputils
the kernel-the firmware the
kernel-The headers
kexec-tools
kpartx
krb5-libs
libX11
libX11-common
all libxfont
the libc-client
libcom_err
libcurl
libdrm
libedit
libicu the
libpng
libsemanage
libss is the
libstdc ++
libudev
libuser
libwmf-lite
libxcb the
libxml2
logrotate
is the lsof the
mdadm
mhash
mod_ruid2
module -init-tools
mysql
mysql-libs
mysql-server
ncurses
ncurses-base
ncurses-libs
nspr
nss
nss-softokn
nss-softokn-freebl
nss-sysinit
nss-tools
nss-util
openldap
openldap-devel
openssh
openssh-clients
openssh-server
openssl
pam
parted
pcre
pcre-devel
perl
perl-Archive-Tar
perl-Compress-Raw-Zlib
perl-Compress-Zlib
perl-Digest-SHA
perl-ExtUtils-MakeMaker
perl-ExtUtils-ParseXS
perl-IO-Compress-Base
perl-IO-Compress-Zlib
perl-IO-Socket-INET6
perl-IO-Zlib
perl-Module-Pluggable
perl-Package-Constants
perl-Pod-Escapes
perl-Pod-Simple
perl-Test-Harness
perl-Time-HiRes
perl-devel
perl-libs
perl- version
php
php-bcmath
php-cli
php-common
php-devel
php-gd
php-imap
php-intl
php-ldap
php-mbstring
php-mcrypt
php-mysql
php-pdo
php-php-gettext
php-process
php-pspell
php -recode
php-soap
php-tcpdf
php-tcpdf-dejavu-sans-fonts
php-tidy
php-xml
php-xmlrpc
pinentry
policycoreutils
polkit
postfix
procps
python
python-libs
quota
rpm
rpm-libs
rpm-python
screen
selinux-policy
selinux-policy-targeted
spamassassin
sqlite
sudo
sysvinit-tools
tzdata
udev
vesta-nginx
vesta-php
vim-common
vim -enhanced
vim-minimal
vsftpd
xorg-x11-drv-ati-firmware
yum
Installing for dependencies:
ipset
libmnl
libwmf
perl-Error
perl-Mail-SPF
vim-filesystem

Answer 1

Good afternoon. Replacing the configuration files of a particular software depends on the operation of rpm, or rather on the rpm specification written by the developer of the package assembly. So, if the files in the cpio archive of the rpm package are marked as %config in the specification, then during installation an additional check is performed on the state of the files on the target system (controlled by the noreplace additional specification).
To solve your problem, you can go in two directions:
1. Create a test environment for checking for updates. Update the packages you are interested in (from the list) separately on the test environment, checking the changes made at each step.
2. Connect src repositories corresponding to the current repo on your system. These src repositories contain src.rpm files which, when installed, will give you access to the specification files (spec files) of the rpm packages you are interested in. You will study the necessary spec file directives and understand what changes will be made when installing the package.
More about %config directive: www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html
More about rpm: https://docs.fedoraproject.org/en-US/Fedora_Draft_...