[ 4.0.3.0-113] Provisioning using provision_containers.sh should not fail when image is already present in the sm db
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Juniper Openstack |
New
|
Undecided
|
Abhay Joshi | ||
R4.0 |
New
|
Undecided
|
Abhay Joshi |
Bug Description
The following happens when the image is already present in the sm database:
root@nodei5:
----> Pre provision checks to make sure setup is ready for contrail provisioning
Configuring => nodel11-vm1
[2017-11-07 12:02:27,451: local_exec_cmd] Error: Could not find a certificate for nodel11-
[2017-11-07 12:02:27,451: local_exec_cmd] None
Configuring => nodel11-vm2
[2017-11-07 12:02:40,291: local_exec_cmd] Error: Could not find a certificate for nodel11-
[2017-11-07 12:02:40,291: local_exec_cmd] None
Configuring => nodel11-vm3
[2017-11-07 12:02:54,968: local_exec_cmd] Error: Could not find a certificate for nodel11-
[2017-11-07 12:02:54,969: local_exec_cmd] None
Configuring => nodel11-vm4
[2017-11-07 12:03:04,839: local_exec_cmd] Error: Could not find a certificate for nodel11-
[2017-11-07 12:03:04,839: local_exec_cmd] None
----> Adding server manager objects to server manager database
image modification is not allowed, delete and add it.
Expectation is to use the existing image and proceed.