Bug 1702024
| Summary: | Cannot create Directory Server's instances using dscreate | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Akshay Adhikari <aadhikar> |
| Component: | 389-ds-base | Assignee: | mreynolds |
| Status: | CLOSED ERRATA | QA Contact: | RHDS QE <ds-qe-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 8.0 | CC: | abokovoy, kbanerje, lkrispen, mkosek, ndehadra, nkinder, nsoman, rmeggins, spichugi, tbordaz, vashirov |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | 8.1 | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-1.4-8010020190526145819.eb48df33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-11-05 21:00:29 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Akshay Adhikari
2019-04-22 18:20:25 UTC
I'm stumped. I built rpms from scratch on your test system using the same source code that is in 1.4.0.20-9 and it installs fine every time. (In reply to mreynolds from comment #2) > I'm stumped. I built rpms from scratch on your test system using the same > source code that is in 1.4.0.20-9 and it installs fine every time. I am still facing the same issue while trying the same on the test machine. [root@vm-idm-005 ~]# dscreate interactive Install Directory Server (interactive mode) =========================================== Enter system's hostname [vm-idm-005.lab.eng.pnq.redhat.com]: Use strict hostname verification (set to "no" if using GSSAPI behind a load balancer) [yes]: yes Enter the instance name []: test Enter port number [389]: Create self-signed certificate database [yes]: Enter secure port number [636]: Enter Directory Manager DN [cn=Directory Manager]: Enter the Directory Manager password: Confirm the Directory Manager Password: Enter the database suffix (or enter "none" to skip) [dc=vm-idm-005,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com]: dc=example,dc=com Create sample entries in the suffix [no]: yes Do you want to start the instance after the installation? [yes]: yes Are you ready to install? [no]: yes Starting installation... Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv → /usr/lib/systemd/system/dirsrv@.service. Job for dirsrv failed because of unavailable resources or another system error. See "systemctl status dirsrv" and "journalctl -xe" for details. Error: Command '['systemctl', 'start', 'dirsrv@test']' returned non-zero exit status 1. Also with the inf file. [root@vm-idm-005 ~]# dscreate from-file instance.inf Starting installation... Job for dirsrv failed because of unavailable resources or another system error. See "systemctl status dirsrv" and "journalctl -xe" for details. Error: Command '['systemctl', 'start', 'dirsrv@dsinstance']' returned non-zero exit status 1. I think I'm testing on a different system: vm-idm-033.lab.eng.pnq.redhat.com Is there another one I should be using? Okay, I apparently was sabotaging my own testing. For some reason when I was building my test RPMS on the beaker systems, those builds were updating the filesystem in a way that "fixed" the problem. So every RPM I tested after that "worked". This obviously gave me inconsistent test results, and sent me looking in the wrong direction. Only after trying a fresh RHEL 8 system with rpms built on a different system was the problem still present. I was able to verify that this problem is fixed upstream, and I'm pretty sure fix is found in these two related tickets: https://pagure.io/389-ds-base/issue/50123 - with_tmpfiles_d is associated to systemd https://pagure.io/389-ds-base/issue/50125 - perl fix ups for tmpfiles I will be confirming this tomorrow There was a regression that appears was introduced in 1.4.0.20-8 - this is now fixed. Build Tested: 389-ds-base-1.4.0.20-10.module+el8.0.0+3096+101825d5.x86_64 1) Creating an instance using the inf file. [root@vm-idm-005 ~]# dscreate from-file instance.inf Starting installation... Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv → /usr/lib/systemd/system/dirsrv@.service. Completed installation for dsinstance-new [root@vm-idm-005 ~]# status-dirsrv Status of instance "dsinstance-new" ● dirsrv - 389 Directory Server dsinstance-new. Loaded: loaded (/usr/lib/systemd/system/dirsrv@.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2019-04-24 22:33:51 IST; 5s ago 2) Creating an instance in interactive mode. [root@vm-idm-005 ~]# dscreate interactive Install Directory Server (interactive mode) =========================================== Enter system's hostname [vm-idm-005.lab.eng.pnq.redhat.com]: Use strict hostname verification (set to "no" if using GSSAPI behind a load balancer) [yes]: Enter the instance name [vm-idm-005]: Enter port number [389]: Create self-signed certificate database [yes]: Enter secure port number [636]: Enter Directory Manager DN [cn=Directory Manager]: Enter the Directory Manager password: Confirm the Directory Manager Password: Enter the database suffix (or enter "none" to skip) [dc=vm-idm-005,dc=lab,dc=eng,dc=pnq,dc=redhat,dc=com]: dc=example,dc=com Create sample entries in the suffix [no]: yes Are you ready to install? [no]: yes Starting installation... Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv → /usr/lib/systemd/system/dirsrv@.service. Completed installation for vm-idm-005 The instance is up and running, marking this as VERIFIED. 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://access.redhat.com/errata/RHSA-2019:3401 |