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

Bug 1850574: add better cloud init message for ovirt import #6511

Merged
merged 1 commit into from Sep 10, 2020

Conversation

atiratree
Copy link
Member

No description provided.

@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. label Sep 3, 2020
@openshift-ci-robot
Copy link
Contributor

@suomiy: This pull request references Bugzilla bug 1850574, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1850574: add better cloud init message for ovirt import

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Sep 3, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 3, 2020
@atiratree
Copy link
Member Author

@matthewcarleton

cloud

@matthewcarleton
Copy link
Contributor

thanks @suomiy I think this looks good. I'm asking around for other outside opinions to make sure it makes sense too :)

@matthewcarleton
Copy link
Contributor

@suomiy I had a good chat with some other designers and they made the good point of surfacing this type of message in either the Connect to provider step where it would be more of a general list of things that might not show up. If we did that we could then consider hiding the advanced > cloud init step entirely. WDYT?

@atiratree
Copy link
Member Author

@matthewcarleton I to not think this is a very useful message to have in the connect to provider step. There is already too much happening there. Plus this is very specific

@matthewcarleton
Copy link
Contributor

@suomiy My line of thinking here is that for a user to know as soon as possible where they could see a gap in their expectations and what we have in the wizard.
At the very least changing the title is probably a good idea ( I know I wrote this to begin with haha)

Possible data missing from import
This wizard may not show all data from the import. If data is not showing here view the details of the import after it has completed for a full data set.

@atiratree
Copy link
Member Author

updated the text

aa

please review
@irosenzw @yaacov @glekner @pcbailey

@yaacov
Copy link
Member

yaacov commented Sep 9, 2020

I assume @matthewcarleton 's 👍 means he approve :-)

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 9, 2020
@yaacov
Copy link
Member

yaacov commented Sep 9, 2020

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Sep 9, 2020
@atiratree
Copy link
Member Author

updated the design

bb

@atiratree
Copy link
Member Author

@yaacov can you relgtm?

@matthewcarleton
Copy link
Contributor

LGTM!

@yaacov
Copy link
Member

yaacov commented Sep 10, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 10, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: suomiy, yaacov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit e625a05 into openshift:master Sep 10, 2020
@openshift-ci-robot
Copy link
Contributor

@suomiy: All pull requests linked via external trackers have merged:

Bugzilla bug 1850574 has been moved to the MODIFIED state.

In response to this:

Bug 1850574: add better cloud init message for ovirt import

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@spadgett spadgett added this to the v4.6 milestone Sep 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-medium Referenced Bugzilla bug's severity is medium for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. component/kubevirt Related to kubevirt-plugin lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants