Description of problem: I never heard of unsecure and everywhere is always used insecure, so I would rather see this changed to insecure, since this is a huge inconsistency. Version-Release number of selected component (if applicable): vdsm-4.20.0-878.git64a7b51.el7.centos.x86_64 but it's there since vdsm-client was introduced How reproducible: always Steps to Reproduce: 1. man vdsm-client 2. 3. Actual results: unsecure option is present Expected results: it should be "insecure" Additional info:
sounds like doc fixes.. can be squeezed to 4.1.3 imo
Hi Petr, The change has been already merged: "unsecure" option is deprecated and the right option was introduced.
This is fixed in 'vdsm-client --help', but it's still missing in man pages.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Petr, what vdsm version have you checked? There is no man page in 4.1, I've added it only now.
I checked 4.20.something (4.2 master) since I reported the bug for that version :)
(In reply to Petr Matyáš from comment #6) > I checked 4.20.something (4.2 master) since I reported the bug for that > version :) IMO it's generally wrong, because the bug is targeted to 4.1, so it should be checked with 4.1 release. But in this case I think it's good that we found out that man page is missing from 4.1 and added it by subsequent patch (and of course fixed in master).
Moving back to 4.1.3 as it's part of 4.19.19 build
Included in v4.19.19 tag, moving to ON_QA
Verified with vdsm-4.19.19-1.el7ev.x86_64 and vdsm-4.20.1-26.gitd624d2f.el7.centos.x86_64 Both man page and --help shows insecure now instead of unsecure.