Skip to content

Conversation

@crawford
Copy link
Contributor

No description provided.

wking and others added 4 commits April 17, 2020 16:15
Fixing some of the logging from 0517783 (ovirt: Implement destroy,
2019-10-28, #1948) to avoid things like:

  $ openshift-install destroy cluster --dir one
  INFO searching VMs by tag=one-6xlb7
  INFO Found %!s(int=3) VMs
  INFO Stopping VM one-6xlb7-master-1 : errors: %s%!(EXTRA <nil>)
  ...

because the final 'err' had no %s in the template string to consume
it.  This commit fixes the two cases which had an 'errors: %s' using
up the final template %s, but leaves a lot of other potential logging
cleanup in this package alone.
This brings the language used in the prompts inline with the style used
in the other platforms and adds some more detail to the help messages.
This is a follow-up to d947a58. There were a few incorrect formatting
verbs and a few redundant logging statements.
This is a follow-on to 3eccc34. After looking at this more closely, I
realized that the cert bundle is only prompted if the CA is trusted
locally. This means that if the CA isn't trusted, the communication with
the oVirt engine will be insecure. I added a warning to reflect that
reality.
@openshift-ci-robot
Copy link
Contributor

@crawford: This pull request references Bugzilla bug 1825418, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.4.0) matches configured target release for branch (4.4.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1825415 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1825415 targets the "4.5.0" release, which is one of the valid target releases: 4.5.0, 4.5.z
  • bug has dependents
Details

In response to this:

Bug 1825418: ovirt: clean up prompts and logging

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 bugzilla/high bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Apr 18, 2020
@openshift-ci-robot
Copy link
Contributor

@crawford: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-aws-fips 4cf6223 link /test e2e-aws-fips
ci/prow/e2e-ovirt 4cf6223 link /test e2e-ovirt
ci/prow/e2e-libvirt 4cf6223 link /test e2e-libvirt
ci/prow/e2e-openstack 4cf6223 link /test e2e-openstack
ci/prow/e2e-aws-scaleup-rhel7 4cf6223 link /test e2e-aws-scaleup-rhel7

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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. I understand the commands that are listed here.

err = uninstaller.removeTemplate(con)
uninstaller.Logger.Errorf("Removing Template - error: %s", err)
if err := uninstaller.removeVMs(con); err != nil {
uninstaller.Logger.Errorf("Failed to remove VMs: %s", err)
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: error message strings should begin with lowercase letters as they are often appended

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree (I think), but this isn’t an error string. This is a log line, which I generally capitalize, with the error string embedded (and that string should be lowercase).

Copy link
Contributor

Choose a reason for hiding this comment

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

Correct. My mistake!

@patrickdillon
Copy link
Contributor

/lgrm

@crawford crawford added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged. labels Apr 19, 2020
@abhinavdahiya
Copy link
Contributor

/approve

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya

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

The pull request process is described here

Details 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-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 19, 2020
@openshift-merge-robot openshift-merge-robot merged commit d49a404 into openshift:release-4.4 Apr 19, 2020
@openshift-ci-robot
Copy link
Contributor

@crawford: Some pull requests linked via external trackers have merged: . The following pull requests linked via external trackers have not merged:

Details

In response to this:

Bug 1825418: ovirt: clean up prompts and logging

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.

@crawford crawford deleted the ovirt branch April 20, 2020 15:36
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/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants