Skip to content
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

Merged
merged 3 commits into from
Mar 2, 2021
Merged

Conversation

TeddyAndrieux
Copy link
Collaborator

Component:

'salt'

Context:

Some CVE was discovered in Salt 3002.2 https://saltproject.io/security_announcements/active-saltstack-cve-release-2021-feb-25/

Summary:


@TeddyAndrieux TeddyAndrieux added topic:build Anything related to building steps complexity:easy Something that requires less than a day to fix topic:salt Everything related to SaltStack in our product labels Mar 1, 2021
@TeddyAndrieux TeddyAndrieux added this to the MetalK8s 2.7.3 milestone Mar 1, 2021
@TeddyAndrieux TeddyAndrieux requested a review from a team March 1, 2021 13:03
@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Hello teddyandrieux,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Conflict

A conflict has been raised during the creation of
integration branch w/2.8/improvement/upgrade-salt-30025 with contents from improvement/upgrade-salt-30025
and development/2.8.

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

@TeddyAndrieux TeddyAndrieux force-pushed the improvement/upgrade-salt-30025 branch from 684b1c6 to 093e2c4 Compare March 1, 2021 13:05
@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Conflict

A conflict has been raised during the creation of
integration branch w/2.9/improvement/upgrade-salt-30025 with contents from w/2.8/improvement/upgrade-salt-30025
and development/2.9.

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

@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

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
@TeddyAndrieux TeddyAndrieux force-pushed the improvement/upgrade-salt-30025 branch from 093e2c4 to 80ac2a2 Compare March 1, 2021 16:27
@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

History mismatch

Merge commit #75d22962bfeb70a9f7df6e62576331ca46015f50 on the integration branch
w/2.8/improvement/upgrade-salt-30025 is merging a branch which is neither the current
branch improvement/upgrade-salt-30025 nor the development branch
development/2.8.

It is likely due to a rebase of the branch improvement/upgrade-salt-30025 and the
merge is not possible until all related w/* branches are deleted or updated.

Please use the reset command to have me reinitialize these branches.

@TeddyAndrieux
Copy link
Collaborator Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Reset complete

I have successfully deleted this pull request's integration branches.

@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Conflict

A conflict has been raised during the creation of
integration branch w/2.8/improvement/upgrade-salt-30025 with contents from improvement/upgrade-salt-30025
and development/2.8.

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

@bert-e
Copy link
Contributor

bert-e commented Mar 1, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@TeddyAndrieux
Copy link
Collaborator Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Mar 2, 2021

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.7

  • ✔️ development/2.8

  • ✔️ development/2.9

The following branches will NOT be impacted:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Mar 2, 2021

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.7

  • ✔️ development/2.8

  • ✔️ development/2.9

The following branches have NOT changed:

  • development/1.0
  • development/1.1
  • development/1.2
  • development/1.3
  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6

Please check the status of the associated issue None.

Goodbye teddyandrieux.

@bert-e bert-e merged commit 80ac2a2 into development/2.7 Mar 2, 2021
@bert-e bert-e deleted the improvement/upgrade-salt-30025 branch March 2, 2021 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity:easy Something that requires less than a day to fix topic:build Anything related to building steps topic:salt Everything related to SaltStack in our product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants