Description of problem: While running dnf update, the following appeared between the last "Cleanup" line and the first "Verifying" line: Cleanup : PyYAML-3.11-9.fc23.x86_64 280/280 Configuration node global/system_id_source not found Verifying : kernel-core-4.2.7-300.fc23.x86_64 1/280 I have no idea what this line means, how important it is, or what I am supposed to do about it. Did the upgrade succeed, or is the system in an inconsistent / vulnerable state? Version-Release number of selected component (if applicable): $ rpm -qa | egrep dnf | sort dnf-1.1.4-2.fc23.noarch dnf-conf-1.1.4-2.fc23.noarch dnf-langpacks-0.15.1-1.fc23.noarch dnf-langpacks-conf-0.15.1-1.fc23.noarch dnf-plugins-core-0.1.14-1.fc23.noarch dnf-plugin-system-upgrade-0.7.1-1.fc23.noarch dnf-yum-1.1.4-2.fc23.noarch python2-dnf-1.1.4-2.fc23.noarch python2-dnf-plugin-system-upgrade-0.7.1-1.fc23.noarch python3-dnf-1.1.4-2.fc23.noarch python3-dnf-langpacks-0.15.1-1.fc23.noarch python3-dnf-plugins-core-0.1.14-1.fc23.noarch python3-dnf-plugin-system-upgrade-0.7.1-1.fc23.noarch python-dnf-langpacks-0.15.1-1.fc23.noarch python-dnf-plugins-core-0.1.14-1.fc23.noarch python-dnf-plugins-extras-common-0.0.12-1.fc23.noarch python-dnf-plugins-extras-migrate-0.0.12-1.fc23.noarch How reproducible: 1/1 Steps to Reproduce: 1. sudo dnf upgrade Actual results: The line "Configuration node global/system_id_source not found" appears. Expected results: The line does not appear. Additional info:
Created attachment 1106498 [details] list of installed packages
This is error from rpm, probably from %post scriplet execution of some package.
This error is not from rpm. It is from some scriptlet executed from rpm. Probably postscript from kernel package which generates ramdisk using dracut tool. See bug 1284381 Can you confirm this by trying to recreate ramdisk?
> See bug 1284381 > Can you confirm this by trying to recreate ramdisk? Confirmed. I have the exact problem as described in BZ 1284381: an older /etc/lvm/lvm.conf file and a newer /etc/lvm/lvm.conf.rpmnew that has the missing value. Updating the /etc/lvm/lvm.conf file makes the message go away.
*** This bug has been marked as a duplicate of bug 1284381 ***