ubuntu-389-directory-server team mailing list archive

[Nick Rosbrook <2008441@xxxxxxxxxxxxxxxxxx>]

Hello Kelvin, or anyone else affected,

Accepted 389-ds-base into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/389-ds-
base/2.0.15-1ubuntu2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: 389-ds-base (Ubuntu Jammy)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
389 Directory Server, which is subscribed to 389-ds-base in Ubuntu.
https://bugs.launchpad.net/bugs/2008441

Title:
  389 Directory Server Manager not show even cockpit-389-ds is installed

Status in 389-ds-base package in Ubuntu:
  Fix Released
Status in 389-ds-base source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  Part of the UI (389 directory server) is missing from the cockpit menu on the affected versions. The UI files are not being build, they are not packaged in the affected version.
  The workaround would be to build those files externally and manually place them where the UI expects them to be.

  [ Test Plan ]

  1. Install the following packages on a fresh installation of Jammy
   - 389-ds
   - cockpit
   - cockpit-389-ds

  2. Ensure that cockpit is enabled and listening on port 9090

  3. Open a browser and connect to the system on port 9090

  4. Login to the cockpit web application

  5. Verify that the menu on the left includes the 389 Directory Server
  link

  6. Click the link and use the plugin to create a new instance of
  389-ds

  [ Where problems could occur ]

  While issues are unlikely, there are a number of places where bug
  fixes include minor changes to the cockpit UI. If users rely on
  scripts for automated testing/automation (e.g. selenium), these
  changes could cause those tests/automations could break.

  [ Other Info ]

   * This change only applies to jammy as releases after jammy have a newer
     version of 389-ds-base that includes the missing files

  [ Original Bug Description ]

  In 22.04 LTS, cockpit-389-ds will also install when install 389-ds

  ```
  # apt info 389-ds
  Package: 389-ds
  Version: 2.0.15-1
  Priority: optional
  Section: universe/net
  Source: 389-ds-base
  Origin: Ubuntu
  Maintainer: Ubuntu Developers <ubuntu-devel-discuss@xxxxxxxxxxxxxxxx>
  Original-Maintainer: Debian FreeIPA Team <pkg-freeipa-devel@xxxxxxxxxxxxxxxxxxxxxxx>
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 49.2 kB
  Depends: 389-ds-base, cockpit-389-ds
  Homepage: https://directory.fedoraproject.org
  Download-Size: 10.8 kB
  APT-Manual-Installed: yes
  APT-Sources: http://azure.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  Description: 389 Directory Server suite - metapackage
   Based on the Lightweight Directory Access Protocol (LDAP), the 389
   Directory Server is designed to manage large directories of users and
   resources robustly and scalably.
   .
   This is a metapackage depending on the LDAPv3 server and a Cockpit UI plugin
   for administration.
  ```

  After cockpit-389-ds install, 389 Directory Server suppose could be
  administrated via Cockpit but "389 Directory Server" does not shown
  after login Cockpit.

  After check the files installed via cockpit-389-ds, it seems missing
  some files inside /usr/share/cockpit/389-console such as
  /usr/share/cockpit/389-console/manifest.json,
  /usr/share/cockpit/389-console/index.html, etc.

  ```
  # dpkg --listfiles cockpit-389-ds
  /.
  /usr
  /usr/share
  /usr/share/cockpit
  /usr/share/cockpit/389-console
  /usr/share/doc
  /usr/share/doc/cockpit-389-ds
  /usr/share/doc/cockpit-389-ds/copyright
  /usr/share/metainfo
  /usr/share/metainfo/389-console
  /usr/share/metainfo/389-console/org.port389.cockpit_console.metainfo.xml
  /usr/share/doc/cockpit-389-ds/changelog.Debian.gz
  ```

  Thank you for your time!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/389-ds-base/+bug/2008441/+subscriptions