-
Notifications
You must be signed in to change notification settings - Fork 545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[collect] Handle custom node and inherited configs with collections #3852
[collect] Handle custom node and inherited configs with collections #3852
Conversation
Congratulations! One of the builds has completed. 🍾 You can install the built RPMs by following these steps:
Please note that the RPMs should be used only in a testing environment. |
8641897
to
d6bc604
Compare
24cdb35
to
4b56b74
Compare
I've restarted the 2 failed jobs, not sure why they are failing, and it's not the first time, I'll take that away as a separate issue |
sos/collector/sosnode.py
Outdated
self.run_command(f"rm {remote_config} ; rmdir {self.tmpdir}", | ||
use_shell=True, | ||
need_root=True) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, same here. Very much not a fan of doing rm
s like this - the local sos installation on the remote node should take care of any cleanup. If we place the inherited config files in /tmp
, then they would be both out of the way and cleaned up separately by long-standing behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll presume you mean leaving the inherited conf in the tmp directory and letting systemd-tmpfiles-clean.timer
RHEL, or tmpfiles.d
for Ubuntu, handle the cleanup on schedule?
It works for my use case, as long as we are comfortable that the file remains might (although probably uncommon) store plugin_options
in the file for things like mysql.dbpass
, postgresql.password
, skydive.password
?
I've started building some packages for testing [1], so will do the testing soon [1] https://launchpad.net/~arif-ali/+archive/ubuntu/sos-pr-3852 |
@TrevorBenson did you test the oc transport already? I'm asking because I'm setting up an environment to test some other stuff and I can use it to test this PR as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tested both the of the new config options, and works as expected from the juju
perspective. Thanks for your work on this
EDIT: don't forget to squash your commits, as ideally it is preferred to have one commit per PR
Just the 3 / 5 retry attempts are worth to fix, otherwise ACK. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me overall. Just two super minor nits, and Pavel's comment on the 3 vs 5 attempts. FWIW, I think 3 attempts is sufficient.
Nope. not yet. I'd need to reconfigure some things or get a spare system so would take me at least a week before I could do testing via |
No problem as I tend to squash/fixup everything, but sometimes I've seen the force push removing a line hide comments which appeared to come from a review of a specific commit vs. the entire file. Once all reviewers are happy I'll get it into the single commit and force push. 👍🏼 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please just squash at least the 2 review commits.
3d35b2f
to
4fdbb38
Compare
I've squashed into a single commit. My initial tests were with control persist and all worked as expected. Once the checks are complete I will load from the updated copr repo for the saltstack transport test. I believe @arif-ali will test, or already has tested, with juju & @jcastill will test with oc. |
Signed-off-by: Trevor Benson <trevor.benson@gmail.com>
4fdbb38
to
ff74a74
Compare
FYI I moved the arguments below |
Please place an 'X' inside each '[]' to confirm you adhere to our Contributor Guidelines