server: fix failed to remove template/iso if upload from local fails

[ustcweizhou]

Description

This PR fixes the issue that failed to remove template/iso if upload from local fails

When upload template/iso/volume from local fails, the install_path will not be a full path of file so removing it will fail.

mysql> select install_path from template_store_ref;
+--------------------------------------------------------------------+
| install_path                                                       |
+--------------------------------------------------------------------+
| template/tmpl/1/3/805f4763-248e-40ec-b79a-b868cc480d0a.qcow2       |
| template/tmpl/1/4/c7e32c9e-5e72-3726-85cf-aa5ccd84118d.qcow2       |
| template/tmpl/2/201/bc4f4f08-138a-31b8-af1a-d4450eff7982.qcow2     |
| template/tmpl/2/202                                                |
| template/tmpl/2/203/203-2-d47f8cde-a2a8-31e7-a826-2628ad98a6c8.iso |
| template/tmpl/2/204                                                |
| template/tmpl/5/205                                                |
| template/tmpl/2/206                                                |
| template/tmpl/2/207                                                |
| template/tmpl/2/208                                                |
| template/tmpl/2/209                                                |
| template/tmpl/2/210                                                |
+--------------------------------------------------------------------+
12 rows in set (0.00 sec)

mysql> select install_path from volume_store_ref;
+---------------------------------------------------------+
| install_path                                            |
+---------------------------------------------------------+
| volumes/2/22                                            |
| volumes/2/19/f93face9-6521-4184-b89a-cb07f86bbae8.qcow2 |
| volumes/2/23                                            |
| volumes/2/24                                            |
+---------------------------------------------------------+
4 rows in set (0.00 sec)

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

[yadvr]

@blueorangutan package

[blueorangutan]

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔centos7 ✖centos8 ✔debian. JID-2612

[shwstppr]

@blueorangutan test centos7 vmware-67u3

[blueorangutan]

@shwstppr a Trillian-Jenkins test job (centos7 mgmt + vmware-67u3) has been kicked to run smoke tests

[blueorangutan]

Trillian test result (tid-3453)
Environment: vmware-67u3 (x2), Advanced Networking with Mgmt server 7
Total time taken: 45950 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4626-t3453-vmware-67u3.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_templates.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_snapshots.py
Smoke tests completed. 81 look OK, 2 have error(s)
Only failed tests results shown below:

Test	Result	Time (s)	Test File
test_01_deploy_kubernetes_cluster	Failure	3613.69	test_kubernetes_clusters.py
test_02_invalid_upgrade_kubernetes_cluster	Failure	3601.97	test_kubernetes_clusters.py
test_03_deploy_and_upgrade_kubernetes_cluster	Failure	0.04	test_kubernetes_clusters.py
test_04_deploy_and_scale_kubernetes_cluster	Failure	0.04	test_kubernetes_clusters.py
test_05_delete_kubernetes_cluster	Failure	0.04	test_kubernetes_clusters.py
test_07_deploy_kubernetes_ha_cluster	Failure	0.04	test_kubernetes_clusters.py
test_08_deploy_and_upgrade_kubernetes_ha_cluster	Failure	0.04	test_kubernetes_clusters.py
test_09_delete_kubernetes_ha_cluster	Failure	0.04	test_kubernetes_clusters.py
ContextSuite context=TestKubernetesCluster>:teardown	Error	38.33	test_kubernetes_clusters.py
test_02_create_template_with_checksum_sha1	Error	5.11	test_templates.py
test_03_create_template_with_checksum_sha256	Error	5.11	test_templates.py
test_04_create_template_with_checksum_md5	Error	5.12	test_templates.py

[yadvr]

@blueorangutan test

[blueorangutan]

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[blueorangutan]

Trillian test result (tid-3472)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 35325 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4626-t3472-kvm-centos7.zip
Smoke tests completed. 83 look OK, 0 have error(s)
Only failed tests results shown below:

Test	Result	Time (s)	Test File

[shwstppr]

@ustcweizhou Local upload failed with a message,
Failed to upload file due to system misconfiguration. Please contact admin.
Now with changes, I cannot delete the template with message,
The template is either getting uploaded or it may be initiated shortly, please wait for it to be completed
Is this desired? I think we can allow deleting when it is in NotUploaded state

[weizhouapache]

NotUploaded

@shwstppr NotUploaded is the initialed state of volumes/template/iso when it is uploaded from local.
when upload starts, it will be transited to UploadInProgress
when upload failed, it will be transited to UploadError

I think deleting template/iso in NotUploaded state should not be allowed (same as volumes).
when upload fails (by default template/isos/volumes will be in UploadError state after 1 hour), we can remove them.

[Pearl1594]

Verified behavior. LGTM

[yadvr]

ping @ustcweizhou @shwstppr @Pearl1594 - should we merge this on 4.14 now, or change base/milestone to 4.15.1.0?