Bug 1168613 - dscreate not on openSUSE Leap 15.1 and manual tells to use it
Summary: dscreate not on openSUSE Leap 15.1 and manual tells to use it
Status: RESOLVED FIXED
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Installation (show other bugs)
Version: Leap 15.1
Hardware: 64bit Other
: P5 - None : Major with 3 votes (vote)
Target Milestone: ---
Assignee: William Brown
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-03 17:43 UTC by Boyd Gerber
Modified: 2020-04-15 22:31 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Boyd Gerber 2020-04-03 17:43:02 UTC
dscreate not found.

The documentation says

https://doc.opensuse.org/documentation/leap/security/single-html/book.security/index.html

I ran

zypper install 389-ds

yast2 ldap-server

Then I tried to run the above.  It fails with

Internal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.

Caller:  /usr/lib64/ruby/2.5.0/open3.rb:199:in `spawn'

Details: No such file or directory - /usr/sbin/dscreate


These commands do not exist:

The 389 Directory Server is controlled by 3 primary commands:

dsctl

Manages a local instance and requires root permissions. Requires you to be connected to a terminal which is running the directory server instance. Used for starting, stopping, backing up the database and more.

dsconf

The primary tool used for administration and configuration of the server. Manages an instance's configuration via its external interfaces. This allows you to make configuration changes remotely on the instance.

dsidm

Used for identity management (manage users, groups, passwords etc.). The permissions are granted by access controls, so users can reset their own password or change details of their own account, for example.

Creating the 389 Directory Server Instance

You create the instance with the dscreate command. It can take a configuration file (*.inf) which defines the instance configuration settings. Alternatively, the command can be run in an interactive mode.

All the configuration/setups fail with

Details: No such file or directory - /usr/sbin/dscreate

or

/usr/sbin/dscreate
/usr/sbin/dscreate: No such file or directory

How do you setup LDAP when the tools are missing

Searching for dscreate only finds this
/usr/share/dirsrv/inf/dscreate.map

Any ideas? This must be a bug with the packaging of 389-ds

Regards,

--
Boyd Gerber <gerberb@xxxxxxxxx> 801 849-0213
ZENEZ 1042 East Fort Union #135, Midvale Utah 84047
Comment 1 Josef Reidinger 2020-04-06 09:02:04 UTC
reassigning to 389-ds maintainer.
Comment 4 Robert Divko 2020-04-12 12:27:10 UTC
Not only a matter of documentation!
389-ds does not work without it.
All commands dscreaete, dsctl, dsconf, dsidm are missing.
THese are normally in lib389 package, wich seams to be missing.
Comment 5 William Brown 2020-04-14 00:19:46 UTC
Hi there,

It appears there are some updates SLE15p1 that are awaiting release into Leap15.1. I am following up to ensure these are published asap to resolve this issue.

I'm sorry about this, and I appreciate your patience as I work to get it cleaned up. Thanks!
Comment 6 William Brown 2020-04-15 22:31:54 UTC
This has been resolved by the maintenance team pushing the packages into leap 15.1, thanks to them!