Bug 1394864

Summary: libcrypt-nss conflicts with libcrypt
Product: [Fedora] Fedora Reporter: penthium2 <penthium2>
Component: livecd-toolsAssignee: Brian Lane <bcl>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: adam.stokes, bcl, bruno, dhuff, Jasper.Hartline, jrefl5, katzj, penthium2, sherba800
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-30 18:00:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description penthium2 2016-11-14 15:35:40 UTC
Description of problem:
Error creating Live CD : Failed to build transaction : libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64
libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.livecd-creator  --releasever=25 --config=/root/mykickstart.ks --fslabel=myiso-alpha_1_x86_64
2.
3.

Actual results:

Error creating Live CD : Failed to build transaction : libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64
libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64
Expected results:


Additional info:

Comment 1 Brian Lane 2016-11-14 16:30:13 UTC
That's not a bug -- it means that whatever repos you are using have a problem, or that you have selected conflicting packages in your kickstart.

Comment 2 penthium2 2016-11-15 07:18:17 UTC
Sory it's a bug, I just try this creation : 
livecd-creator  --releasever=25 --config= /usr/share/spin-kickstarts/fedora-live-lxde.ks --fslabel=forBugzilla

And this is the result :
/usr/lib64/python2.7/optparse.py:1013: PendingDeprecationWarning: The KSOption class is deprecated and will be removed in pykickstart-3.  Use the argparse module instead.
  option = self.option_class(*args, **kwargs)
['/sbin/mkfs.ext4', '-F', '-L', '_forBugzilla', '-m', '1', '-b', '4096', '/dev/loop0']
/usr/lib/python2.7/site-packages/yum/config.py:1093: PendingDeprecationWarning: use len(mi) instead
  startupconf.distroverpkg)
No such package system-config-network to remove
Error creating Live CD : Failed to build transaction : libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64
libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64

In this test, I'm using the official kickstart file form fedora to build the 
fedora-live-lxde iso file.

Please move on.

Comment 3 penthium2 2016-11-15 07:36:04 UTC
please accept my apology for the stupid : "move on"

Comment 4 Artem 2016-11-28 14:37:52 UTC
I confirm this annoying bug. No matter whether it be custom (created by user) or default kickstart file you have used to create iso you will get the same error.

Comment 5 James Crawford 2016-11-29 18:58:25 UTC
in kickstart file do:
-libcrypt
libcrypt-nss

and you get pass that problem, you then get an error from resizefs.

"Error creating Live CD : resize2fs returned an error (-11)"

.
.
.
Unmounting directory /var/tmp/x64/imgcreate-eJEwo5/install_root
Losetup remove /dev/loop0
Checking filesystem /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
resizing /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
Checking filesystem /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
Truncating sparse file /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img to 4381298688
Extending sparse file /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img to 8589934592
Checking filesystem /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
resizing /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
Checking filesystem /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
Losetup add /dev/loop0 mapping to /var/tmp/x64/imgcreate-eJEwo5/tmp-a2xOzn/ext3fs.img
Extending sparse file /var/tmp/x64/imgcreate-eJEwo5/iso-L2YGSL/LiveOS/osmin to 67108864
Losetup add /dev/loop1 mapping to /var/tmp/x64/imgcreate-eJEwo5/iso-L2YGSL/LiveOS/osmin
Checking filesystem /dev/mapper/imgcreate-2894-40523
resizing /dev/mapper/imgcreate-2894-40523
Losetup remove /dev/loop1
Losetup remove /dev/loop0
Error creating Live CD : resize2fs returned an error (-11)!

.
.
Should this br opened as a new BUG?

Comment 6 Brian Lane 2016-11-29 22:45:37 UTC
Is there any other information available? -11 doesn't appear to be a normal resize2fs error so I suspect you have something else going wrong.

Comment 7 James Crawford 2016-11-30 00:42:47 UTC
Same script I was using Last Monday on a fedora 24 system.
I can reproduce once I get back in to work in the AM. any diags/logs you want can be gotten with guidance options to get the needed info let me know.
I'll run it about 1400-1500 UTC

Comment 8 James Crawford 2016-11-30 17:00:08 UTC
See comment 25 in bug 1360781. They used e2fsprogs from 
e2fsprogs-1.43.3-1.fc26.src.rpm and the resize2fs appears to work.

just got 93 updates on the F25 system will retest after a reboot.

Comment 9 James Crawford 2016-11-30 17:47:38 UTC
Still getting resize2fs error, the following is in /var/log/messages

ov 30 10:43:47 localhost kernel: show_signal_msg: 12 callbacks suppressed
Nov 30 10:43:47 localhost kernel: resize2fs[32733]: segfault at 20 ip 000055ac4b7094fc sp 00007ffc06438520 error 4 in resize2fs[55ac4b704000+d000]
Nov 30 10:43:48 localhost abrt-hook-ccpp: Process 32733 (resize2fs) of user 0 killed by SIGSEGV - dumping core

anyone want me to zip up the core dump and attach it?

Comment 10 Brian Lane 2016-11-30 18:00:24 UTC
So that sounds like an e2fsprogs bug, or something going wrong with your hardware. I'd open a bug with e2fsprogs and include the coredump.

Comment 11 James Crawford 2016-11-30 19:51:10 UTC
(In reply to Brian Lane from comment #10)
> So that sounds like an e2fsprogs bug, or something going wrong with your
> hardware. I'd open a bug with e2fsprogs and include the coredump.

Thanks will do

Comment 12 Red Hat Bugzilla 2023-09-14 03:34:23 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days