-
Notifications
You must be signed in to change notification settings - Fork 17
Open
Labels
bugProblem when deploying a Data Safe Haven.Problem when deploying a Data Safe Haven.
Description
✅ Checklist
- I have searched open and closed issues for duplicates.
- This is a problem observed when using a Data Safe Haven.
- I can reproduce this with the latest version.
- I have read through the documentation.
- This isn't an open-ended question (open a discussion if it is).
💻 System information
- Operating System: macOS
- Data Safe Haven version: v5.5.1
- Browser details: Google Chrome
🚫 Describe the problem
Users reported being unable to log into a workstation after successfully logging into Guacamole:
Containers involved in logging seemed up and running, and their DNS entries are accurate. When accessing the workstation via serial console. we discovered that nslcd had trouble resolving the name identity..... When using resolvectl status to check the workstation DNS configuration, we obtained the following:
Which is not the IP of the DNS Server used at the TRE:
🚂 Workarounds or solutions
We believe it's another consequence of issue #1802, that sadly is not addressed by #2442.
Redeploying the SRE doesn't not fix it. However, re-running cloud-init does. @craddm believes even a VM restart could fix it too.
Metadata
Metadata
Assignees
Labels
bugProblem when deploying a Data Safe Haven.Problem when deploying a Data Safe Haven.