Description of problem: ..during installation, this renders following messages: Creating directory server . . . sh: semanage: command not found -< here Your new DS instance 'rider' was successfully created. what is the impact of above? Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to comment #0) > Description of problem: > ..during installation, this renders following messages: > > Creating directory server . . . > sh: semanage: command not found -< here > Your new DS instance 'rider' was successfully created. > > what is the impact of above? The impact is that the Directory Server and Admin Server ports may not be properly labelled. The setup scripts label the selected Directory Server port as ldap_port_t (teh standard ports are already labelled by the base system policy), and the Admin Server port as http_port_t.
The dependency on policycoreutil-python has been added to the 389-ds-base spec file since the setup perl modules that use semanage are a part of that package. This will be fixed in 389-ds-base-1.2.6 alpha 3.
The dependency has also been added to the 389-admin spec file since it calls semanage directly from one of it's perl modules. This will be fixed in 389-admin-1.1.11 alpha 3.
Marking verified based on Comment#5.