-
Notifications
You must be signed in to change notification settings - Fork 45
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
Upgrade salt to 3002.5 #3158
Upgrade salt to 3002.5 #3158
Conversation
Hello teddyandrieux,My role is to assist you with the merge of this Status report is not available. |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/2.8/improvement/upgrade-salt-30025 origin/development/2.8
$ git merge origin/improvement/upgrade-salt-30025
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/2.8/improvement/upgrade-salt-30025 |
684b1c6
to
093e2c4
Compare
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/2.9/improvement/upgrade-salt-30025 origin/development/2.9
$ git merge origin/w/2.8/improvement/upgrade-salt-30025
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/2.9/improvement/upgrade-salt-30025 |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
Do not longer provide the SALT_VERSION default value in the Dockerfile, this docker file is supposed to be used with the right Salt version directly in the argument ``` docker build . --build-arg SALT_VERSION=<salt_version> ``` In the buildchain we override this value automatically with the one in versions.py, so in case of Salt upgrade the one in the dockerfile do not need to be maintained
Add roster directly in salt master config so that it's simpler to do some manual call to `salt-ssh` directly. Also in Salt 3002.5 `roster` from kwargs in ssh command is ignored, sees saltstack/salt#59657
093e2c4
to
80ac2a2
Compare
History mismatchMerge commit #75d22962bfeb70a9f7df6e62576331ca46015f50 on the integration branch It is likely due to a rebase of the branch Please use the |
/reset |
Reset completeI have successfully deleted this pull request's integration branches. |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: $ git fetch
$ git checkout -B w/2.8/improvement/upgrade-salt-30025 origin/development/2.8
$ git merge origin/improvement/upgrade-salt-30025
$ # <intense conflict resolution>
$ git commit
$ git push -u origin w/2.8/improvement/upgrade-salt-30025 |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye teddyandrieux. |
Component:
'salt'
Context:
Some CVE was discovered in Salt 3002.2 https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/
Summary:
roster
in Salt master configuration file (sees [BUG] Giving roster inkwargs
for ssh command is not longer possible since 3002.3 saltstack/salt#59657)