Bug 1911658

Summary: [machines] The error message should disappear after correction and re-run successfully
Product: Red Hat Enterprise Linux 8 Reporter: Xianghua Chen <xchen>
Component: cockpit-appstreamAssignee: Katerina Koukiou <kkoukiou>
Status: NEW --- QA Contact: Xianghua Chen <xchen>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.4CC: wshi, ymao
Target Milestone: rcKeywords: Reopened
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-06 07:28:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Xianghua Chen 2020-12-30 14:53:05 UTC 
Description of problem: 
The error message should disappear after correction and re-run successfully

Version-Release number of selected component (if applicable):
cockpit-machines-234-1.el8.noarch
libvirt-dbus-1.3.0-2.module+el8.3.0+6423+e4cb6418.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare a off VM

2. Move the image file like:

# mv /var/lib/libvirt/images/cirros.qcow2 /var/lib/libvirt/images/cirros.qcow2.bak

3. Click run, the vm failed to run and there will be an error under State like:

VM corros failed to start
Cannot access storage file '/var/lib/libvirt/images/cirros.qcow2' (as uid:107, gid:107): No such file or directory
4. Move the image back, click Run again
 
Actual results:
In step 4, The vm starts to run and it's "Running" under "State", but there are still previous error message under State as in step 3



Expected results:
The previous error message should be cleared after correction and re-run successfully

Additional info:
Comment 2 RHEL Program Management 2022-06-30 07:27:27 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 5 RHEL Program Management 2023-01-21 07:27:40 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 8 RHEL Program Management 2023-08-06 07:28:16 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.