Repository navigation
Host is still unsecured when provisionCertificate api is called #2763
Description
SUMMARY
When provisionCertificate api is executed the host ends up in unsecured state, instead should be secured
ISSUE TYPE
- Bug Report
COMPONENT NAME
API, agent
CLOUDSTACK VERSION
4.12
CONFIGURATION
ca.framework.cert.automatic.renewal = true
ca.plugin.root.allow.expired.cert = true
ca.plugin.root.auth.strictness = false
OS / ENVIRONMENT
NA
STEPS TO REPRODUCE
execute provisionCertificate api with a random kvm host with/out recconect=true, the api call is successful but connection is unsecured.
EXPECTED RESULTS
Connection is secured
ACTUAL RESULTS
Connection is unsecured
Activity
borisstoyanov commentedon Jul 24, 2018
ping @rhtyd and @dhlaluku. Could this be related to these changes: #2756
dhlaluku commentedon Jul 24, 2018
@borisstoyanov I do not think so, that small fix that I did was for the NPE issue. The VM lifecycle tests have already been failing before and I think it might be due to regressions in provisionCertificate API itself that need looking into. Perhaps @rhtyd can help us here since he authored this feature.
kvm: Fixes apache#2763 move post-renewal libvirt restart class suitably
kvm: Fixes #2763 move post-renewal libvirt restart class suitably (#2764