Skip to content
Jira Community Issue Sync

│ Error: Post "https://1C699EDDF386B763D5BB53DC0FFDB7AB.gr7.us-east-1.eks.amazonaws.com/api/v1/namespaces/kube-system/serviceaccounts": dial tcp: lookup 1C699EDDF386BBAGTHNJKMAC0FFDB7AB.gr7.us-east-1.eks.amazonaws.com on 00.00.000.00:53: no such host #1049

Sign in to view logs

│ Error: Post "https://1C699EDDF386B763D5BB53DC0FFDB7AB.gr7.us-east-1.eks.amazonaws.com/api/v1/namespaces/kube-system/serviceaccounts": dial tcp: lookup 1C699EDDF386BBAGTHNJKMAC0FFDB7AB.gr7.us-east-1.eks.amazonaws.com on 00.00.000.00:53: no such host

│ Error: Post "https://1C699EDDF386B763D5BB53DC0FFDB7AB.gr7.us-east-1.eks.amazonaws.com/api/v1/namespaces/kube-system/serviceaccounts": dial tcp: lookup 1C699EDDF386BBAGTHNJKMAC0FFDB7AB.gr7.us-east-1.eks.amazonaws.com on 00.00.000.00:53: no such host #1049

Triggered via issue July 8, 2024 18:05
@appilonappilon
commented on #2543 4d62449
Status Success
Total duration 22s
Artifacts –

jira_issues.yaml

on: issue_comment
Jira Community Issue sync
13s
Jira Community Issue sync
Fit to window
Zoom out
Zoom in

Annotations

1 warning
Jira Community Issue sync
The following actions uses Node.js version which is deprecated and will be forced to run on node20: atlassian/gajira-login@ca13f8850ea309cf44a6e4e0c49d9aa48ac3ca4c. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/