mirror of
https://github.com/luthermonson/go-proxmox.git
synced 2026-04-26 17:35:48 +03:00
[GH-ISSUE #68] Cloud-init Fails #14
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/go-proxmox#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mcbenjemaa on GitHub (Aug 7, 2023).
Original GitHub issue: https://github.com/luthermonson/go-proxmox/issues/68
After adding the iso the first time, the second run fails:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x8 pc=0x104837bb0]
goroutine 1 [running]:
github.com/luthermonson/go-proxmox.(*Task).Ping(0x0)
/Users/mbenjemaa/workspace/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-alpha3/tasks.go:39 +0x20
github.com/luthermonson/go-proxmox.(*Task).Wait(0x0, 0x3b9aca00, 0x77359400)
/Users/mbenjemaa/workspace/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-alpha3/tasks.go:145 +0x2c
github.com/luthermonson/go-proxmox.(*Task).WaitFor(...)
/Users/mbenjemaa/workspace/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-alpha3/tasks.go:140
github.com/luthermonson/go-proxmox.(*VirtualMachine).CloudInit(0x140001980e0, {0x104844d81, 0x4}, {0x10485df67, 0x1ed}, {0x10485df67, 0x1ed})
/Users/mbenjemaa/workspace/go/pkg/mod/github.com/luthermonson/go-proxmox@v0.0.0-alpha3/virtual_machine.go:149 +0x1a8
@luthermonson commented on GitHub (Aug 7, 2023):
the stack trace is saying this is coming from pinging a task and i think it's missing a client when it tries to do that. can you give me some code example on how you are using this?
@mcbenjemaa commented on GitHub (Aug 7, 2023):
I just have the example for the Cloud init on the second run it fails.
Basically, in the WaitFor
@mcbenjemaa commented on GitHub (Aug 7, 2023):
I will paste code tomorrow
@mcbenjemaa commented on GitHub (Aug 8, 2023):
run this twice, and in the second run, you get a runtime panic.
@luthermonson commented on GitHub (Aug 9, 2023):
i will merge and cut a new alpha when we fix the other outstanding issue with the cpu float32... feel free to try my code change and see if it fixes your issue. it stemmed from the second call to add tag being a noop and returning a nil task. good catch!
@mcbenjemaa commented on GitHub (Aug 9, 2023):
exactly the task for setting the tag is failing