2024-09-25
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-703 |
|---|
|
2024-09-18
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-700 |
|---|
|
2024-07-01
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-628 |
|---|
|
2024-03-22
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-552 |
|---|
|
2023-06-01
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-246 |
|---|
|
2023-05-30
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-243 |
|---|
|
2023-05-26
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-242 |
|---|
|
2023-05-24
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-239 |
|---|
|
2023-05-19
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-238 |
|---|
|
2023-04-18
Status:
Reported: 2023-04-18 16:08:00 EST
Resolved: 04-21-2023 15:43:17 EST
See
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 5443b7f3-2f11-3f32-ba15-42d15098c09a |
|---|
| key | DSDW-225 |
|---|
|
2023-04-13
Status:
Reported: 2023-04-12 08:32:00 EST
...
David installed tailscale across all Denodo servers except solution manager as a means of connecting to our database in us-east-1. After turning off tailscale (tailscale down) across the denodo servers, Duo/LDAP connectivity was restored. David is going to test tailscale only on stage going forward, until he is confident it's able to work in dev and prod.
The specifics around the tailscale issue was that the denodo servers were not migrated to a new, functioning tailnet, and remained in a tailnet that was no longer functioning, hence the connectivity issues.
2023-04-12
Status:
Reported: 2023-04-12 09:12:00 EST
...