This commit is contained in:
forgejo-actions 2026-10-17 14:15:36 +00:00
commit ce7f373620
10 changed files with 201 additions and 47 deletions

View file

@ -344,6 +344,7 @@
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-ressource-part-en-error-juste-apres-le-202">La ressource part en <code class="docutils literal notranslate"><span class="pre">error</span></code> juste après le 202</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-demarre-mais-n-a-pas-d-adresse">La VM démarre mais n’a pas d’adresse</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-joint-pas-sa-gateway-subnet-vxlan">La VM ne joint pas sa gateway (subnet <code class="docutils literal notranslate"><span class="pre">vxlan</span></code>)</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-a-une-adresse-mais-cloud-init-n-applique-rien">La VM a une adresse mais cloud-init n’applique rien</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#le-user-data-est-servi-vide">Le user-data est servi vide</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-demarre-pas-uefi">La VM ne démarre pas (UEFI)</a></li>
@ -413,6 +414,34 @@ la MAC n’est pas réservée — l’ordre <code class="docutils literal notran
<p>Si le serveur ne voit passer aucune requête, le problème est en amont : tap absent, bridge non
raccordé, VM dans le mauvais netns.</p>
</section>
<section id="la-vm-ne-joint-pas-sa-gateway-subnet-vxlan">
<h2>La VM ne joint pas sa gateway (subnet <code class="docutils literal notranslate"><span class="pre">vxlan</span></code>)<a class="headerlink" href="#la-vm-ne-joint-pas-sa-gateway-subnet-vxlan" title="Lien vers cette rubrique">#</a></h2>
<p>La gateway d’un subnet <code class="docutils literal notranslate"><span class="pre">vxlan</span></code> est un macvlan <code class="docutils literal notranslate"><span class="pre">gw-&lt;subnet&gt;</span></code> à MAC anycast
(<a class="reference internal" href="../concepts/modes-reseau.html"><span class="doc">Modes réseau</span></a>). Le watchdog contrôle sa présence, sa MAC, les adresses et l’entrée
FDB : ses notifications (<code class="docutils literal notranslate"><span class="pre">interface</span> <span class="pre">gw-…</span></code>, <code class="docutils literal notranslate"><span class="pre">lacks</span> <span class="pre">the</span> <span class="pre">gateway</span> <span class="pre">address</span></code>, <code class="docutils literal notranslate"><span class="pre">no</span> <span class="pre">local</span> <span class="pre">fdb</span>
<span class="pre">entry</span></code>…) disent déjà ce qui manque. À la main, dans le netns du VPC :</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># macvlan actif, MAC 02:01:00:&lt;VNI&gt;, gateway en /32 ; adresse d'émission seule sur le bridge</span>
ip<span class="w"> </span>-n<span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>-br<span class="w"> </span>addr<span class="w"> </span>show<span class="w"> </span>gw-&lt;subnet&gt;
ip<span class="w"> </span>-n<span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>-br<span class="w"> </span>addr<span class="w"> </span>show<span class="w"> </span>br-&lt;subnet&gt;
<span class="c1"># entrée locale de la MAC anycast dans le bridge (« master br-&lt;subnet&gt; permanent »)</span>
ip<span class="w"> </span>netns<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>bridge<span class="w"> </span>fdb<span class="w"> </span>show<span class="w"> </span>br<span class="w"> </span>br-&lt;subnet&gt;<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span><span class="m">02</span>:01:00
<span class="c1"># route du subnet émise depuis la gateway</span>
ip<span class="w"> </span>-n<span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>-4<span class="w"> </span>route<span class="w"> </span>show<span class="w"> </span>dev<span class="w"> </span>br-&lt;subnet&gt;
<span class="c1"># confinement : source anycast rejetée sur le veth du subnet</span>
ip<span class="w"> </span>netns<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>ebtables<span class="w"> </span>-t<span class="w"> </span>nat<span class="w"> </span>-L<span class="w"> </span>PREROUTING
ip<span class="w"> </span>netns<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>ebtables<span class="w"> </span>-L<span class="w"> </span>FORWARD
</pre></div>
</div>
<p>Dans le guest, <code class="docutils literal notranslate"><span class="pre">ip</span> <span class="pre">neigh</span> <span class="pre">show</span> <span class="pre">&lt;gateway&gt;</span></code> doit montrer la MAC <code class="docutils literal notranslate"><span class="pre">02:01:00:&lt;VNI&gt;</span></code>. Une autre MAC —
celle d’un hôte, <code class="docutils literal notranslate"><span class="pre">02:03:…</span></code> — signale un subnet de l’ancien modèle (sans <code class="docutils literal notranslate"><span class="pre">relay_ip</span></code>) ou une
gateway posée sur le bridge.</p>
<p>Depuis le netns d’un hôte, une VM d’un <strong>autre</strong> hôte ne répond qu’à l’adresse d’émission :
<code class="docutils literal notranslate"><span class="pre">ip</span> <span class="pre">netns</span> <span class="pre">exec</span> <span class="pre">&lt;vpc&gt;</span> <span class="pre">ping</span> <span class="pre">-I</span> <span class="pre">&lt;relay_ip&gt;</span> <span class="pre">&lt;ip&gt;</span></code>. Un ping sans <code class="docutils literal notranslate"><span class="pre">-I</span></code> part de la gateway et la
réponse revient à l’hôte de la VM — ce n’est pas une panne.</p>
</section>
<section id="la-vm-a-une-adresse-mais-cloud-init-n-applique-rien">
<h2>La VM a une adresse mais cloud-init n’applique rien<a class="headerlink" href="#la-vm-a-une-adresse-mais-cloud-init-n-applique-rien" title="Lien vers cette rubrique">#</a></h2>
<p>Deux causes distinctes, à écarter dans cet ordre.</p>
@ -531,6 +560,7 @@ l’agent n’est plus piloté par lui.</p>
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-ressource-part-en-error-juste-apres-le-202">La ressource part en <code class="docutils literal notranslate"><span class="pre">error</span></code> juste après le 202</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-demarre-mais-n-a-pas-d-adresse">La VM démarre mais n’a pas d’adresse</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-joint-pas-sa-gateway-subnet-vxlan">La VM ne joint pas sa gateway (subnet <code class="docutils literal notranslate"><span class="pre">vxlan</span></code>)</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-a-une-adresse-mais-cloud-init-n-applique-rien">La VM a une adresse mais cloud-init n’applique rien</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#le-user-data-est-servi-vide">Le user-data est servi vide</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-demarre-pas-uefi">La VM ne démarre pas (UEFI)</a></li>