-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Update salt-minion to 3004 and python310 #5017
Conversation
@hgy59 as an FYI, it's still not fully baked yet. The daemon stops after a few seconds for an unknown reason. May be due to the lack of installed salt-master instance, duno, will investigate with current version to confirm expected behavior. Feel free to chim-in if you have a hint on this. And BTW, that in conjunction of the other PR would address all python3 use-cases we have, potentially leading to a bit of clean-up afterwards. |
I found that probably the patch at installation time does not work as expected. The installer log shows that a salt-wheel is built before the patch is applied. I have no clue whether wheels created with pip install will be prefered over the python files in the extract of installer log (DSM 6, aarch64)
the line |
When I remove the
I get the following logfile:
The EDIT: {
"pid": 3885,
"name": "/volume1/@appst",
"start_time": 1640201150.79
} |
There is no output from using the python patch.py and testing on my end worked out properly (but there might be somethine I missed?). Also here is the updated output:
And good catch with the pid file. I'll rework that side of things and see if this hint brings me somewhere... |
@hgy59 I believe I now have found my last remaining issue: when salt-minion start it ends-up forking into a new PID and my assumption is that the start-stop-status script loose sight of it. For instance it starts-up with:
And then right before stopping:
EDIT: And found it! Two issues, a) the service-setup.sh was re-declaring a |
@hgy59 before I merge this, should I move the configuration currently in |
Hi @th0ma7 . You have tagged me in this issue. Do you need any work done by me or was it just a note-to-self ? BR & Happy Holidays
|
No, I was just making the linkage with you previous work. But you're welcome to join in if you like, cheers and happy holidays! |
@th0ma7 I would strongly prefer if your "import commit" has the correct author information attached in git. (I dislike the imports you do as it removes the author information in git). Alternatively merge he's PR first. Or better clone he's branch and work off of that, so we retain the original history. |
@publicarray thnx for the info and I'll try to remind adding @arnebjarne as co-author. Note that I had took good care of linking all PR and prior work. Also, indeed this PR is heavily influenced by his great work but is also significantly adapted/different. |
@SynoCommunity/developers advice needed: current OR, when I'll finish-up the work on |
Co-authored-by: hgy59 <hpgy59@gmail.com>
Co-authored-by: hgy59 <hpgy59@gmail.com>
Co-authored-by: Bjarne Saltbaek <arnebjarne72@hotmail.com>
@arnebjarne I finally found time to come back on this PR. Would you mind giving it a try? It now uses the latest spksrc python framework changes and includes most of your proposed changes from your original PR. Otherwise I think its now ready for merge & publish. |
Co-Author:Bjarne Saltbaek <arnebjarne72@hotmail.com>
@arnebjarne I've ended-up migrating over the |
Tested on:
|
Motivation: Making mileage from @arnebjarne and try to simplify salt-minion package while migrating this last bit to python 3.10
Linked issues: #4845, saltstack/salt#61384
Closes: #4847
Checklist
all-supported
completed successfully