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

shell: Install and use Mitogen #463

Merged
merged 3 commits into from Nov 7, 2018
Merged

Conversation

NicolasT
Copy link
Contributor

@NicolasT NicolasT commented Nov 6, 2018

@NicolasT NicolasT added kind:enhancement New feature or request good first issue Good for newcomers topic:operations Operations-related issues topic:deployment Bugs in or enhancements to deployment stages labels Nov 6, 2018
@NicolasT NicolasT added this to the MetalK8s 1.1.0 milestone Nov 6, 2018
@NicolasT NicolasT requested a review from a team November 6, 2018 16:29
@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Hello NicolasT,

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

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Integration data created

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

The following branches will NOT be impacted:

  • development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Waiting for approval

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

  • one peer

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

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

History mismatch

Merge commit #073d554354e5dcf80129ce61468ae49a717cc7ce on the integration branch
w/1.2/improvement/mitogen is merging a branch which is neither the current
branch improvement/mitogen nor the development branch
development/1.2.

It is likely due to a rebase of the branch improvement/mitogen 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.

@NicolasT
Copy link
Contributor Author

NicolasT commented Nov 6, 2018

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Integration data created

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

The following branches will NOT be impacted:

  • development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Waiting for approval

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

  • one peer

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

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

History mismatch

Merge commit #bd0f0244078e7b80571b5d2f47c1d35a33bd9ecf on the integration branch
w/1.2/improvement/mitogen is merging a branch which is neither the current
branch improvement/mitogen nor the development branch
development/1.2.

It is likely due to a rebase of the branch improvement/mitogen 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.

@NicolasT
Copy link
Contributor Author

NicolasT commented Nov 6, 2018

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Integration data created

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

The following branches will NOT be impacted:

  • development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Waiting for approval

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

  • one peer

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

This is required for `mitogen` to work properly when copying files
around.
@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

History mismatch

Merge commit #38ca5023b82a1325e9858e3c0e0cbc29df9af1bf on the integration branch
w/1.2/improvement/mitogen is merging a branch which is neither the current
branch improvement/mitogen nor the development branch
development/1.2.

It is likely due to a rebase of the branch improvement/mitogen 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.

@NicolasT
Copy link
Contributor Author

NicolasT commented Nov 6, 2018

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Integration data created

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

The following branches will NOT be impacted:

  • development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented Nov 6, 2018

Waiting for approval

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

  • one peer

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

When not setting `ansible_python_interpreter`, `python` as installed in
the `make shell` environment is used. This one doesn't have access to
the SELinux Python bindings, which makes Mitogen-based deployments fail.
@bert-e
Copy link
Contributor

bert-e commented Nov 7, 2018

History mismatch

Merge commit #65b7304ae54c3b2708150f83ec128467d8673ef5 on the integration branch
w/1.2/improvement/mitogen is merging a branch which is neither the current
branch improvement/mitogen nor the development branch
development/1.2.

It is likely due to a rebase of the branch improvement/mitogen 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.

@NicolasT
Copy link
Contributor Author

NicolasT commented Nov 7, 2018

@bert-e reset

@bert-e
Copy link
Contributor

bert-e commented Nov 7, 2018

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Nov 7, 2018

Integration data created

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

The following branches will NOT be impacted:

  • development/1.0

Follow integration pull requests if you would like to be notified of
build statuses by email.

@bert-e
Copy link
Contributor

bert-e commented Nov 7, 2018

Waiting for approval

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

  • one peer

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

@bert-e
Copy link
Contributor

bert-e commented Nov 7, 2018

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/1.1

  • ✔️ development/1.2

The following branches will NOT be impacted:

  • development/1.0

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.

@bert-e
Copy link
Contributor

bert-e commented Nov 7, 2018

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

  • ✔️ development/1.1

  • ✔️ development/1.2

The following branches have NOT changed:

  • development/1.0

Please check the status of the associated issue None.

Goodbye NicolasT.

@bert-e bert-e merged commit 316cdb8 into development/1.1 Nov 7, 2018
@NicolasT NicolasT deleted the improvement/mitogen branch November 26, 2018 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind:enhancement New feature or request topic:deployment Bugs in or enhancements to deployment stages topic:operations Operations-related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants