Comments

192 Comments

Error: nothing provides dracut >= 044-117 needed by kexec-tools-2.0.13-4.fc25.x86_64

dracut 044-117 is only in rawhide. and f25 has just a 044-77

Is it expected to see such messages in upgrade?

Upgrading : selinux-policy-targeted-3.13.1-211.fc25.noarch 5/24

/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/kubelet(/.*)? (system_u:object_r:svirt_sandbox_file_t:s0 and system_u:object_r:docker_var_lib_t:s0).

/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument

libsemanage.semanage_install_final_tmp: setfiles returned error code 1. (No such file or directory).

/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/kubelet(/.*)? (system_u:object_r:svirt_sandbox_file_t:s0 and system_u:object_r:docker_var_lib_t:s0).

/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument

libsemanage.semanage_install_final_tmp: setfiles returned error code 1. (No such file or directory).

/usr/sbin/semodule: Failed!

Upgrading : docker-selinux-2:1.12.1-7.git49151a1.fc25.x86_64 6/24

/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/kubelet(/.*)? (system_u:object_r:svirt_sandbox_file_t:s0 and system_u:object_r:docker_var_lib_t:s0).

/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument

libsemanage.semanage_install_final_tmp: setfiles returned error code 1. (No such file or directory).

/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/lib/kubelet(/.*)? (system_u:object_r:svirt_sandbox_file_t:s0 and system_u:object_r:docker_var_lib_t:s0).

/etc/selinux/targeted/contexts/files/file_contexts: Invalid argument

libsemanage.semanage_install_final_tmp: setfiles returned error code 1. (No such file or directory).

/usr/sbin/semodule: Failed!

+1

The bug with starting already created containers has not been solved yet.

I cannot start already existing container
[root@host ~]# docker start code_scan
Error response from daemon: shim error: docker-runc not installed on system

Error: failed to start containers: code_scan

Issue with 4.13.0-0.rc1.42.fc25 is fixed

+1

I cannot start already existing container [root@host ~]# docker start code_scan

Error response from daemon: shim error: docker-runc not installed on system

Error: failed to start containers: code_scan

@ignatenkobrain It's true that I have rpm*.41.fc26 on my system. because I had a rawhide and later switched to f25

But It does not change the fact that packages for this update has newer NEVR and update is broken.

BTW upgrade with enabled rawhide does not cause a problem dnf update --enablerepo=rawhide rpm

I assume it is cause by renaming of rpm-python* only in rawhide. Is there a reason why it was not renamed in f25?

[root@host ~]# dnf update --best

Last metadata expiration check: 0:12:30 ago on Tue Aug 23 10:12:46 2016.

Error: package python2-rpm-4.13.0-0.rc1.41.fc26.x86_64 requires rpm(x86-64) =

4.13.0-0.rc1.41.fc26, but none of the providers can be installed.

package python3-rpm-4.13.0-0.rc1.41.fc26.x86_64 requires rpm(x86-64) =

4.13.0-0.rc1.41.fc26, but none of the providers can be installed.

package python2-rpm-4.13.0-0.rc1.41.fc26.x86_64 requires rpm(x86-64) =

4.13.0-0.rc1.41.fc26, but none of the providers can be installed.

package python3-rpm-4.13.0-0.rc1.41.fc26.x86_64 requires rpm(x86-64) =

4.13.0-0.rc1.41.fc26, but none of the providers can be installed

(try to add '--allowerasing' to command line to replace conflicting packages)

[root@host ~]# dnf update

Last metadata expiration check: 0:06:16 ago on Tue Aug 23 10:12:46 2016.

Dependencies resolved.

================================================================================

Package Arch Version Repository Size

================================================================================

Skipping packages with broken dependencies:

rpm x86_64 4.13.0-0.rc1.42.fc25 updates-testing 515 k

rpm-build x86_64 4.13.0-0.rc1.42.fc25 updates-testing 146 k

rpm-build-libs x86_64 4.13.0-0.rc1.42.fc25 updates-testing 120 k

rpm-libs x86_64 4.13.0-0.rc1.42.fc25 updates-testing 297 k

rpm-plugin-selinux x86_64 4.13.0-0.rc1.42.fc25 updates-testing 56 k

rpm-plugin-systemd-inhibit x86_64 4.13.0-0.rc1.42.fc25 updates-testing 56 k

Transaction Summary

================================================================================

Skip 6 Packages

Nothing to do.

Complete!

freeipa indirectly depends on resteasy. But it looks like real bug is in pki-core. https://fedorahosted.org/pki/ticket/2403

karma

+1

karma

+1

karma

+1

+1

+1

karma

+1

+1

and finally workaround :-)

mv /etc/gssproxy/80-httpd.conf /etc/gssproxy/80-httpd.conf~

It failed for me because I do not have an apache user on my system which is required in /etc/gssproxy/80-httpd.conf

and error message is misleading "gssproxy[3400]: Option 'euid' is missing from [service/HTTP]." Such option is in problematic configuration snippet but user does not exist.

karma

gssproxy failed to start for me

/usr/sbin/gssproxy -i -d [2016/05/06 21:42:27]: Debug Enabled (level: 1) [2016/05/06 21:42:27]: Config file(s) not found!