Bug 1396731 - Network broken after update (multiple bind99-libs versions)
Summary: Network broken after update (multiple bind99-libs versions)
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: bind99
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Menšík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-19 12:43 UTC by Jan Vlug
Modified: 2016-11-21 10:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-21 10:06:06 UTC
Type: Bug


Attachments (Terms of Use)

Description Jan Vlug 2016-11-19 12:43:06 UTC
Description of problem:
After updating my system, the network does not work correctly anymore.
It seems that dhcp is not working correctly anymore.

output of: dnf list installed | grep bind:
bind-libs.x86_64                         32:9.10.4-2.P4.fc24            @updates
bind-libs-lite.x86_64                    32:9.10.4-2.P4.fc24            @updates
bind-license.noarch                      32:9.10.4-2.P4.fc24            @updates
bind-utils.x86_64                        32:9.10.4-2.P4.fc24            @updates
bind99-libs.x86_64                       9.9.9-2.P3.fc24                @updates
bind99-libs.x86_64                       9.9.9-4.P4.fc24                @System 
bind99-license.noarch                    9.9.9-2.P3.fc24                @updates
bind99-license.noarch                    9.9.9-4.P4.fc24                @System 
jackson-databind.noarch                  2.6.3-2.fc24                   @fedora 
keybinder3.x86_64                        0.3.0-6.fc24                   @fedora 
rpcbind.x86_64                           0.2.3-11.rc1.fc24              @updates
xapian-bindings.x86_64                   1.2.23-1.fc24                  @updates
xapian-bindings-python.x86_64            1.2.23-1.fc24                  @updates

Comment 1 Jan Vlug 2016-11-19 13:12:44 UTC
I resolved this problem by manually configuring the IP, netmask and dns server for the network and executing the following commands:

dnf reinstall bind99-libs
which gave these errors:
Error: Transaction check error:
  file /usr/lib64/bind99/libdns-export.so.172 from install of bind99-libs-9.9.9-4.P4.fc24.x86_64 conflicts with file from package bind99-libs-9.9.9-2.P3.fc24.x86_64
  file /usr/lib64/bind99/libirs-export.so.91.0.3 from install of bind99-libs-9.9.9-4.P4.fc24.x86_64 conflicts with file from package bind99-libs-9.9.9-2.P3.fc24.x86_64
  file /usr/lib64/bind99/libisc-export.so.106.1.1 from install of bind99-libs-9.9.9-4.P4.fc24.x86_64 conflicts with file from package bind99-libs-9.9.9-2.P3.fc24.x86_64
  file /usr/lib64/bind99/libisccfg-export.so.90.3.1 from install of bind99-libs-9.9.9-4.P4.fc24.x86_64 conflicts with file from package bind99-libs-9.9.9-2.P3.fc24.x86_64
  file /usr/share/doc/bind99-libs/README from install of bind99-libs-9.9.9-4.P4.fc24.x86_64 conflicts with file from package bind99-libs-9.9.9-2.P3.fc24.x86_64


So I removed:
dnf remove bind99-libs-9.9.9-2.P3.fc24.x86_64
dnf reinstall bind99-libs
dnf remove bind99-license-9.9.9-2.P3.fc24.noarch

Probably something went wrong during the update. Feel free to close this bug if you think that this was not a Fedora, but a local issue for me.

Comment 2 Petr Menšík 2016-11-21 10:06:06 UTC
I think it is issue of your installation. You have installed two instances of same package and I think that is unsupported. Problem is, you system thinks the newer version is manually installed. I recommend different approach.

# Remove newer duplicate
dnf remove bind99-libs-9.9.9-4.P4.fc24.x86_64
# Update previous installation to newer version
dnf upgrade bind99-libs

On my systems, bind99-libs always reports source repository as @updates. I am unable to reproduce your situation. Is it possible you installed bind99-libs with updates-testing repo enabled before?

Reopen please if it does not solve your problem.


Note You need to log in before you can comment on or make changes to this bug.