privazio/ansible-collection-vdc

Fork 0

DNS failures during installation #47

New issue

Closed

opened 2020-08-15 06:03:00 +00:00 by rafael · 9 comments

rafael commented

2020-08-15 06:03:00 +00:00

(Migrated from gitlab.privaz.io)

Unable to resolve dl.openvm.eu

when downloading a template.

where is the error comming from?

a possibility is that the internal DNS is no resolving: 10.71.0.254, however, there is an option to bypass it:

however not entirely clear if the bypass affects also to the SVMs

Unable to resolve dl.openvm.eu when downloading a template. where is the error comming from? a possibility is that the internal DNS is no resolving: 10.71.0.254, however, there is an option to bypass it: however not entirely clear if the bypass affects also to the SVMs

rafael commented

2021-01-30 11:57:52 +00:00

(Migrated from gitlab.privaz.io)

changed title from {-ci test DNS should be a variable-} to {+DNS failures during installation+}

changed title from **{-ci test DNS should be a variable-}** to **{+DNS failures during installation+}**

rafael commented

2021-01-30 11:57:52 +00:00

(Migrated from gitlab.privaz.io)

changed the description

rafael commented

2021-01-30 12:36:21 +00:00

(Migrated from gitlab.privaz.io)

mentioned in issue #84

rafael commented

2021-01-30 12:37:41 +00:00

(Migrated from gitlab.privaz.io)

yes, it is expected to have DNS up in Management network

root@s-3-VM:~# cat /etc/resolv.conf 
nameserver 10.71.0.254
nameserver 10.20.0.1

the setting to bypass internal dns does not affect the SVMs

yes, it is expected to have DNS up in Management network ``` root@s-3-VM:~# cat /etc/resolv.conf nameserver 10.71.0.254 nameserver 10.20.0.1 ``` the setting to bypass internal dns does not affect the SVMs

rafael commented

2021-02-11 07:47:13 +00:00

(Migrated from gitlab.privaz.io)

mentioned in issue valletech/env/pvz3#3

rafael commented

2021-02-19 15:59:56 +00:00

(Migrated from gitlab.privaz.io)

the issue we are seeing is:

failed: [localhost] (item=debian-9-x86_64) => {"ansible_loop_var": "item", "api_http_method": "get", "api_key": "GQO1NpH3Y-oIiDVcxaxm9q7XE6kcRteiSpe5qkh-GLJcDO0fRVHK92VjNr3KMIShoP_fBUxPoyM7l4eK9mZmlw", "api_timeout": 30, "api_url": "https://vdc.test/client/api", "api_verify_ssl_cert": "../ca.crt", "attempts": 60, "changed": true, "item": "debian-9-x86_64", "msg": "Failed: 'The TEMPLATE has not been downloaded '", "zone": "z1"}

The console then states that was not able to resolve xxxx....

the issue we are seeing is: ``` failed: [localhost] (item=debian-9-x86_64) => {"ansible_loop_var": "item", "api_http_method": "get", "api_key": "GQO1NpH3Y-oIiDVcxaxm9q7XE6kcRteiSpe5qkh-GLJcDO0fRVHK92VjNr3KMIShoP_fBUxPoyM7l4eK9mZmlw", "api_timeout": 30, "api_url": "https://vdc.test/client/api", "api_verify_ssl_cert": "../ca.crt", "attempts": 60, "changed": true, "item": "debian-9-x86_64", "msg": "Failed: 'The TEMPLATE has not been downloaded '", "zone": "z1"} ``` The console then states that was not able to resolve xxxx....

rafael commented

2021-02-23 13:35:45 +00:00

(Migrated from gitlab.privaz.io)

Ferm resolution inside is also failing due to DNS:

syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse connection: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse timed: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse out;: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse no: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse servers: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse could: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse be: resolving to IPv4 address failed
syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse reached:

Connection timed out no servers could be reached

Ferm resolution inside is also failing due to DNS: ``` syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse connection: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse timed: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse out;: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse no: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse servers: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse could: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse be: resolving to IPv4 address failed syslog:Feb 23 06:36:15 manager ferm[27149]: ipset v6.34: Syntax error: cannot parse reached: ``` Connection timed out no servers could be reached

rafael commented

2021-02-23 14:15:18 +00:00

(Migrated from gitlab.privaz.io)

mentioned in merge request !147

rafael (Migrated from gitlab.privaz.io) closed this issue

2021-02-23 15:51:13 +00:00

rafael commented

2021-04-19 07:32:16 +00:00

(Migrated from gitlab.privaz.io)

mentioned in issue #117