Project

General

Profile

Bug #13096

Need to figure out the disposition of /home in a way that makes sense and doesn't screw things up

Added by Jordan Hubbard over 3 years ago. Updated almost 3 years ago.

Status:
Closed: Not To Be Fixed
Priority:
Expected
Assignee:
-
Category:
OS
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

We currently have at least 3 different "rules" about how /home should exist / be managed / etc.

1. If you have local user accounts, maybe they redirect their home dirs though /home (where /home points to /mnt/tank/MyHomies or something) or maybe they live in /home directly; it's undefined except by long-standing conventions.

2. If you have LDAP configured, apparently /home has to point somewhere specific or things just totally break. We had this problem recently.

3. If you have AD configured, /home has to do something else entirely and not compatibly with LDAP

We need to at the very least create some Python code which manages /home based on "need" and figures out how to report appropriate errors in the case where the needs conflict, but at the very least we need to set and change /home from ONE place so we don't have things dangling or smashed when people change the box's configuration.

History

#1 Updated by John Hixson over 3 years ago

  • Status changed from Unscreened to Investigation

#2 Updated by Jordan Hubbard over 3 years ago

Possible calsoft candidate.

#3 Updated by Jordan Hubbard over 3 years ago

  • Assignee changed from John Hixson to Wojciech Kloska

#4 Updated by Jordan Hubbard over 3 years ago

  • Assignee changed from Wojciech Kloska to Erin Clark

#5 Updated by Jordan Hubbard over 3 years ago

  • Target version changed from 261 to 111

Pushing to NMOS - we are managing to live with this for now.

#6 Updated by Anonymous over 3 years ago

According to description of the bug ,please find my understanding so far and approach as in-lined -

We currently have at least 3 different "rules" about how /home should exist / be managed / etc.
1. If you have local user accounts, maybe they redirect their home dirs though /home (where /home points to /mnt/tank/MyHomies or something) or maybe they live in /home directly; it's undefined except by long-standing conventions. RAVI <<<<< If we are creating a user in FreeNAS then we need to browse a local volume mount point which works fine >>>>>>>

2. If you have LDAP configured, apparently /home has to point somewhere specific or things just totally break. We had this problem recently.
RAVI <<<<<
For testing the remote home directory in an AD environment, where the FreeNAS box is a member of a domain ( xyz.com) we need to
- First join the FreeNAS to Active Directory domain as a member
- Import the users in FreeNAS.
- Set the home folders of AD user (e.g Test) and check if the same is reflecting in FreeNAS
- CRUD operations from the user into its home dir from FreeNAS should be reflecting into AD
>>>>>>>

3. If you have AD configured, /home has to do something else entirely and not compatible with LDAP ""
RAVI<<<<<
The same scenario should be tried with LDAP & FreeNAS >>>>>>>

We can try to test all the 3 scenarios and see what changes are required if we encounter any issue as far as the "Above needs of /home " and log reporting is concerned.
I need your suggestions & approach to move ahead, Thank you !!

-Ravi

#7 Updated by Anonymous over 3 years ago

Hi,

Can anyone suggest if the approach i mentioned above is appropriate? Thank You !!

-Ravi

#8 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Assignee changed from Erin Clark to Anonymous

BRB: over to you calsoft.

#9 Updated by Vaibhav Chauhan about 3 years ago

BRB: Neha, We don't have access to slack logs, please let us know what you need from us.

#10 Updated by Anonymous about 3 years ago

Hi Vaibhav, One of the Calsoft guys(Ravi) has put up his observations and approach on this ticket here. Does the approach look good for fixing this issue?

#11 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

Erin,

Since this was last assigned to you, do you have any comment on their proposed approach?

#12 Updated by Erin Clark about 3 years ago

I think it sounds reasonable, lets try it and see if it works.

#13 Updated by Anonymous about 3 years ago

Hi Erin, if I import freenas users into the AD environment, where am I supposed to create their home directories?

#14 Updated by Anonymous about 3 years ago

Hi Kris, could you please help me with the question I mentioned above?

#15 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Assignee changed from Anonymous to John Hixson

Unfortunately I'm not really the best qualified to answer that, not knowing how AD works under the hood. John, can you ping with your thoughts for Neha?

#16 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Assignee changed from John Hixson to Anonymous

Neha,

Ok, I had a conversation with jpaetzel about this. Where the home dirs live isn't as important. Right now he thinks AD uses /var/db/home and /home is a symlink to there. That is fine. What we really need to do is move the home-dir creation logic out of both the ix-ldap and ix-activedirectory scripts into something like ix-homedir which handles creating $HOME and various sym-links to correct spot and the transition between them. We can keep things in /var/db/home if that is easier.

Does that make sense?

#17 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 3 years ago

  • Target version changed from 111 to 9.10.2

#18 Avatar?id=14398&size=24x24 Updated by Kris Moore almost 3 years ago

  • Status changed from Investigation to Closed: Not To Be Fixed

Old calsoft bug, closing this one out as NTBF.

Also available in: Atom PDF