Actions
Bug #7151
closed
Name resolution in rudder-vagrant is sometimes quite faulty
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When using Rudder-vagrant, the name resolutino can be completly broken (depending on the dns of the host system), which result to nodes that can't fetch their promises; which misses completly the point of having a simple system for testing.
I'll backport the network part from RTF, which does work perfectly well (fixing resolv.conf and /etc/hosts)
Updated by Nicolas CHARLES about 9 years ago
- Status changed from New to Pending technical review
- Assignee changed from Nicolas CHARLES to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-vagrant/pull/13
Updated by Nicolas CHARLES about 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder-vagrant|2f9fb6b08082fa03ea121777db0bd5c0316688ff.
Updated by Benoît PECCATTE about 9 years ago
Applied in changeset rudder-vagrant|93290dbc276d792aa86653b0570eaa2d42e004fa.
Updated by Alexis Mousset almost 9 years ago
- Has duplicate Bug #7087: Vagrant demo broken with 3.1 added
Updated by Benoît PECCATTE about 8 years ago
- Status changed from Pending release to Released
Actions