Bug 1791150

Summary: 389 Directory Server not showing as installed in cockpit/aplication.
Product: [Fedora] Fedora Reporter: Marcin Kozyra <marcink7440>
Component: cockpitAssignee: Marius Vollmer <mvollmer>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: chplee, dperpeet, ichavero, pasik, stefw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 18:06:44 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 Marcin Kozyra 2020-01-15 02:26:42 UTC
In cockpit/applications installing 389 Directory Server will not show it as installed.

After installation of 389 Directory Server I still see "Install" next to it. Pressing it again results in error stating 389 Directory Server is already installed.

Tried it on 2 systems, one of them being fresh install. All Fedoras 31

Comment 1 Martin Pitt 2020-01-16 09:24:25 UTC
In /usr/share/app-info/xmls/fedora.xml.gz the entry is

<component type="addon">
<id>org.port389.cockpit_console</id>
<pkgname>cockpit-389-ds</pkgname>
<source_pkgname>389-ds-base</source_pkgname>
<name>389 Directory Server</name>
<summary>389 Directory Server Management</summary>
<description><p>389 Directory Server is a highly usable, fully featured, reliable and secure LDAP server implementation. It handles many of the largest LDAP deployments in the world.</p></description>
<project_license>GPL-3.0+</project_license>
<url type="homepage">https://www.port389.org/</url>
<extends>org.cockpit_project.cockpit</extends>
<launchable type="cockpit-manifest">cockpit-389-console</launchable>
</component>

I clicked on "Install" on Cockpit's Applications page, which according to `pkcon get-transactions` installed the following:

 - installing python3-zipp-0.5.1-2.fc31.noarch
 - installing python3-importlib-metadata-0.23-1.fc31.noarch
 - installing python3-pluggy-0.12.0-2.fc31.noarch
 - installing python3-wcwidth-0.1.7-11.fc31.noarch
 - installing python3-py-1.8.0-2.fc31.noarch
 - installing python3-packaging-19.0-2.fc31.noarch
 - installing python3-more-itertools-7.2.0-1.fc31.noarch
 - installing python3-attrs-19.1.0-2.fc31.noarch
 - installing python3-atomicwrites-1.3.0-2.fc31.noarch
 - installing python3-pytest-4.6.9-1.fc31.noarch
 - installing python3-argparse-manpage-1.2.2-1.fc31.noarch
 - installing bash-completion-1:2.8-7.fc31.noarch
 - installing python3-lib389-1.4.2.5-3.fc31.noarch
 - installing cockpit-389-ds-1.4.2.5-3.fc31.noarch

So the package name seems to match, cockpit-389-ds is installed and /usr/share/metainfo/389-console/org.port389.cockpit_console.metainfo.xml is present. It also ships an apparently correct /usr/share/cockpit/389-console/manifest.json , I see "389 Directory Server" in the menu, and at least its initial screen works.

Reloading the page, and even restarting cockpit and packagekit doesn't help, so it's not just a bug with not picking up dynamic updates in the page.

OTOH this works correctly for subscription manager and cockpit-podman.

Marius, do you see what could be wrong here?

Comment 2 Ben Cotton 2020-11-03 16:10:44 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-11-24 18:06:44 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Chipeng Li 2023-08-09 21:08:38 UTC
Problem persists, Fedora 38.