FD.io Nomad Issue


Vanessa Valderrama
 

Jenkins has been restarted and jobs are running again.

We got approval to the Gerrit resize at the time so next week's
maintenance will be cancelled.

Thank you,

Vanessa

On 10/29/20 1:33 PM, Vanessa Valderrama wrote:
The community has requested a restart of Jenkins. We're placing Jenkins
in shutdown mode to prepare for the restart.

Thank you,

Vanessa

On 10/29/20 11:26 AM, Vanessa Valderrama wrote:
Nomad executors are not starting in Jenkins. This was due to the DNS for
the Nomad URL in Jenkins which is configured to use
nomad.fdiopoc.net:4646 pointing to the wrong IP address.

; <<>> DiG 9.11.14-RedHat-9.11.14-2.fc30 <<>> nomad.fdiopoc.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22624
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nomad.fdiopoc.net.        IN    A
;; ANSWER SECTION:
nomad.fdiopoc.net.    180    IN    A    157.230.67.179
;; Query time: 38 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Oct 29 09:55:49 CDT 2020
;; MSG SIZE  rcvd: 62

We tried hard-coding the Nomad URL to the IP address 10.30.51.32:4646
and 10.39.51.33:4646. Unfortunately that is not resolving the issue.

We will continue to work with the community to resolve this issue as
quickly as possible.

Thank you,
Vanessa


Vanessa Valderrama
 

The community has requested a restart of Jenkins. We're placing Jenkins
in shutdown mode to prepare for the restart.

Thank you,

Vanessa

On 10/29/20 11:26 AM, Vanessa Valderrama wrote:
Nomad executors are not starting in Jenkins. This was due to the DNS for
the Nomad URL in Jenkins which is configured to use
nomad.fdiopoc.net:4646 pointing to the wrong IP address.

; <<>> DiG 9.11.14-RedHat-9.11.14-2.fc30 <<>> nomad.fdiopoc.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22624
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nomad.fdiopoc.net.        IN    A
;; ANSWER SECTION:
nomad.fdiopoc.net.    180    IN    A    157.230.67.179
;; Query time: 38 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Oct 29 09:55:49 CDT 2020
;; MSG SIZE  rcvd: 62

We tried hard-coding the Nomad URL to the IP address 10.30.51.32:4646
and 10.39.51.33:4646. Unfortunately that is not resolving the issue.

We will continue to work with the community to resolve this issue as
quickly as possible.

Thank you,
Vanessa


Vanessa Valderrama
 

Nomad executors are not starting in Jenkins. This was due to the DNS for
the Nomad URL in Jenkins which is configured to use
nomad.fdiopoc.net:4646 pointing to the wrong IP address.

; <<>> DiG 9.11.14-RedHat-9.11.14-2.fc30 <<>> nomad.fdiopoc.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22624
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;nomad.fdiopoc.net.        IN    A
;; ANSWER SECTION:
nomad.fdiopoc.net.    180    IN    A    157.230.67.179
;; Query time: 38 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Oct 29 09:55:49 CDT 2020
;; MSG SIZE  rcvd: 62

We tried hard-coding the Nomad URL to the IP address 10.30.51.32:4646
and 10.39.51.33:4646. Unfortunately that is not resolving the issue.

We will continue to work with the community to resolve this issue as
quickly as possible.

Thank you,
Vanessa