Repository navigation
Conversation
Collaborator
Author
|
@blueorangutan package |
|
@Damans227 a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #14361 +/- ##
============================================
- Coverage 19.91% 19.91% -0.01%
+ Complexity 20198 20195 -3
============================================
Files 6373 6373
Lines 577234 577234
Branches 70696 70696
============================================
- Hits 114945 114942 -3
- Misses 449724 449726 +2
- Partials 12565 12566 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 19471 |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #13079
Adding a fresh KVM host fails when
/etc/cloudstack/agent/agent.propertiesdoes not exist yet.keystore-setuponly saves the keystore passphrase when that file is already there, so on a new host the passphrase is never written. The next step,keystore-cert-import, reads the passphrase from that file, finds nothing and exits, and after three tries the add fails with "Failed to setup certificate in the KVM agent's keystore file". This creates the file when it is missing, so the passphrase is saved and the host adds on the first try. When the file already has a passphrase it is reused as before.Test:
On a KVM lab, put a host in maintenance and remove it. On the host, stop
cloudstack-agentand clear/etc/cloudstack/agent/so onlyenvironment.propertiesandlog4j-cloud.xmlare left. Then add it back withcmk add host hypervisor=KVM url=http://10.0.33.100 .... For before, the same steps with main'skeystore-setupcopied onto the host.Before: add fails, no
agent.propertiesis created.management-server.log, same output three times:
On the host:
After: host adds on the first try.
Removing the host and adding it again without clearing the folder reuses the saved passphrase, and
agent.propertiesstill has onekeystore.passphraseline: