-
Notifications
You must be signed in to change notification settings - Fork 196
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
OCPBUGS-22216: Make lvmo version visible to users via configmap #2789
OCPBUGS-22216: Make lvmo version visible to users via configmap #2789
Conversation
ed3906c
to
92fe96b
Compare
/test test-rebase |
|
||
```shell | ||
$ oc get configmap -n openshift-storage lvms-version -o jsonpath='{.data.version}' | ||
v4.14.0-10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we want to display LVMS version when running microshift version
as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we don't want the CSI driver more tightly coupled to the core service, any more than we do for other add-ons.
by image tag, with only the major version correlating the major MicroShift version. | ||
|
||
The LVMS version is not exposed by LVMS itself. For troublshooting purposes, MicroShift exposes the LVMS version | ||
via a configmap in the `openshift-storage` namespace. To get the LVMS version, run the following command: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, also update the https://github.com/openshift/microshift/blob/main/docs/user/debugging_tips.md document in this PR
Something has goofed up the lvmd.yaml default config generation. Looking into it |
/retitle OCPBUGS-22216: Make lvmo version visible to users via configmap |
@copejon: This pull request references Jira Issue OCPBUGS-22216, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this: 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. |
/retest-required |
I suspect this needs to be rebased to pick up some of the recent fixes for test flakes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two minor formatting things, but looks good overall
e61661d
to
3bbde74
Compare
/retest |
330188f
to
509d867
Compare
/retest |
/test microshift-metal-tests-arm |
6782543
to
5fa1ac3
Compare
scripts/auto-rebase/rebase-lvms.sh
Outdated
@@ -373,7 +397,7 @@ usage() { | |||
echo "$(basename "$0") to LVMS_RELEASE_IMAGE Performs all the steps to rebase LVMS" | |||
echo "$(basename "$0") download LVMS_RELEASE_IMAGE Downloads the content of a LVMS release image to disk in preparation for rebasing" | |||
echo "$(basename "$0") images Updates LVMS images" | |||
echo "$(basename "$0") manifests Updates LVMS manifests" | |||
echo "$(basename "$0") manifests LVMS_RELEASE_IMAGE Updates LVMS manifests" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in the other rebase script the manifests command relies on the image already being downloaded. Instead of changing the interface here, could we have the 'download' command put the information needed by the 'manifests' command somewhere to be found later when 'manifests' is run?
kind: ConfigMap | ||
metadata: | ||
name: lvms-version | ||
namespace: openshift-storage |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The microshift-version config map goes into kube-public to ensure special RBAC rules aren't needed to read it. Will an agent using a service account need special permission to read data from this namespace?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAICT, new and existing SAs at least have view access to CMs across the cluster. Tested this by creating a namespace and using it's default SA to read the CM in the openshift-storage namespace.
That said, I'll move change it to the kube-public NS, should those permissions be tightened up in the future.
35eeb5f
to
cd48efc
Compare
write CM to kube-public ns Signed-off-by: Jon Cope <jcope@redhat.com> add lvms version cm to openshift-storage ns Signed-off-by: Jon Cope <jcope@redhat.com>
cd48efc
to
690d5cb
Compare
Verify job is broken. Blocked until #2915 is merged |
/test verify |
/lgtm |
[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:
Approvers can indicate their approval by writing |
@copejon: 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. |
@copejon: Jira Issue OCPBUGS-22216: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-22216 has been moved to the MODIFIED state. In response to this: 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 openshift-eng/jira-lifecycle-plugin repository. |
/cherry-pick release-4.15 |
@copejon: new pull request created: #2946 In response to this:
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. |
No description provided.