Closed hlawatschek closed 5 years ago
how did you disable version check?
Thats a lousy hack. for testing reasons you could modify app/models/foreman_fog_proxmox/proxmox.rb:version_suitable? and return true at the beginning of the function.
But even better you might want to extend lib/foreman_fog_proxmox/semver.rb to support the new versioning ;-)
To be fair to it, it's not wrong, though - the real issue here is that PVE has decided to make their version a non-semver compliant version. With that being the case, it seems like the wrong direction to adapt "semver.rb" to support what isn't really a semver string, is it?
Having said that above, the change that resolves this issue is a single character in the regex in that file, so here's a PR for that anyway (#107)
Fixed by #99
Proxmox 6.0 API is intentionally rejected by the plugin. Only 5.3, 5.4 are accepted. It would be modified with 0.9.0 fog-proxmox release when it would be suitable (and tested!). See #113
Describe the bug semver initialization and therefore version check fails for PVE 6.0-6
Proxmox version:
pvesh get /version
┌─────────┬──────────┐ │ key │ value │ ├─────────┼──────────┤ │ release │ 6.0 │ ├─────────┼──────────┤ │ repoid │ c71f879f │ ├─────────┼──────────┤ │ version │ 6.0-6 │ └─────────┴──────────┘
Semver error message: Proxmox version 6.0-6.6.0 is not semver suitable
BTW: after disabling version check PVE6 seems to work fine.