-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Labels
QA/Sarea/provisioning-v2Provisioning issues that are specific to the provisioningv2 generating frameworkProvisioning issues that are specific to the provisioningv2 generating frameworkkind/bugIssues that are defects reported by users or that we know have reached a real releaseIssues that are defects reported by users or that we know have reached a real releasepriority/0release-noteNote this issue in the milestone's release notesNote this issue in the milestone's release notesstatus/release-note-addedteam/hostbustersThe team that is responsible for provisioning/managing downstream clusters + K8s version supportThe team that is responsible for provisioning/managing downstream clusters + K8s version support
Milestone
Description
Rancher Server Setup
- Rancher version:
v2.9-dd23578d3e3499f54d80c4ed88cc52c44ee69539-head
Describe the bug
The system-agent-upgrader
SUC plan does not contain the environment variables for the system-agent
data directory (CATTLE_AGENT_VAR_DIR
), so when the system upgrade controller applies the plan, the previous configuration is lost and the default of /var/lib/rancher/agent
is used.
To Reproduce
Provision a v1.30.2+k3s2
cluster on rancher version above.
Result
Agent installs correctly, but after plan is run defaults to /var/lib/rancher/agent
.
Expected Result
Specified system agent data directory is used.
Screenshots
Additional context
Metadata
Metadata
Assignees
Labels
QA/Sarea/provisioning-v2Provisioning issues that are specific to the provisioningv2 generating frameworkProvisioning issues that are specific to the provisioningv2 generating frameworkkind/bugIssues that are defects reported by users or that we know have reached a real releaseIssues that are defects reported by users or that we know have reached a real releasepriority/0release-noteNote this issue in the milestone's release notesNote this issue in the milestone's release notesstatus/release-note-addedteam/hostbustersThe team that is responsible for provisioning/managing downstream clusters + K8s version supportThe team that is responsible for provisioning/managing downstream clusters + K8s version support