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

Ensure containerd is ready before importing container image #3020

Merged
merged 3 commits into from
Jan 11, 2021

Conversation

TeddyAndrieux
Copy link
Collaborator

Component:

'salt'

Context:

Time to time importing of pause image fail because containerd just get upgraded and not fully restarted

         ID: Inject pause image
    Function: containerd.image_managed
        Name: k8s.gcr.io/pause:3.1
      Result: False
     Comment: Failed to import archive: time="2021-01-08T10:22:26+01:00" level=debug msg="unpacking 1 images"
     Started: 10:22:26.698077
    Duration: 168.411 ms
     Changes: 

Summary:

  • Add a salt module to check for container engine to be ready (using crictl version)
  • Make sure container engine is ready before importing pause image
  • Make sure container engine is ready before importing nginx image

@TeddyAndrieux TeddyAndrieux added kind:bug Something isn't working complexity:easy Something that requires less than a day to fix topic:salt Everything related to SaltStack in our product labels Jan 8, 2021
@TeddyAndrieux TeddyAndrieux requested a review from a team January 8, 2021 17:15
@bert-e
Copy link
Contributor

bert-e commented Jan 8, 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 Jan 8, 2021

Integration data created

I have created the integration data for the additional destination branches.

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

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 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 TeddyAndrieux force-pushed the bugfix/wait-after-containerd-restart branch from 776e884 to c08067d Compare January 8, 2021 17:15
@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

History mismatch

Merge commit #776e88496360be0b9502880193251bb2e0dd8989 on the integration branch
w/2.8/bugfix/wait-after-containerd-restart is merging a branch which is neither the current
branch bugfix/wait-after-containerd-restart nor the development branch
development/2.8.

It is likely due to a rebase of the branch bugfix/wait-after-containerd-restart 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 TeddyAndrieux force-pushed the bugfix/wait-after-containerd-restart branch from c08067d to 0da6de4 Compare January 8, 2021 17:16
@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

History mismatch

Merge commit #04919ccaeec9df0bbb2c99721b36aef94a095daf on the integration branch
w/2.8/bugfix/wait-after-containerd-restart is merging a branch which is neither the current
branch bugfix/wait-after-containerd-restart nor the development branch
development/2.8.

It is likely due to a rebase of the branch bugfix/wait-after-containerd-restart 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 TeddyAndrieux force-pushed the bugfix/wait-after-containerd-restart branch from 0da6de4 to 0914eac Compare January 8, 2021 17:17
@TeddyAndrieux
Copy link
Collaborator Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

Integration data created

I have created the integration data for the additional destination branches.

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

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 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:

gdemonet
gdemonet previously approved these changes Jan 8, 2021
- init_delay: 2

Ensure containerd is ready:
test.configurable_test_state:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reason cri.ready is not implemented as some module?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would need to create a state module in addition to wrap this call. Using slots looks simpler to me :)

Copy link
Collaborator Author

@TeddyAndrieux TeddyAndrieux Jan 8, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WDYM ? As a salt state module ?

For me, since it's something that does not change anything on the machine we do not want to have a salt state module for this.

Copy link
Contributor

@NicolasT NicolasT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe there's a little bug (likely not something we'd ever run into, but still).

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 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:

The following reviewers are expecting changes from the author, or must review again:

@NicolasT
Copy link
Contributor

NicolasT commented Jan 8, 2021

Is this in any way related to #2960 ?

@TeddyAndrieux
Copy link
Collaborator Author

TeddyAndrieux commented Jan 8, 2021

I believe there's a little bug (likely not something we'd ever run into, but still).

Ups, I forgot to add the new sls in the iso 😄

Is this in any way related to #2960 ?

Yep I will close this one

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

History mismatch

Merge commit #76ac91d9b1c30fe606b85b1973107291020c37e3 on the integration branch
w/2.8/bugfix/wait-after-containerd-restart is merging a branch which is neither the current
branch bugfix/wait-after-containerd-restart nor the development branch
development/2.8.

It is likely due to a rebase of the branch bugfix/wait-after-containerd-restart 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 Jan 8, 2021

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

Integration data created

I have created the integration data for the additional destination branches.

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

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 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:

The following reviewers are expecting changes from the author, or must review again:

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

History mismatch

Merge commit #43d371ede0d1f8bb8ef67dc471d7babb382b352f on the integration branch
w/2.8/bugfix/wait-after-containerd-restart is merging a branch which is neither the current
branch bugfix/wait-after-containerd-restart nor the development branch
development/2.8.

It is likely due to a rebase of the branch bugfix/wait-after-containerd-restart 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.

Add a salt state to ensure containerd is running and reachable with
crictl. So when we try to import the pause image we are sure containerd
is ready
In repo salt state we import the nginx image before creating the
repository manifest. Add a requisite to make the container engine is
ready before importing this nginx container image
@TeddyAndrieux TeddyAndrieux force-pushed the bugfix/wait-after-containerd-restart branch from 03f8a68 to 419fb64 Compare January 8, 2021 20:31
@TeddyAndrieux
Copy link
Collaborator Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 2021

Integration data created

I have created the integration data for the additional destination branches.

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

You can set option create_pull_requests if you need me to create
integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Jan 8, 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:

The following reviewers are expecting changes from the author, or must review again:

Copy link
Contributor

@gdemonet gdemonet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@TeddyAndrieux
Copy link
Collaborator Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Jan 11, 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:

The following reviewers are expecting changes from the author, or must review again:

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jan 11, 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

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 Jan 11, 2021

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

  • ✔️ development/2.7

  • ✔️ development/2.8

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 c3f6be7 into development/2.7 Jan 11, 2021
@bert-e bert-e deleted the bugfix/wait-after-containerd-restart branch January 11, 2021 23:30
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 kind:bug Something isn't working topic:salt Everything related to SaltStack in our product
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants