--- Begin Message ---
Hi Leandro,

So if you can't schedule a downtime for, at least, some VMs i would add a 3rd Box. Also in terms of having a valid Quorum a 3rd Box would be a good thing.

About the Upgrade, as Alain pointed out, there is no way to accidentially upgrade, at least if you don't put "bullseye" in the sources.list manually (like you did, that's why i asked about the Upgrade). So just make shure you explicitly use "buster", not "stable" or "bullseye" in the Debian repo. If apt still complains about the release change just run an update using "apt-get update --allow-releaseinfo-change", this should fix things you. If you already upgraded some packages from the bullseye repo i would keep things running as they are for now (obviously nothing broke by now, so don't touch it...) and start planning the Upgrade to 7.0. The Upgrade to 7.0 was hassle free for the Clusters i ran it by now. Also telling from Forum and Mailing Lists, i wouldn't expect any issues as long as you don't have any special setups with PCI passthrough Devices or something like that.

Best
Martin

Am 24.08.21 um 17:13 schrieb Leandro Roggerone:
Hello , Martin.
Im still in pve 6.04.
I was looking at the document you pointed out (Upgrade from 6.x to 7.0)
It is frustrating to see that upgrading  is a very difficult process.
My cluster contains 2 servers.
Both are in production , at 50 - 60 % storage and memory capacity so it is not easy for me to create backups and move VMs.

I will study how to proceed with this update from pve 6  to 7.
Perhaps:
Adding a third new box already running version 7.
Adding a networking storage ? need to check out wich one.

Meanwhile , until I can go to pve 7 , I think I should upgrate to latest pve 6 and disable automatic upgrades ...
Do you think it is ok ?

Thanks for your words!!
Leandro.


El mié, 18 ago 2021 a las 14:58, Martin Holub (<[email protected] <mailto:[email protected]>>) escribió:

    Hi Leandro,

    Are you already on PVE7? Otherwise, just changing the Sources to
    Bullseye, i'm pretty shure that this will break things, or at
    least produce unwanted results. If you want to upgrade to Debian
    Bullseye better check
    https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
    <https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0>

    Best regards
    Martin

    Am 18.08.21 um 15:19 schrieb Leandro Roggerone:
    thanks Martin.
    According to documentation , for a non subscription
    environment ,this is how it should looks like:

    root@pve:/etc/apt# cat /etc/apt/sources.list
    deb http://ftp.debian.org/debian <http://ftp.debian.org/debian>
    bullseye main contrib

    deb http://ftp.debian.org/debian <http://ftp.debian.org/debian>
    bullseye-updates main contrib

    # security updates
    deb http://security.debian.org/debian-security
    <http://security.debian.org/debian-security> bullseye-security
    main contrib

    After running apt-get update from cli , it did not return any error.
    seems to be working ok now.
    Thanks again.
    Leandro.

    El mar, 17 ago 2021 a las 11:44, Martin Holub via pve-user
    (<[email protected]
    <mailto:[email protected]>>) escribió:




        ---------- Forwarded message ----------
        From: Martin Holub <[email protected]
        <mailto:[email protected]>>
        To: [email protected]
        <mailto:[email protected]>
        Cc:
        Bcc:
        Date: Tue, 17 Aug 2021 16:43:30 +0200
        Subject: Re: [PVE-User] (no subject)
        Hi,

        On Aug 14th "Bullseye" was released, therefore Buster moved from
        "stable" to "oldstable" and Bullseye became the new "stable"
        Version of
        Debian.

        Cheers.
        Martin

        Am 17.08.21 um 16:37 schrieb Leandro Roggerone:
        > root@pve:~# apt-get update
        > Get:1 http://security.debian.org
        <http://security.debian.org> buster/updates InRelease [65.4 kB]
        > Get:2 http://ftp.debian.org/debian
        <http://ftp.debian.org/debian> buster InRelease [122 kB]
        > Get:3 http://ftp.debian.org/debian
        <http://ftp.debian.org/debian> buster-updates InRelease [51.9 kB]
        > Reading package lists... Done
        >
        >
        > E: Repository 'http://security.debian.org
        <http://security.debian.org> buster/updates InRelease' changed
        > its 'Suite' value from 'stable' to 'oldstable'
        > N: This must be accepted explicitly before updates for this
        repository can
        > be applied. See apt-secure(8) manpage for details.
        > E: Repository 'http://ftp.debian.org/debian
        <http://ftp.debian.org/debian> buster InRelease' changed its
        > 'Suite' value from 'stable' to 'oldstable'
        > N: This must be accepted explicitly before updates for this
        repository can
        > be applied. See apt-secure(8) manpage for details.
        > E: Repository 'http://ftp.debian.org/debian
        <http://ftp.debian.org/debian> buster-updates InRelease'
        > changed its 'Suite' value from 'stable-updates' to
        'oldstable-updates'
        > N: This must be accepted explicitly before updates for this
        repository can
        > be applied. See apt-secure(8) manpage for details.
        >
        > This is my source.list
        > root@pve:~# cat /etc/apt/sources.list
        > deb http://ftp.debian.org/debian
        <http://ftp.debian.org/debian> buster main contrib
        >
        > deb http://ftp.debian.org/debian
        <http://ftp.debian.org/debian> buster-updates main contrib
        >
        > # security updates
        > deb http://security.debian.org <http://security.debian.org>
        buster/updates main contrib
        >
        > This was working ok until sat 14.
        > Any idea ?
        > Thanks!
        >
        >
        
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
        
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>>
        > Libre
        > de virus. www.avast.com <http://www.avast.com>
        >
        
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
        
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>>
        > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
        > _______________________________________________
        > pve-user mailing list
        > [email protected] <mailto:[email protected]>
        > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
        <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>
        >




        ---------- Forwarded message ----------
        From: Martin Holub via pve-user <[email protected]
        <mailto:[email protected]>>
        To: [email protected]
        <mailto:[email protected]>
        Cc: Martin Holub <[email protected] <mailto:[email protected]>>
        Bcc:
        Date: Tue, 17 Aug 2021 16:43:30 +0200
        Subject: Re: [PVE-User] (no subject)
        _______________________________________________
        pve-user mailing list
        [email protected] <mailto:[email protected]>
        https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
        <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>


    
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
        Libre de virus. www.avast.com
    
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>



--- End Message ---
_______________________________________________
pve-user mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Reply via email to