This message was deleted.
# puppet-enterprise
s
This message was deleted.
t
console-services.log:
Copy code
qtp406947619-448] ERROR [p.p.r.ds] Failed request to get directory server settings via GET /api/rbac/ds. Status code:  500, Message: {:kind "puppetlabs.rbac/server-error", :msg "An uncaught server error was thrown. Check the log for details."}
system was installed using recover from backup. secrets have been copied, services have been restarted.
old puppetserver had ldap connection configured.
its a different parameter
but the solution to dump and reimport the ds settings may help you?
maybe try to blank it out
t
Dump worked (on old server)
Tranferred ds.txt file to new server.
Runnning test produces an error:
error: ds_pw_obfuscated: disallowed-key
m
im just sort of spitballing here,
but try removing that key from the file and importing it
t
Ho do we blank out LDAP config? WebUI not working.
m
edit the ds file manually then post it in
t
removed the key. test work.
post not working.
psql exception: wrong key or data
m
the format of the file must ave change significantly in these versions,
i can maybe get you ablank one from the same version in my lab?
you would have to reconfigure LDAP in the UI
t
not possible. ldap is empty with an error message.
we followed the pe backup and restore procedure, including back and restore of the secrets.
m
yeah im in break fix mode here, there is obviously a bug here
t
should we file a support ticket?
How can we empty the ldap config, so that we can configure LDAP using the WebUI?
m
I would file a ticket
im thinking the most likey solution is to post in an empty “template” ds file
but this is new and unique and worth a ticket
j
There are database migrations from the old version to the new version, and the keys are now encrypted. The easiest way is to delete the corresponding table rows and put all the DS settings back in manually.
You may be able to use https://puppet.com/docs/pe/2021.7/rbac_api_v1_directory.html#put_ds with an empty payload
{}
to reset it as well.
t
Issue was solved by the customer. Documentation needs an update that the orchestration services also has a secrets key which must also be transferred to the new server.