Bug 1859288 - add version information for 389-ds-base and RHDS to cli and cockpit
Summary: add version information for 389-ds-base and RHDS to cli and cockpit
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: 389-ds-base
Version: 11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DS11.2
: dirsrv-11.2
Assignee: mreynolds
QA Contact: RHDS QE
Marc Muehlfeld
URL:
Whiteboard: sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-21 15:56 UTC by mreynolds
Modified: 2021-11-10 14:54 UTC (History)
4 users (show)

Fixed In Version: redhat-ds-11-8030020210304204141-0b92cc7b
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-19 09:54:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 4258 0 None closed add version information for 389-ds-base and RHDS to cli and cockpit 2021-01-29 14:06:11 UTC
Red Hat Product Errata RHSA-2021:1243 0 None None None 2021-04-19 09:55:08 UTC

Description mreynolds 2020-07-21 15:56:31 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/389-ds-base/issue/51205

#### Issue Description

add missing package version and/or product information , that can be used from cli and web UI/cockpit

for example, with PKI ( the version numbers are just string pattern examples), we have:

equivalent of 389-ds-base:

cat /usr/share/pki/VERSION
Name: pki
Specification-Version: 10.5
Implementation-Version: 10.5.17

rpm -qf /usr/share/pki/VERSION
pki-base-10.5.17-6.el7.noarch


equivalent of RHDS:

cat /usr/share/pki/CS_SERVER_VERSION
Red Hat Certificate System 9.4 (Batch Update 2)

example of XML status:
curl http://`hostname -f`:8080/ca/admin/ca/getStatus
<?xml version="1.0" encoding="UTF-8" standalone="no"?><XMLResponse><State>1</State><Type>CA</Type><Status>running</Status><Version>10.5.17-6.el7</Version></XMLResponse>


then, in cockpit, we could have in the 389-ds or RHDS landing page:
https://`hostname -f`:9090/389-console

the version info, may be either
  LDAP server runing 389-ds-xxx
or
  Red Hat® Directory Server 11.1
with a link (and logo?) to respective project landing pages

and a status?
( from dsctl -l  and dsctl [all-instances] status ? )


#### Package Version and Platform



#### Steps to reproduce

1.
2.
3.

#### Actual results



#### Expected results

Comment 1 mreynolds 2020-09-23 13:00:12 UTC
Upstream ticket:

https://github.com/389ds/389-ds-base/issues/4258

Comment 4 sgouvern 2021-03-12 10:17:21 UTC
With :
cockpit-389-ds-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.noarch
389-ds-base-1.4.3.21-2.module+el8dsrv+10309+dd9f990e.x86_64


# dsconf slapd-inst1 monitor server
dn: cn=monitor
version: 389-Directory/1.4.3.21 B2021.070.2326
...


On the console :
Monitoring Tab / Server Statistics / Server Information Tab : 
a 'Version' field shows : 389-Directory/1.4.3.21 B2021.070.2326

Marking as verified

Comment 5 Marc Muehlfeld 2021-03-22 12:30:30 UTC
Should I write a release note for 8.3 about this enhancement?
Might be interesting for our customers.

Comment 7 errata-xmlrpc 2021-04-19 09:54:31 UTC
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 (Moderate: redhat-ds:11 security and bug fix update), 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-2021:1243


Note You need to log in before you can comment on or make changes to this bug.