[Starlingx-discuss] 【StarlingX】Regarding CentOS 8 Kernel & RPMS environment upgrade
zhaos at neusoft.com
zhaos at neusoft.com
Mon Jul 20 08:42:04 UTC 2020
Hi StarlingX Community：
Regarding CentOS 8 Kernel & RPMS environment upgrade:
CentOS 8 environment upgrading for StarlingX has completed tasks as follows:：
(1). Completion of CentOS 8 Container compilation environment upgrade and support for Layer Build.
(2). Based on the CentOS 8 environment, you can successfully build the ISO file, and boot and install the ISO normally。
(3). The basic RPM/SRPM/TAR packages has been upgraded and submitted to CentOS 8 branch。
SRPM （el7-> el8 upgrade）
49
TAR Upgrade
192
RPM Noarch Upgrade
784
RPM X86-64 Upgrade
1134
Patch Upload
277
Patch upload path: https://review.opendev.org/#/q/topic:centos8+branch:f/centos8
For detailed upgrade package name and statistical results, please refer to Google Doc path:
https://drive.google.com/drive/folders/1dacqazwoKZwPNFIf1ccdeDTH0z1KcPiF?usp=sharing
CentOS 8 environment upgrading for StarlingX currently is working on the following content：
(1). Fix puppet command error
https://review.opendev.org/#/c/740207/
(2). oidc-auth-tools should use python3
https://review.opendev.org/#/c/739877/
(3). https://review.opendev.org/#/q/owner:fuyong%2540neusoft.com+status:open
(4). Fix docker-ce installation error
https://review.opendev.org/#/c/741564/
https://review.opendev.org/#/c/741563/
CentOS 8 environment upgrading for StarlingX the follow-up work is as follows：
(1). RPM Signature of CentOS8 upgrade.
When generating an ISO in a centos8 environment, once the rpm is signed, it cannot be installed normally.
Error message: package libgcc-8.3.1-4.5.el8.x86_64 does not verify: Payload SHA256 digest:
BAD (Expected 7f29143af796be275a93a9b34348d50fdf4fbfdc1f0eb0ec665839fc2862a88c != c099cc8c0c04b1a7534bd4b0338)
① We think the version of rpm and dnf used for build is inconsistent with the version of dnf and rpm used for ISO installation.
After the versions are consistent, the problem still occurs.
② We generated PKCS#8 KEY in centos8 environment instead of ima_signing_key.priv, but still did not solve the problem.
③ And we found that not all rpm packages can not be verified.
eg:
[fy at 15799bc37d1f Packages]$ rpm -K -v lvm2-2.03.05-5.el8.0.1.x86_64.rpm
lvm2-2.03.05-5.el8.0.1.x86_64.rpm:
Header SHA256 digest: OK
Header SHA1 digest: OK
Payload SHA256 digest: OK
MD5 digest: OK
[fy at 15799bc37d1f Packages]$ rpm -K -v lvm2-libs-2.03.05-5.el8.0.1.x86_64.rpm
lvm2-libs-2.03.05-5.el8.0.1.x86_64.rpm:
Header SHA256 digest: OK
Header SHA1 digest: OK
Payload SHA256 digest: BAD (Expected 7fa4ad6535a742f748e092cce42c2b85af76207f8499924d4ed5f59d9559fda8 !=
be1b9ba6355003b4c89d6ba3fb4de5daee8260edd9a8ce363f7e9d29ae9a99fd)
MD5 digest: BAD (Expected ad345d7dc65b948ee681f374ea691d7a != 37fc3cdb87dd1a190305ddb5b46de9fa)
For detailed verify statistics, please refer to Google Doc path:
https://drive.google.com/drive/folders/1xvZoyBAg3XVlHySu5itJcCYoQdlDZPhz?usp=sharing
(2). The libvirtd.service does not start after booting:
localhost:/home/sysadmin# virsh list
error: failed to connect to the hypervisor
error: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory
Since the status of the libvirtd service is disabled, the service is inactive after booting, resulting in virsh list failed
.
(3). config/sysinv Requires: python3-ipaddr. But python3-ipaddr package does not exist in Centos8
(4). utilites/python-cephclient Requires:
python3-ipaddress. But python3-ipaddress package does not exist in centos8
(5). Some services failed to start problem.
--------------------------
1) services error info:
localhost:/home/sysadmin# systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● controllerconfig.service loaded failed failed controllerconfig service
● dnf-makecache.service loaded failed failed dnf makecache
● fm-api.service loaded failed failed Fault Management REST API Servi>
● logmgmt.service loaded failed failed StarlingX Log Management
Wait for the master merge to branch centos8, and the logmgmt.service error is fixed
● sm-api.service loaded failed failed Service Management API Unit
● sw-patch.service loaded failed failed StarlingX Patching
● sysinv-agent.service loaded failed failed StarlingX System Inventory Agent
● syslog-ng.service loaded failed failed System Logger Daemon
After configuring IP, restart the syslog-ng.service successfully
The above is StarlingX's information collation based on CentOS 8 environment branch,
the current branch: f/centos8 base environment has merged the Layer Build function from the master (Master: 2020-05-20).
We believe that the subsequent master merger task will be a relatively easy task.
As the focus of our team's tasks is gradually tilted towards Rook&Ceph related content.
Finally, we would like to thank the community experts who have followed and reviewed the CentOS 8 upgrade task during this period.
Thank you for your great support !
Best Regards
-----------------
From: Neusoft - Team
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication
is not the intended recipient,unauthorized use,forwarding, printing, storing, disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this communication in error,please
immediately notify the sender by return e-mail, and delete the original message and all copies from
your system. Thank you.
---------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.starlingx.io/pipermail/starlingx-discuss/attachments/20200720/5e10e462/attachment-0001.html>
More information about the Starlingx-discuss
mailing list