levindecaro commented on issue #6804: URL: https://github.com/apache/cloudstack/issues/6804#issuecomment-1274519943
@DaanHoogland At this moment, the impact of this issue in my environment can be discarded, since it just delete something dosen't exist. The user can proceed the deletion by 2nd retry. However, I will observe this problem will be more serious for same upgrade path when "snapshot.backup.to.secondary=false". ACS likely can't delete the invalid path volume snapshot and left the primarystorage inconsistent with database record, however I don't have another environment to verify this observation. for my deletion fail case, `/cloudstack/sg1/d0126a5a-62c9-4935-b6f8-bba159d6fbae/7ccea8f2-f393-4db1-9c11-b60a337cb53c` `d0126a5a-62c9-4935-b6f8-bba159d6fbae` actually a image file, not a directory. `7ccea8f2-f393-4db1-9c11-b60a337cb53c` should be same level of `d0126a5a-62c9-4935-b6f8-bba159d6fbae` when snapshot.backup.to.secondary=false or `7ccea8f2-f393-4db1-9c11-b60a337cb53c` copied to secondary storage when snapshot.backup.to.secondary=true -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
