privazio/ansible-collection-vdc

Fork 0

Temporal Failure in name resolution #115

New issue

Closed

opened 2021-03-22 10:34:39 +00:00 by rafael · 4 comments

rafael commented

2021-03-22 10:34:39 +00:00

(Migrated from gitlab.privaz.io)

No description provided.

rafael commented

2021-03-22 10:36:24 +00:00

(Migrated from gitlab.privaz.io)

Not clear why happening in environment PVZ5
when comparing with PVZ4, the latter sets global DNS resolver in systemd-resolved

I am also suspicious of DNSMASq reading resolv.conf, which may trigger a loop.

Not clear why happening in environment PVZ5 when comparing with PVZ4, the latter sets global DNS resolver in systemd-resolved I am also suspicious of DNSMASq reading resolv.conf, which may trigger a loop.

rafael commented

2021-03-22 10:39:48 +00:00

(Migrated from gitlab.privaz.io)

Yes, after making some tests it is clear the adding no-resolv is required in the manager
also, setting up the global resolver

Yes, after making some tests it is clear the adding no-resolv is required in the manager also, setting up the global resolver

rafael commented

2021-03-22 10:50:04 +00:00

(Migrated from gitlab.privaz.io)

mentioned in commit a853280d9c

mentioned in commit a853280d9cdb28ffa998711f58bd67d730f7f393

rafael commented

2021-03-22 15:34:40 +00:00

(Migrated from gitlab.privaz.io)

also, it turns out that the lxd package conflicts with vrack-dnsmasq.

this is being managed from the node bootstraping

also, it turns out that the lxd package conflicts with vrack-dnsmasq. this is being managed from the node bootstraping

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

2021-03-22 15:36:14 +00:00

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

privazio/ansible-collection-vdc#115

No description provided.

Rows
Columns