Project

General

Profile

Demande #5562

Migrer l'infra en Bullseye

Added by Quentin Gibeaux over 1 year ago. Updated 4 days ago.

Status:
Nouveau
Priority:
Normale
Assignee:
-
Category:
-
Target version:
Start date:
09/02/2021
Due date:
% Done:

91%

Estimated time:
(Total: 0.00 h)
Spent time:
(Total: 2.50 h)
Difficulté:
2 Facile

Description

Debian Bullseye est sorti, il faut migrer l'infra


Subtasks

Demande #5563: Migrer Guarana sur BullseyeFermépitchum .

Actions
Demande #5564: Migrer Galanga sur BullseyeFerméQuentin Gibeaux

Actions
Demande #5565: Migrer Virola sur BullseyeRésolu

Actions
Demande #5566: Migrer Calamus sur BullseyeRésoluQuentin Gibeaux

Actions
Demande #5567: Migrer bastion sur BullseyeRésoluFrançois Poulain

Actions
Demande #5568: Migrer admin sur BullseyeRésoluFrançois Poulain

Actions
Demande #5569: Migrer dns sur BullseyeRésoluQuentin Gibeaux

Actions
Demande #5570: Migrer mail sur BullseyeRésoluPierre-Louis Bonicoli

Actions
Demande #5571: Migrer sympa sur BullseyeRésoluPierre-Louis Bonicoli

Actions
Demande #5572: Migrer adl sur BullseyeRésoluFrançois Poulain

Actions
Demande #5573: Migrer lamp sur BullseyeRésoluQuentin Gibeaux

Actions
Demande #5574: Migrer agir sur BullseyeRésoluFrançois Poulain

Actions
Demande #5575: Migrer bots sur BullseyeFerméFrédéric Couchet

Actions
Demande #5576: Migrer dtc sur BullseyeNouveauBenjamin Drieu

Actions
Demande #5577: Migrer republique-numerique sur BullseyeFermépitchum .

Actions
Demande #5578: Migrer mumble sur BullseyeFerméQuentin Gibeaux

Actions
Demande #5579: Migrer candidatsfr sur BullseyeNouveauBenjamin Drieu

Actions
Demande #5580: Migrer pad sur BullseyeRésoluRomain H.

Actions
Demande #5581: Migrer scm sur BullseyeRésoluQuentin Gibeaux

Actions
Demande #5582: Migrer pouet BullseyeRésoluQuentin Gibeaux

Actions
Demande #5583: Migrer spip BullseyeRésoluFrançois Poulain

Actions
Demande #5589: Générer un nouveau dépot bullseye pour apt.april.orgRésoluQuentin Gibeaux

Actions
Demande #5590: Migrer vers Debian Bullseye la vm webchatRésoluRomain H.

Actions

Related issues

Related to Admins - Demande #3799: Migrer le parc des machines et VM vers Debian BusterFermé07/12/2019

Actions

History

#1

Updated by Christian P. Momon over 1 year ago

  • Related to Demande #3799: Migrer le parc des machines et VM vers Debian Buster added
#2

Updated by Christian P. Momon over 1 year ago

Quelques points relevés dans le fichier de release :

  • https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#security-archive
    5.1.3. Changed security archive layout
    
    For bullseye, the security suite is now named bullseye-security instead of codename/updates
    and users should adapt their APT source-list files accordingly when upgrading.
    
    The security line in your APT configuration may look like:
    
    deb https://deb.debian.org/debian-security bullseye-security main contrib
    
    If your APT configuration also involves pinning or APT::Default-Release, it is likely to require
    adjustments as the codename of the security archive no longer matches that of the regular archive.
    An example of a working APT::Default-Release line for bullseye looks like:
    
    APT::Default-Release "/^bullseye(|-security|-updates)$/";
    
    which takes advantage of the undocumented feature of APT that it supports regular expressions (inside /). 
    
  • https://www.debian.org/releases/bullseye/amd64/release-notes/ch-information.en.html#ssh-not-available
    5.1.23. No new SSH connections possible during upgrade
    
    Although existing Secure Shell (SSH) connections should continue to work through the upgrade as usual,
    due to unfortunate circumstances the period when new SSH connections cannot be established is longer than usual.
    If the upgrade is being carried out over an SSH connection which might be interrupted, it's recommended
    to upgrade openssh-server before upgrading the full system.
    
#5

Updated by François Poulain 9 months ago

Le temps de la migration, passage du protocol drbd en mode « A » :

Pour synchroniser la nouvelle conf :

# drbdadm --dry-run adjust virola
drbdsetup-84 net-options ipv4:172.16.0.252:7788 ipv4:172.16.0.251:7788 --set-defaults --max-epoch-size=8000 --max-buffers=8000 --cram-hmac-alg=sha1 --rr-conflict=disconnect --after-sb-2pri=disconnect --after-sb-1pri=consensus --after-sb-0pri=discard-younger-primary --protocol=A --shared-secret=wei8Aigithei3VeiNgaixing4siedeiz2Chohso1ieguemaiheeng9hik0ie 
# drbdadm adjust virola
# drbdadm adjust calamus

On voit le « A » avant le r----- :

# cat /proc/drbd 
version: 8.4.10 (api:1/proto:86-101)
srcversion: 473968AD625BA317874A57E 
 0: cs:Connected ro:Secondary/Primary ds:UpToDate/UpToDate A r-----
    ns:0 nr:1920182780 dw:1920182760 dr:0 al:0 bm:0 lo:2 pe:0 ua:0 ap:0 ep:1 wo:f oos:0
 1: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate A r-----
    ns:656795692 nr:0 dw:656794916 dr:1707361681 al:751973 bm:0 lo:1 pe:0 ua:0 ap:1 ep:1 wo:f oos:0

Also available in: Atom PDF