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

[release-4.13] USHIFT-1016: microshift crashes if LVM is not supported by host #1597

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #1577

/assign copejon

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 30, 2023

@openshift-cherrypick-robot: An error was encountered cloning bug for cherrypick for bug USHIFT-1016 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message. request failed. Please analyze the request body for more details. Status code: 400: {"errorMessages":["Number value expected as the Sprint id."],"errors":{}}

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.

In response to this:

This is an automated cherry-pick of #1577

/assign copejon

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.

@copejon
Copy link
Contributor

copejon commented Mar 30, 2023

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 30, 2023
@dhellmann
Copy link
Contributor

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 30, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 30, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, dhellmann, openshift-cherrypick-robot

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

@eggfoobar
Copy link
Contributor

eggfoobar commented Mar 30, 2023

LGTM, verified the resolution works:

System:
OS: RHEL 9.2 Beta
MicroShift Ref: This PR (de24ddb, c8278c0, b251d36)

Ran:

# remove lvm
$ sudo dnf remove lvm2* -y
$ make clean rpm srpm
$ sudo dnf localinstall -y ~/microshift/_output/rpmbuild/RPMS/*/*.rpm

# make sure error get's printed
$ sudo journalctl -u microshift.service | grep "failed to find 'vgs' command line tool"
....
Mar 30 19:30:36 microshift-instance-9.local microshift[160573]: infrastructure-services-manager W0330 19:30:36.458260  160573 storage.go:75] skipping CSI deployment: %vfailed to find 'vgs' command line tool: exec: "vgs": executable file not found in $PATH

# check to make sure storage ns isn't created
$ oc get ns
NAME                                 STATUS   AGE
default                              Active   11m
kube-node-lease                      Active   11m
kube-public                          Active   11m
kube-system                          Active   11m
openshift-dns                        Active   11m
openshift-infra                      Active   11m
openshift-ingress                    Active   11m
openshift-kube-controller-manager    Active   11m
openshift-ovn-kubernetes             Active   11m
openshift-route-controller-manager   Active   11m
openshift-service-ca                 Active   11m

# re-install lvm and restart microshift
$ sudo dnf install lvm2* -y && sudo systemctl restart microshift

# check storage namespace has been created
$ oc get ns
NAME                                 STATUS   AGE
default                              Active   13m
kube-node-lease                      Active   13m
kube-public                          Active   13m
kube-system                          Active   13m
openshift-dns                        Active   12m
openshift-infra                      Active   12m
openshift-ingress                    Active   12m
openshift-kube-controller-manager    Active   12m
openshift-ovn-kubernetes             Active   12m
openshift-route-controller-manager   Active   12m
openshift-service-ca                 Active   12m
openshift-storage                    Active   8s ### Created

@eggfoobar
Copy link
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 30, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 30, 2023

@eggfoobar: This pull request references USHIFT-1016 which is a valid jira issue.

In response to this:

/jira refresh

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.

@jogeo
Copy link
Contributor

jogeo commented Mar 30, 2023

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 30, 2023
@@ -75,6 +75,11 @@ func startCSIPlugin(cfg *config.MicroshiftConfig, kubeconfigPath string) error {
}
)

if err := lvmd.LvmSupported(); err != nil {
klog.Warning("skipping CSI deployment: %v", err)
Copy link
Member

Choose a reason for hiding this comment

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

Nothing to hold this PR if we don't want to touch it, but it's missing f: klog.Warningf so the log looks like:

skipping CSI deployment: %vfailed to find 'vgs' command line tool: exec: "vgs": executable file not found in $PATH

I'd say we could leave it as is in 4.13 and make a small fix in main (or even just fix it when touching this file in another PR)

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, Jon caught that and fixed it in this PR, #1598 seems the bot didn't pick up his cherry pick.

Copy link
Contributor

Choose a reason for hiding this comment

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

Well it didn't pick it up because the timing is off, this needs to go in first before we can cherry-pick that one

Copy link
Contributor

Choose a reason for hiding this comment

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

Yeah, i'll have that backported rather than fix the the bot-generated PR.

@eggfoobar
Copy link
Contributor

/label bugzilla/valid-bug

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 31, 2023

@eggfoobar: Can not set label bugzilla/valid-bug: Must be member in one of these teams: []

In response to this:

/label bugzilla/valid-bug

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.

@ggiguash
Copy link
Contributor

ggiguash commented Apr 2, 2023

/label bugzilla/valid-bug

@openshift-ci openshift-ci bot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Apr 2, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 2, 2023

@openshift-cherrypick-robot: all tests passed!

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.

@openshift-merge-robot openshift-merge-robot merged commit ded652d into openshift:release-4.13 Apr 2, 2023
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. 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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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