Bug #3315
onehost sync does not detect updated remotes
| Status: | Closed | Start date: | 11/07/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Javi Fontan | % Done: | 0% | |
| Category: | CLI | |||
| Target version: | Release 4.10.1 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.10 |
Description
Monitoring retrieves the correct version of host remotes but sync does not find any host to update.
Associated revisions
bug #3315: use semantic versioning for remotes
onehost sync was using alphabetical comparison but this method does not work for this
comparison:
4.10.0 > 4.8.0
Now the versions are parsed by Gem::Version, that comes with rubygems and should
be installed in the frontend.
When the version can not be parsed it falls back to text comparison or forces update
if the comparison can not be made (one of the two versions is malformed).
More information about semantic versioning: http://semver.org/
bug #3315: use semantic versioning for remotes
onehost sync was using alphabetical comparison but this method does not work for this
comparison:
4.10.0 > 4.8.0
Now the versions are parsed by Gem::Version, that comes with rubygems and should
be installed in the frontend.
When the version can not be parsed it falls back to text comparison or forces update
if the comparison can not be made (one of the two versions is malformed).
More information about semantic versioning: http://semver.org/
History
#1
Updated by Ruben S. Montero over 6 years ago
- Assignee set to Javi Fontan
#2
Updated by Javi Fontan over 6 years ago
This problem happens because the comparison of versions is alphanumeric so 4.8.0 > 4.10.0. It needs to understand the version format.
#3
Updated by Ruben S. Montero over 6 years ago
- Target version changed from Release 4.12 to Release 4.10.1
#4
Updated by Javi Fontan over 6 years ago
- Status changed from Pending to Closed
- Resolution set to fixed