From: Joseph John <jjk.saji@gmail.com>
To: alain.pean@c2n.upsaclay.fr,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Proxmox 6.3.3 upgrade [ Out of 4 node cluster, can I only upgrade one only to the next stable release ]
Date: Thu, 24 Nov 2022 11:22:38 +0400 [thread overview]
Message-ID: <CAKeuxjAa5c9-ON4p9Ma_aYDLCLpaKE11QDdzBHTGh0dhjkCOeQ@mail.gmail.com> (raw)
In-Reply-To: <e59c908a-2364-054e-20f8-1a230cbcc1da@c2n.upsaclay.fr>
Dear Alain
Thanks for the mail
It works for 6.X , I tested
I have now 4 clustered instance , 2 of them 6.3.3 and 2 of them 6.4-15
I have done migration testing from 6.3.3. to to 6.4-15 and vise verse
Like to add that all this system were in 6.X range
I have not update to 7, will be doing it and results I will post to the
group
Thanks
Joseph John
On Fri, Nov 18, 2022 at 1:13 PM Alain Péan <alain.pean@c2n.upsaclay.fr>
wrote:
> Le 18/11/2022 à 08:54, Mark Schouten via pve-user a écrit :
> > This should work just fine, at least for a while.
>
> I can add that migration of VMs between the new node, and the old nodes
> will not work until the old nodes are also upgraded.
>
> Alain
>
> --
> Administrateur Système/Réseau
> C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
> Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
> Tel : 01-70-27-06-88 Bureau A255
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2022-11-24 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 6:05 Joseph John
[not found] ` <mailman.105.1668758104.284.pve-user@lists.proxmox.com>
2022-11-18 9:07 ` Alain Péan
2022-11-24 7:22 ` Joseph John [this message]
2022-11-25 1:25 ` Joseph John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKeuxjAa5c9-ON4p9Ma_aYDLCLpaKE11QDdzBHTGh0dhjkCOeQ@mail.gmail.com \
--to=jjk.saji@gmail.com \
--cc=alain.pean@c2n.upsaclay.fr \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.