• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • rhel-9.6
    • rhel-9.5
    • libdb
    • None
    • libdb-5.3.28-55.el9
    • No
    • None
    • sst_cs_apps
    • ssg_core_services
    • 10
    • 5
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None

      What were you trying to do that didn't work?

      I'm writing the leapp automation to convert pam_userdb database from BerkeleyDB to GDBM, but the convert_db utility doesn't fail on error. Thus, it is impossible to know whether automation has failed.

      What is the impact of this issue to you?

      Customers will upgrade to RHEL10, but the pam_userdb database won't be converted, thus they won't be able to connect if they are using this PAM module.

      How reproducible is this bug?:

      Always

      Steps to reproduce

      1. Create a corrupted/misbehaving database for pam_userdb.
      2. Run `convert_db`

      Expected results

      convert_db should fail and report the error.

      Actual results

      convert_db doesn't fail.

            fjanus@redhat.com Filip Janus
            ipedrosa@redhat.com Iker Pedrosa
            Filip Janus Filip Janus
            bot rhel-cs-apps-subsystem-qe bot rhel-cs-apps-subsystem-qe
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: