ubuntu-389-directory-server team mailing list archive

[Mauricio Faria de Oliveira <2008441@xxxxxxxxxxxxxxxxxx>]

Apparently, the new changes FTBFS due to internet access or other issues.
The work on this continues in the background.

** Changed in: 389-ds-base (Ubuntu Jammy)
     Assignee: Tom Moyer (tom-tom) => Dariusz Gadomski (dgadomski)

-- 
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:
  Incomplete

Bug description:
  [ Impact ]

  It is expected that there will be minimal impact by this SRU. The only
  things that were added to the package were the missing Cockpit plugin
  files (in debian/cockpit_dist) and adding a line to debian/rules to
  copy those files into the correct location during the package build
  process. No other files outside of these were touched by this SRU.

  [ 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