From: "Luis G. Coralle" <luiscoralle@fi.uncoma.edu.ar>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Problem with backup
Date: Wed, 23 Feb 2022 23:45:59 -0300 [thread overview]
Message-ID: <CAG+yBPTatOB1=ptBgDBHfi__6Tt1fG1bnsQFOmFFV03gsg+MJA@mail.gmail.com> (raw)
In-Reply-To: <mailman.218.1645612928.456.pve-user@lists.proxmox.com>
Hi, the problem was that one VM had mounted a non-existent .iso image.
El mié, 23 feb 2022 a la(s) 07:42, Eneko Lacunza via pve-user (
pve-user@lists.proxmox.com) escribió:
>
>
>
> ---------- Forwarded message ----------
> From: Eneko Lacunza <elacunza@binovo.es>
> To: pve-user@lists.proxmox.com
> Cc:
> Bcc:
> Date: Wed, 23 Feb 2022 11:41:29 +0100
> Subject: Re: [PVE-User] Problem with backup
> Try refreshing Web interface. All nodes are upgraded to 7.1?
>
> El 23/2/22 a las 3:03, Luis G. Coralle escribió:
> > I have a 5 nodes cluster with proxmox pve 7.1-10.
> > I have problem when I start a backup on a shared NFS backup storage, it
> > shows the following message:
> >
> >
> > Some errors have been encountered:
> >> pve5: Parameter verification failed. (400)
> >
> > *next-run*: property is not defined in schema and the schema does not
> allow
> >> additional properties
> >> *schedule*: property is not defined in schema and the schema does not
> >> allow additional properties
> >> *type*: property is not defined in schema and the schema does not allow
> >> additional prope
> >
> >
> >
> > Has it happen anyone?
> >
>
> Eneko Lacunza
> Zuzendari teknikoa | Director técnico
> Binovo IT Human Project
>
> Tel. +34 943 569 206 |https://www.binovo.es
> Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
>
> https://www.youtube.com/user/CANALBINOVO
> https://www.linkedin.com/company/37269706/
>
>
>
> ---------- Forwarded message ----------
> From: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com>
> To: pve-user@lists.proxmox.com
> Cc: Eneko Lacunza <elacunza@binovo.es>
> Bcc:
> Date: Wed, 23 Feb 2022 11:41:29 +0100
> Subject: Re: [PVE-User] Problem with backup
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
--
Luis G. Coralle
Secretaría de TIC
Facultad de Informática
Universidad Nacional del Comahue
(+54) 299-4490300 Int 647
prev parent reply other threads:[~2022-02-24 2:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 2:03 Luis G. Coralle
[not found] ` <mailman.218.1645612928.456.pve-user@lists.proxmox.com>
2022-02-24 2:45 ` Luis G. Coralle [this message]
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='CAG+yBPTatOB1=ptBgDBHfi__6Tt1fG1bnsQFOmFFV03gsg+MJA@mail.gmail.com' \
--to=luiscoralle@fi.uncoma.edu.ar \
--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.