On 01/16/12 17:49, Drew Fisher wrote:
On 1/16/12 4:38 AM, Jan Damborsky wrote:
On 01/13/12 06:33 PM, Drew Fisher wrote:
Another solution that occurs to me is that the initial user account
creation could perhaps be disabled in sysconfig when it detects
such a
condition. I'm not sure I like it, necessarily, but it also prevents
the system ending up in maintenance mode from this situation, which
seems important to me.
Comparing with other alternatives, I think this would be the best
trade off for now. In addition to that, related help screen could be
amended to clarify that behavior.
Unless we work out another solution, if you agree, I would proceed
with
this approach. I think filing separate CR would be perhaps
appropriate
as these
changes would end up if install gate (while config-user ones will
go into ON one).
I don't have a better idea, but I'd like Drew to agree with this, too.
I think this solution has the most merit. We can alter sysconfig to
detect this entire condition and inform the user during sysconfig
rather than after the fact (when the system is in maintenance mode)
and point them to documentation to help them.
Also, with sysconfig groups project, coming back later (after the
datasets and mountpoints are set correctly) to only configure the
admin user will be considerably easier on the user.
Thank you, Drew.
Since the thread is relatively long, let me try to summarize
proposed changes below to be sure I haven't forgotten anything.
Drew, Dave, Mike, please let me know if I missed or misunderstood
any point.
Thank you very much,
Jan
[1] SCI tool
SCI tool will check for presence of parent of home ZFS dataset.
If the parent is missing, creation of initial user account will be
disabled.
Related help screen will be enhanced to clarify the reason.
[2] config-user smf service
config-user will not create parents of home ZFS dataset. If any of
parent
is missing, config-user willinform in smf log file which datasets are
missing
and in default case (home ZFS dataset not explicitly specified in SC
manifest)
it will also provide set of commands which could be used to create
missing datasets.
Then the service will enter maintenance mode.
Example of error message logged in default case:
"Service failed to create home directory ZFS dataset for initial
user, because following
parent ZFS datasets are missing (were not created during installation):
rpool/export
rpool/export/home
To recover from the failure, create parent dataset(s) manually on
command line with:
zfs create -o mountpoint=/export rpool/export
zfs create rpool/export/home
then clear the service using 'svcadm clear config-user'.
Alternatively, reinstall
affected system(s) using ai_manifest(4) specifying appropriate
entries for those
ZFS datasets (refer to /usr/share/auto-install/manifest/default.xml
as an example)."
[3] Default AI manifests
Section defining creation of <root_pool>/export and
<root_pool>/export/home
ZFS datasets will be enriched with comment clarifying impact of not
creating
those datasets (i.e. how configuration of initial user account is to
be affected).
[4] Documentation
Existing documentation will be examined to make sure it provides correct
and complete information.
Sounds good, Jan. Thanks for researching this.
Thank you, guys.
Jan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
