From: Leandro Roggerone <leandro@tecnetmza.com.ar>
To: Martin Holub <martin@holub.co.at>
Cc: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] (no subject)
Date: Tue, 24 Aug 2021 12:13:03 -0300 [thread overview]
Message-ID: <CALt2oz5N_Wmp5K4JUxuC3cmVayEEfErVHPuM7sU8BU7TM_HOXQ@mail.gmail.com> (raw)
In-Reply-To: <e5a1f5ef-ab9b-9283-cd90-6aba6acc35ba@holub.co.at>
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 (<martin@holub.co.at>)
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
>
> 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 bullseye main contrib
>
> deb http://ftp.debian.org/debian bullseye-updates main contrib
>
> # security updates
> deb 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 (<
> pve-user@lists.proxmox.com>) escribió:
>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Martin Holub <martin@holub.co.at>
>> To: pve-user@lists.proxmox.com
>> 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 buster/updates InRelease [65.4 kB]
>> > Get:2 http://ftp.debian.org/debian buster InRelease [122 kB]
>> > Get:3 http://ftp.debian.org/debian buster-updates InRelease [51.9 kB]
>> > Reading package lists... Done
>> >
>> >
>> > E: Repository '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 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 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 buster main contrib
>> >
>> > deb http://ftp.debian.org/debian buster-updates main contrib
>> >
>> > # security updates
>> > deb 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
>> >
>> > 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
>> >
>> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>> > _______________________________________________
>> > pve-user mailing list
>> > pve-user@lists.proxmox.com
>> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>> >
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Martin Holub via pve-user <pve-user@lists.proxmox.com>
>> To: pve-user@lists.proxmox.com
>> Cc: Martin Holub <martin@holub.co.at>
>> Bcc:
>> Date: Tue, 17 Aug 2021 16:43:30 +0200
>> Subject: Re: [PVE-User] (no subject)
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> 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>
>
>
next prev parent reply other threads:[~2021-08-24 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 14:37 Leandro Roggerone
[not found] ` <mailman.458.1629211453.329.pve-user@lists.proxmox.com>
2021-08-18 13:19 ` Leandro Roggerone
[not found] ` <e5a1f5ef-ab9b-9283-cd90-6aba6acc35ba@holub.co.at>
2021-08-24 15:13 ` Leandro Roggerone [this message]
2021-08-24 15:36 ` Alain Péan
[not found] ` <1aca635b-412d-c199-2382-629b16457939@holub.co.at>
2021-08-25 12:11 ` Leandro Roggerone
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 23:11 Christian Karg
[not found] <CAGehcqHmTqfjBRwt61hWjjA1CQm8inajfS0=EOqCPrAdmGUheA@mail.gmail.com>
2023-07-24 8:58 ` Aaron Lauterer
2021-02-25 20:18 Aaron Wood
2021-02-26 11:17 ` Thomas Lamprecht
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=CALt2oz5N_Wmp5K4JUxuC3cmVayEEfErVHPuM7sU8BU7TM_HOXQ@mail.gmail.com \
--to=leandro@tecnetmza.com.ar \
--cc=martin@holub.co.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox