openvasmd will not tell the truth about scanners and more! about gvmd

[asmaack]

Same error seems to be encountered for other commands as well, see:

$ sudo openvasmd --get-users
admin

$ gvm-cli socket -c --xml "<get_users/>"
<get_users_response status="200" status_text="OK"><filters id=""><term>first=1 rows=1000 sort=name</term><keywords><keyword><column>first</column><relation>=</relation><value>1</value></keyword><keyword><column>rows</column><relation>=</relation><value>1000</value></keyword><keyword><column>sort</column><relation>=</relation><value>name</value></keyword></keywords></filters><sort><field>name<order>ascending</order></field></sort><users start="1" max="1000"/><user_count>0<filtered>0</filtered><page>0</page></user_count></get_users_response>

[mattmundell]

Should be solved with /pull/243

[asmaack]

Confirmed fix, works like a charm now!

I suppose, in a perfect world this shouldn't have happened on a release branch :-)
Or is openvas-manager-7.0 not in feature freeze?

[bjoernricks]

Yes it is. But sometimes we have to fix important customer issues which lead to such backports. We are trying to improve the situation for future releases.