Yes, it was already a bit late therefore the "still not helpful" was meant to be
"the log output is still not helpful", sorry for that. So for me it's not
"/etc/ipa/server.conf" but "/etc/ipa/default.conf". Debug mode is on,
I see the extra debug log but no new findings through that.
Is there something "hidden" a rpm plugin is doing compared to manually creating
the files at the specific locations and running ipa-server-install? I wan't to avoid
creating a plugin all the time as I'm currently simply refactoring, trying out.
I've done the following on the VM (all files updated with the latest insights):
executed: "ipa-server-install --uninstall"
updated the three .js files (postfixbook.js, mailalias.js, mailenabled.js) in
"/usr/share/ipa/ui/js/plugins/postfixbook"
updated their two python files in
"/usr/lib/python3.6/site-packages/ipaserver/plugins"
updated the schema file (75-postfix-book-schema.ldif) in
"/usr/share/ipa/schema.d"
executed: "ipa-server-install"
The ipaserver-install log shows:
2022-06-04T12:10:57Z DEBUG [7/11]: updating schema
2022-06-04T12:10:57Z DEBUG Processing schema LDIF file
/usr/share/ipa/schema.d/75-postfix-book-schema.ldif
2022-06-04T12:10:57Z DEBUG Not updating schema
2022-06-04T12:10:57Z DEBUG step duration: dirsrv __update_schema 0.21 sec
2022-06-04T12:10:57Z DEBUG [8/11]: upgrading server
So it says already "Not updating schema". I even run
"ipa-server-upgrade" but it simply doesn't care about the schema, as it
seems.
When I execute
ldapsearch -o ldif-wrap=no -D 'cn=Directory Manager' -W -x -s base -b
'cn=schema' objectclasses | grep -I mail
ldapsearch -o ldif-wrap=no -D 'cn=Directory Manager' -W -x -s base -b
'cn=schema' attributetypes | grep -i mail
My attributeTypes and objectClasses are therefore missing. I. even reverted the schema
file back to the initial state and tried again, but same behaviour, it gets ignored. So
what is the plugin approach doing more than the manual approach?