Pf9ctl Utility Fails With Segmentation Fault
Problem
While adding a node to the Management plane using pf9ctl prep-node seeing the following error:
- Initialising host 2023-09-06T17:49:12.6909Z DEBUG Running command https_proxy=http://qcwebproxylb.xxxxxx.net:3128 bash "-c" "systemctl start unattended-upgrades"stdout:stderr:
2023-09-06T17:49:12.691Z DEBUG Started unattended-upgrades
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0xb04369]
goroutine 1 [running]:
github.com/platform9/pf9ctl/pkg/pmk.PrepNode({{0xc0008ca2d0, 0x25}, {0xc000828390, 0x16}, {0xc000034ee0, 0xb}, {0xc000034ea8, 0x7}, {0xc000034ec0, 0x6}, ...}, ...)
/go/src/github.com/platform9/pf9ctl/pkg/pmk/node.go:140 +0xb49
github.com/platform9/pf9ctl/cmd.prepNodeRun(0x14636c0, {0xd32749, 0x8, 0x8})The pf9ctl utility fails with segmentation fault if there is a problem related to the package installation from the internal repo. pf9ctl is using the proxy setting to access the customer’s internal repo which is causing this issue.
Environment
Platform9 Managed Kubernetes - v5.6 and Higher.
Answer
This is a known issue, Platform9 team is investigating this. The fix for this issue will be available in PMK-5.11 release.
Additional Information
To know more details about this issue, please open a support ticket with the Jira id- PMK-6388.
PreviousGetting Errors on Reverting MetalLB Addon to v0.13.7 From v0.13.11 Default version in 1.26 K8s
NextRequirement to Change Platform9 Management Plane FQDN.
Last updated
