[BUG] USHIFT-657 MicroShift does not find lvmd config if no microshift config file exists.

[copejon]

Which issue(s) this PR addresses:

Closes # USHIFT-657

This PR removes the assumption that the microshift config and the lvmd config are always co-located. This created a situation where, if a user does not create a microshift config, the search for the lvmd config would short circuit. This isn't a safe assumption because the microshift default values, used when a user hasn't created a config file, are generally safe for common use cases. The lvmd config however must usually be defined to describe the host's storage environment, which is probably less uniform with arbitrary volume group names.

This became and issue when the name of the microshift default/example config was changed in the RPM spec, which provided an anchor for the lvmd config logic to rely on when no user config was specified.

[copejon]

I'm unable to access the jira board at the moment. Will try again tomorrow and append the ticket link asap.

[copejon]

/bug
/hold

[pmtk]

/retest-required

[copejon]

pre-steps are failing during system dep installs
/retest

[pmtk]

/retest

[copejon]

/bug

[copejon]

/hold cancel

[pmtk]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, pmtk

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 [copejon,pmtk]

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

[openshift-ci]

@copejon: 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
ci/prow/e2e-router-smoke-test	1294a83	link	false	/test e2e-router-smoke-test

Full PR test history. Your PR dashboard.

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.