public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Filip Schauer <f.schauer@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox v2] fix #5946: rest-server: worker_task: detect task status on multi-line message
Date: Mon, 15 Sep 2025 21:37:08 +0200	[thread overview]
Message-ID: <b9f38b79-6f7d-4a82-80c5-e0406d3f2049@proxmox.com> (raw)
In-Reply-To: <20250811125839.267803-1-f.schauer@proxmox.com>

Am 11.08.25 um 14:58 schrieb Filip Schauer:
> Properly detect the status of a task when the last log message spans
> over multiple lines.
> 
> This fixes task status detection in Proxmox Backup Server when the
> directory creation task fails during creation of the partition on disk.
> With this fix the status becomes:
> 
> TaskState::Error { message: "command "sgdisk" "-n1" "-t1:8300"
> "/dev/sdc" failed - status code: 2 - Caution: invalid main GPT header,
> but valid backup; regenerating main header" }
> 
> instead of TaskState::Unknown.

I really would like to get unit tests for this added, covering all basic
variations.

> 
> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
> ---
>  proxmox-rest-server/src/worker_task.rs | 35 +++++++++++---------------
>  1 file changed, 14 insertions(+), 21 deletions(-)
> 
> diff --git a/proxmox-rest-server/src/worker_task.rs b/proxmox-rest-server/src/worker_task.rs
> index a3a65add..c9ae5243 100644
> --- a/proxmox-rest-server/src/worker_task.rs
> +++ b/proxmox-rest-server/src/worker_task.rs
> @@ -464,29 +464,22 @@ pub fn upid_read_status(upid: &UPID) -> Result<TaskState, Error> {
>          data.pop();
>      }
>  
> -    let last_line = match data.iter().rposition(|c| *c == b'\n') {
> -        Some(start) if data.len() > (start + 1) => &data[start + 1..],
> -        Some(_) => &data, // should not happen, since we removed all trailing newlines
> -        None => &data,
> -    };
> -
> -    let last_line = std::str::from_utf8(last_line)
> -        .map_err(|err| format_err!("upid_read_status: utf8 parse failed: {}", err))?;
> -
> -    let mut endtime = upid.starttime; // as fallback
> -    let mut iter = last_line.splitn(2, ": ");
> -    if let Some(time_str) = iter.next() {
> -        if let Ok(parsed_endtime) = proxmox_time::parse_rfc3339(time_str) {
> -            endtime = parsed_endtime; // save last found time for when the state cannot be parsed
> -            if let Some(rest) = iter.next().and_then(|rest| rest.strip_prefix("TASK ")) {
> -                if let Ok(state) = TaskState::from_endtime_and_message(parsed_endtime, rest) {
> -                    return Ok(state);
> -                }
> -            }
> +    let state = data.rsplit(|&c| c == b'\n').find_map(|line| {
> +        let line_str = std::str::from_utf8(line).ok()?;
> +        let mut parts = line_str.splitn(2, ": ");
> +        let time_str = parts.next()?;
> +        let endtime = proxmox_time::parse_rfc3339(time_str).ok()?;
> +        if let Some(rest) = parts.next().and_then(|rest| rest.strip_prefix("TASK ")) {
> +            Some(TaskState::from_endtime_and_message(endtime, rest).ok()?)
> +        } else {
> +            // no last line with both, end-time and task-state, found.
> +            Some(TaskState::Unknown { endtime })
>          }
> -    }
> +    });
>  
> -    Ok(TaskState::Unknown { endtime }) // no last line with both, end-time and task-state, found.
> +    Ok(state.unwrap_or(TaskState::Unknown {
> +        endtime: upid.starttime,
> +    }))
>  }
>  
>  static WORKER_TASK_LIST: LazyLock<Mutex<HashMap<usize, Arc<WorkerTask>>>> =



_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


      reply	other threads:[~2025-09-15 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 12:58 Filip Schauer
2025-09-15 19:37 ` Thomas Lamprecht [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=b9f38b79-6f7d-4a82-80c5-e0406d3f2049@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.schauer@proxmox.com \
    --cc=pbs-devel@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal