Change to using new dependency name for osreleaser

[mx-psi]

What does this PR do?

Changes github.com/cobaugh/osrelease to github.com/acobaugh/osrelease.

Fixes #626.

Additional notes

To do this I

1. changed the name in go.mod and the Go code that used it,
2. ran go mod tidy -go=1.15 and
3. ran go mod vendor.

Step 3 added another vendored dependency unrelated AFAIK to this change.

[k8s-ci-robot]

Welcome @mx-psi!

It looks like this is your first PR to kubernetes/node-problem-detector 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/node-problem-detector has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @mx-psi. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[vteratipally]

/lgtm /ok-to-test

[tallclair]

Friendly ping. I'd like to see this merged.

[mx-psi]

Anything I can do to get this merged?

[vteratipally]

/ok-to-test
/lgtm

[vteratipally]

/lgtm
/ok-to-test

[mx-psi]

It seems unlikely to me that the failing tests are related to the contents of this PR. Can someone with more knowledge of the project assess if these are related and, if so, how to fix them? cc @tallclair ?

[k8s-ci-robot]

@mx-psi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-npd-e2e-test	0b64594	link	true	/test pull-npd-e2e-test

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.

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.

[vteratipally]

/retest

[vteratipally]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mx-psi, vteratipally

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:

• OWNERS [vteratipally]

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