RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1242861 - enterprise user is not logged in after creation in g-i-s
Summary: enterprise user is not logged in after creation in g-i-s
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-initial-setup
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 7.2
Assignee: Matthias Clasen
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-14 09:39 UTC by Vladimir Benes
Modified: 2015-11-19 08:28 UTC (History)
1 user (show)

Fixed In Version: gnome-initial-setup-3.14.4-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 08:28:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2157 0 normal SHIPPED_LIVE control-center bug fix and enhancement update 2015-11-19 08:48:59 UTC

Description Vladimir Benes 2015-07-14 09:39:07 UTC
Description of problem:
I've added freeipa enterprise user with sssd, home dir should be created via oddjobd but it doesn't work. I can successfully log in via gdm after killing the stalled session where g-i-s just disappeared and no info is shown.

GDM writes out that it creates directory but this is not the case in g-i-s. I think this code should be added or user at least warned that he has to relogin via gdm.

Version-Release number of selected component (if applicable):
gnome-initial-setup-3.14.4-1.el7.x86_64
gnome-shell-3.14.4-13.el7.x86_64
gdm-3.14.2-5.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.configure freeipa with user (I have beaker job doing so, can provide it)
1a configure oddjobd to create home directory 
2.start g-i-s and add that user
3.end g-i-s with start using RHEL
4.stalled session without user logged in

Actual results:
you have to kill the session and relog via gdm, this works, home dir is created and user can be used

Expected results:
g-i-s should log you into the session with home dir automatically created

Additional info:

Comment 2 Vladimir Benes 2015-07-14 14:07:10 UTC
so the issue is not the directory creation as if directory exists g-i-s doesn't log the user anyway.

Comment 3 Vladimir Benes 2015-07-14 15:52:21 UTC
after logging in yelp with getting started should be started not gnome-initial-setup as it's now.

Comment 4 Matthias Clasen 2015-07-15 20:12:04 UTC
the reason that gnome-initial-setup gets started again after login is that the copying of saved data from gnome-initial-setup to the account failed - that would have put in place ~/.config/gnome-initial-setup-done, which is the marker to tell us we don't need to run it in the session.

Comment 5 Ray Strode [halfline] 2015-07-27 20:42:09 UTC
i have a patch for this, but it still needs a little more work before it's ready

Comment 6 Vladimir Benes 2015-07-29 14:46:49 UTC
(In reply to Ray Strode [halfline] from comment #5)
> i have a patch for this, but it still needs a little more work before it's
> ready

Very well, Ray! It's fixed!

Comment 9 errata-xmlrpc 2015-11-19 08:28:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2157.html


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