#51161 incorrect hostname and formatting issues causes SLE15.2 install to soft fail
Closed: wontfix 3 years ago by firstyear. Opened 3 years ago by firstyear.

Issue Description

There are two minor issues that cause issues with SLE15.2

--- Logging error ---
Traceback (most recent call last):
  File "/usr/lib64/python3.6/logging/__init__.py", line 996, in emit
    stream.write(msg)
UnicodeEncodeError: 'ascii' codec can't encode character '\u2192' in position 152: ordinal not in range(128)
Call stack:
  File "/usr/sbin/dscreate", line 75, in <module>
    result = args.func(inst, log, args)
  File "/usr/lib/python3.6/site-packages/lib389/cli_ctl/instance.py", line 68, in instance_create
    if sd.create_from_inf(args.file):
  File "/usr/lib/python3.6/site-packages/lib389/instance/setup.py", line 534, in create_from_inf
    self.create_from_args(general, slapd, backends, self.extra)
  File "/usr/lib/python3.6/site-packages/lib389/instance/setup.py", line 670, in create_from_args
    self._install_ds(general, slapd, backends)
  File "/usr/lib/python3.6/site-packages/lib389/instance/setup.py", line 808, in _install_ds
    self.log.debug(f"CMD: {args} ; STDOUT: {stdout} ; STDERR: {stderr}")
Message: 'CMD: systemctl enable dirsrv@localhost ; STDOUT:  ; STDERR: Created symlink /etc/systemd/system/multi-user.target.wants/dirsrv@localhost.service \u2192 /usr/lib/systemd/system/dirsrv@.service.\n'

As well, the full machine name is used, not "localhost" during the ldap connection, which causes the setup to fail to connect and do the final steps.


Will probably need to be applied to 1.4.2/1.4.3

Metadata Update from @firstyear:
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None

3 years ago

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.2

3 years ago

Metadata Update from @firstyear:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/4214

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: fixed)

3 years ago

Login to comment on this ticket.

Metadata