#49902 Failure to get hostname in cockpit
Closed: wontfix by spichugi. Opened by vashirov.

Issue Description

Cockpit 389-ds plugin implicitly depends on hostname command:

js/servers.js
1281:      cockpit.spawn(["hostname", "--fqdn"], { superuser: true, "err": "message" }).fail(function(ex) {

which might be missing in minimal installation environments (such as containers).

Package Version and Platform

master

Steps to reproduce

  1. Install cockpit-389-ds on a system without hostname package
  2. Try to create an instance

Actual results

Window appears with the title "Failed to get hostname!" and message "not-found"

Expected results

Either hostname should be a dependency or we should use hostnamectl status --static to get the hostname. hostnamectl is part of systemd and is available in minimal install.


Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4.0

Metadata Update from @mreynolds:
- Issue priority set to: normal
- Issue set to the milestone: 1.4.1 (was: 1.4.0)

https://pagure.io/389-ds-base/pull-request/50918 fixes the issue

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

Commit c013a028 fixes this issue

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/2961

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)

Metadata
Related Pull Requests