Description of problem: At the end of the install procedure during the creation of the user account. Version-Release number of selected component: anaconda-23.19.2-1 The following was filed automatically by anaconda: anaconda 23.19.2-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.4/site-packages/pyanaconda/users.py", line 211, in createGroup raise ValueError("Group %s already exists" % group_name) File "/usr/lib64/python3.4/site-packages/pyanaconda/kickstart.py", line 728, in execute users.createGroup(grp.name, **kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/install.py", line 95, in doConfiguration ksdata.group.execute(storage, ksdata, instClass, u) File "/usr/lib64/python3.4/threading.py", line 868, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) ValueError: Group users already exists Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-23_B_T4-x86_64 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.2.0-1.fc23.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 23
Created attachment 1071308 [details] File: anaconda-tb
Created attachment 1071309 [details] File: anaconda.log
Created attachment 1071310 [details] File: dnf.log
Created attachment 1071311 [details] File: dnf.rpm.log
Created attachment 1071312 [details] File: environ
Created attachment 1071313 [details] File: lsblk_output
Created attachment 1071314 [details] File: nmcli_dev_list
Created attachment 1071315 [details] File: os_info
Created attachment 1071316 [details] File: storage.log
Created attachment 1071317 [details] File: syslog
Created attachment 1071318 [details] File: ifcfg.log
Created attachment 1071319 [details] File: packaging.log
Created attachment 1071320 [details] File: program.log
What steps did you take leading up to the crash? What options did you set when creating a user?
(In reply to David Shea from comment #14) The crash was triggered by adding the group "users" when creating the new user.
This issue was absent from anaconda-23.19.1-1.fc23 as included in Fedora 23 Beta TC1.
Another user experienced a similar problem: I added "users" as additional group for the new user. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-23_B_T5-x86_64 rd.live.check quiet hashmarkername: anaconda kernel: 4.2.0-300.fc23.x86_64 package: anaconda-23.19.3-1 product: Fedora reason: ValueError: Group users already exists release: Cannot get release name. version: 23
Proposed as a Freeze Exception for 23-final by Fedora user dshea using the blocker tracking app because: There doesn't appear to be anything in the criteria about user creation, but this is pretty severe change in behavior. This crash will affect any install that attempts to add a user to an existing system group, both interactive and kickstart installs.
[anaconda root@localhost tmp]# anaconda --version anaconda 23.19.3-1 Tested f23/aarch64 instalation. New user added to 'wheel, mock' groups and instalation failed in same way: 12:29:09,375 CRIT anaconda: Traceback (most recent call last): File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) File "/usr/lib64/python3.4/threading.py", line 868, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/install.py", line 95, in doConfiguration ksdata.group.execute(storage, ksdata, instClass, u) File "/usr/lib64/python3.4/site-packages/pyanaconda/kickstart.py", line 728, in execute users.createGroup(grp.name, **kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/users.py", line 211, in createGroup raise ValueError("Group %s already exists" % group_name) ValueError: Group mock already exists 12:29:09,376 DEBUG anaconda: Gtk running, queuing exception handler to the main loop
System got installed and is in bootable state. Just no user created.
Another user experienced a similar problem: I created an administrator user and tried to add it to both the wheel and systemd-journal groups. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-23_B-x86_64 quiet hashmarkername: anaconda kernel: 4.2.0-300.fc23.x86_64 package: anaconda-23.19.4-1 product: Fedora reason: ValueError: Group systemd-journal already exists release: Cannot get release name. version: 23
Another user experienced a similar problem: This happens when you specify GID in brackets to a group which already exists. But this brackets should be considered only if group does not exist. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-23_B-x86_64 rd.live.check quiet hashmarkername: anaconda kernel: 4.2.0-300.fc23.x86_64 package: anaconda-23.19.4-1 product: Fedora reason: ValueError: Group users already exists release: Cannot get release name. version: 23
Discussed at 2015-09-28 freeze exception review meeting: https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2015-09-28/f23-blocker-review.2015-09-28-16.01.html . Accepted as a freeze exception issue, this is a noticeable installer bug that can't be fixed with an update, and should be fixable quite safely.
Another user experienced a similar problem: tried to install fedora23 cinnamon beta on VirtualBox 4.3.26. I have chosed to add user into additional groups: plugdev,netdev,audio,video. And on Creating users this error appeared cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz0 initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Cinnamon-x86_64-23_B rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 hashmarkername: anaconda kernel: 4.2.0-300.fc23.x86_64 other involved packages: python3-libs-3.4.3-5.fc23.x86_64 package: anaconda-core-23.19.4-1.fc23.x86_64 product: Fedora reason: ValueError: Group audio already exists release: Fedora release 23 (Twenty Three) version: 23
python-blivet-1.12.6-1.fc23 anaconda-23.19.6-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-6f7d535c92
anaconda-23.19.6-1.fc23, python-blivet-1.12.6-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update anaconda python-blivet' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-6f7d535c92
anaconda-23.19.6-1.fc23, python-blivet-1.12.6-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
Another user experienced a similar problem: Just ran installer. USB created with dd. Had to boot in low grahics mode, probably because of bumblebee. Still 1920x1080. Partition existed, added extra existing partition at custom mount point. All in all, nothing special. cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/isolinux/vmlinuz0 root=live:LABEL=Fedora-Live-Xfce-x86_64-23_B-1 ro rd.live.image quiet rhgb nomodeset hashmarkername: anaconda kernel: 4.2.0-300.fc23.x86_64 other involved packages: python3-libs-3.4.3-5.fc23.x86_64 package: anaconda-core-23.19.4-1.fc23.x86_64 product: Fedora reason: ValueError: Group dialout already exists release: Fedora release 23 (Twenty Three) version: 23
The fix for this landed after Beta. You should find that it works in Final TC/RC builds, which you can read about on test@ and find at https://dl.fedoraproject.org/pub/alt/stage/ . Thanks for the report!
Thanks @awilliam. Re-ran the installer labelled TC11. (Had to use basic graphics mode again, which is a different issue.) Asked again to add user to group "dialout". Issue not reproduced, confirming the "close" status. Thank you for your attention.