-
Notifications
You must be signed in to change notification settings - Fork 80
STOR-2868: Implement device relinking #598
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
Changes from all commits
a272ceb
d12b18d
5a77a03
480677a
70b6b91
8f67520
724dff8
ded965d
83337f7
7414aa1
284e31d
36927b1
eb9c565
b2982f7
c47fa7f
4f8d3c3
e2b8b2b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,6 +10,8 @@ ifeq ($(VERSION),) | |
| VERSION = latest | ||
| endif | ||
|
|
||
| .DEFAULT_GOAL := build | ||
|
|
||
|
Comment on lines
+13
to
+14
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🛠️ Refactor suggestion | 🟠 Major Default goal now points to a path that can fail on clean checkouts With Proposed fix build-diskmaker:
+ mkdir -p $(TARGET_DIR)
env GOOS=$(TARGET_GOOS) GOARCH=$(TARGET_GOARCH) go build -mod=vendor -ldflags '-X main.version=$(REV)' -o $(TARGET_DIR)/diskmaker $(CURPATH)/cmd/diskmaker-manager
.PHONY: build-diskmaker
build-operator:
+ mkdir -p $(TARGET_DIR)
env GOOS=$(TARGET_GOOS) GOARCH=$(TARGET_GOARCH) go build -mod=vendor -ldflags '-X main.version=$(REV)' -o $(TARGET_DIR)/local-storage-operator $(CURPATH)/cmd/local-storage-operator
.PHONY: build-operatorAs per coding guidelines, "-Focus on major issues impacting performance, readability, maintainability and security. Avoid nitpicks and avoid verbosity." 🤖 Prompt for AI Agents
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. go build -o There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🧩 Analysis chain🏁 Script executed: Length of output: 1536 🏁 Script executed: Length of output: 1787 🏁 Script executed: Length of output: 1750
|
||
| # Use podman or docker to build containers. Can bet set explicitly. | ||
| # make bundle REGISTRY=quay.io/username TOOL_BIN=`which docker` | ||
| ifeq ($(TOOL_BIN),) | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -37,3 +37,36 @@ spec: | |
| annotations: | ||
| summary: "LocalVolumeSet has had a deletion timestamp older than 72 hours" | ||
| description: "LocalVolumeSet {{ $labels.lvSetName }} has been marked for deletion for more than 72 hours." | ||
| - name: lso_no_stable_volume_path | ||
| rules: | ||
| - alert: LSONoStableLocalVolumePath | ||
| expr: min_over_time(lso_device_link_without_stable_path{policy="None"}[5m]) == 1 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure if it's a bug or not: So, should it be just
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I am not sure. Fix it as a follow up I guess? |
||
| for: 10m | ||
| labels: | ||
| severity: warning | ||
| annotations: | ||
| summary: | | ||
| Local Storage operator has observed that pv {{ $labels.persistent_volume }} does not | ||
| have a stable device-path in /dev/disk/by-id/ that it can use and hence it may be using | ||
| device paths which may change on reboot. Such device paths should be used carefully. | ||
| message: "Local volume represented by PersistentVolume {{ $labels.persistent_volume }} does not have any valid stable path" | ||
| description: | | ||
| Local Storage operator has observed that pv {{ $labels.persistent_volume }} does not | ||
| have a stable device-path in /dev/disk/by-id/ that it can use and hence it may be using | ||
| device paths which may change on reboot. Such device paths should be used carefully. | ||
| - name: lso_device_link_mismatch | ||
| rules: | ||
| - alert: LSODeviceLinkMismatch | ||
| expr: min_over_time(lso_device_link_mismatch{policy="None"}[5m]) == 1 | ||
| for: 10m | ||
| labels: | ||
| severity: warning | ||
| annotations: | ||
| summary: | | ||
| Local Storage operator has observed that pv {{ $labels.persistent_volume }} does not | ||
| have matching symlink it should be using vs symlink LSO prefers it to use for stability between reboots and OS upgrade. | ||
| message: "Local volume represented by PersistentVolume {{ $labels.persistent_volume }} uses a sub-optimal device symlink" | ||
| description: | | ||
| Local Storage operator has observed that pv {{ $labels.persistent_volume }} is using a symlink | ||
| that is not optimum for stability between reboots and OS upgrades. Consider updating | ||
| LocalVolumeDeviceLink policy to preferredSymlink to allow LSO to manage the symlink. | ||
Uh oh!
There was an error while loading. Please reload this page.