Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI doesn't show backup failure #7093

Closed
Sempronto opened this issue Oct 31, 2024 · 3 comments
Closed

UI doesn't show backup failure #7093

Sempronto opened this issue Oct 31, 2024 · 3 comments
Assignees
Labels
verified All test cases were verified successfully

Comments

@Sempronto
Copy link

Sempronto commented Oct 31, 2024

In the backup panel, the details always show the last successful backup, even if subsequent failed

Steps to reproduce

Cause a backup to fail (for example by changing the access password to the destination share)

Expected behavior

In the backup panel, clicking on "See details" on bottom the scheduled backup, these show that the backup failed

Actual behavior

the details still show the last successful backup

Image
Image

Components

core 3.1.4

@stephdl
Copy link

stephdl commented Nov 19, 2024

QA

install the core testing version with a cluster of two nodes, to test the work you can use a local backup on another node (you can suspend the vm to simulate a failure)

the testing version is ghcr.io/nethserver/core:3.2.3-dev.2

configure a backup of an application

  • case 1 : backup is going well the first backup
    once the backup is done and finished you can go to the list of application and verify that we have the last stats of the backup, the duration of the backup, the time when the backup has finished and a green flag to advertise that everything is good

  • case2 : backup is going bad the second backup
    suspend the destination machine, and trigger to start the backup, you will have a timeout about 2 minutes before to go to error. verify the status of the backup we will have a red flag, the duration, the end of task but no statistics

  • case 3: backup is going bad the first time
    configure a backup of a module and suspend the destination machine before to trigger the backup. You will have a timeout about 2 minutes before to go to error. verify the status of the backup we will have a red flag, the duration, the end of task but no statistics

an example of bad backups
Image

stephdl added a commit to NethServer/ns8-core that referenced this issue Nov 19, 2024
Improve error handling and status reporting in backup process NethServer/dev#7093
@stephdl stephdl added the testing Packages are available from testing repositories label Nov 19, 2024
@nethbot nethbot moved this from In progress to Testing in NethServer Nov 19, 2024
@nrauso nrauso self-assigned this Nov 22, 2024
@nrauso
Copy link

nrauso commented Nov 22, 2024

Test cases 1,2 and 3: VERIFIED

@nrauso nrauso added verified All test cases were verified successfully and removed testing Packages are available from testing repositories labels Nov 22, 2024
@nethbot nethbot moved this from Testing to In Progress in NethServer Nov 22, 2024
@nethbot nethbot moved this from In Progress to Verified in NethServer Nov 22, 2024
@DavidePrincipi
Copy link
Member

@github-project-automation github-project-automation bot moved this from Verified to Done in NethServer Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
verified All test cases were verified successfully
Projects
Archived in project
Development

No branches or pull requests

5 participants