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

UI: Bugfix - provision volumes with labels #2066

Merged
merged 4 commits into from
Dec 10, 2019

Conversation

carlito-scality
Copy link
Contributor

Component: UI

Context:

  • We need to add labels in the templates instead of the Volume object itself when creating volumes so labels can be propagated to PersistentVolume.

Summary:

Acceptance criteria:

Screenshot 2019-11-22 at 10 08 17


Closes: #1891

@carlito-scality carlito-scality added kind:bug Something isn't working moonshot topic:ui UI-related issues complexity:easy Something that requires less than a day to fix labels Nov 22, 2019
@carlito-scality carlito-scality requested a review from a team as a code owner November 22, 2019 09:19
@bert-e
Copy link
Contributor

bert-e commented Nov 22, 2019

Hello carlito-scality,

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 Nov 22, 2019

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

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 Nov 22, 2019

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:

ChengYanJin
ChengYanJin previously approved these changes Nov 22, 2019
Copy link
Contributor

@ChengYanJin ChengYanJin left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -212,11 +212,15 @@ export function* createVolumes({ payload }) {
kind: 'Volume',
metadata: {
name: newVolume.name,
labels: newVolume.labels,
Copy link
Contributor

Choose a reason for hiding this comment

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

No, keep it

@bert-e
Copy link
Contributor

bert-e commented Nov 22, 2019

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 Dec 3, 2019

History mismatch

Merge commit #94bed350fee2418e8e0c3118a630a0d7452f82f1 on the integration branch
w/2.5/bugfix/provision_volumes_with_labels is merging a branch which is neither the current
branch bugfix/provision_volumes_with_labels nor the development branch
development/2.5.

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

@carlito-scality carlito-scality force-pushed the bugfix/provision_volumes_with_labels branch from bd502bd to 0c0b76c Compare December 5, 2019 10:09
@carlito-scality
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2019

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2019

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

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 Dec 5, 2019

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:

…f Volume when creating so labels can be set correctly in PersistentVolume.

- Display the peristentVolume labels instead of Volume labels ifself
- Add cypress-wait-until library to check the volume avaibility by retrying the status check
- Fix Volume SparseLoopDevice failed status due to the size problem
@carlito-scality carlito-scality force-pushed the bugfix/provision_volumes_with_labels branch from 0c0b76c to e202c88 Compare December 5, 2019 14:43
@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2019

History mismatch

Merge commit #aa709d0669bec793ebafc64eda377e2180950545 on the integration branch
w/2.5/bugfix/provision_volumes_with_labels is merging a branch which is neither the current
branch bugfix/provision_volumes_with_labels nor the development branch
development/2.5.

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

@carlito-scality
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2019

Reset complete

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

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2019

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

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 Dec 5, 2019

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:

- cypress-wait-until is required to launch cypress tests
@carlito-scality
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Dec 9, 2019

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 Dec 9, 2019

Build failed

The build for commit did not succeed in branch w/2.5/bugfix/provision_volumes_with_labels.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Dec 10, 2019

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.4

  • ✔️ development/2.5

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

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 Dec 10, 2019

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

  • ✔️ development/2.4

  • ✔️ development/2.5

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

Please check the status of the associated issue None.

Goodbye carlito-scality.

@bert-e bert-e merged commit dd930e0 into development/2.4 Dec 10, 2019
@bert-e bert-e deleted the bugfix/provision_volumes_with_labels branch December 10, 2019 19:47
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:ui UI-related issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UI: Provision volumes with labels (in the PV template)
4 participants