On Tue, Nov 26, 2013 at 6:29 PM, Gianluca Cecchi wrote:
On Tue, Nov 26, 2013 at 4:06 PM, Michael Pasternak wrote:
> On 11/26/2013 04:09 PM, Gianluca Cecchi wrote:
>> Hello,
>> based on RHEVM 3.2 and 3.3 beta docs I'm trying connection from ovirt cli.
>> I have:
>> engine on f19 + ovirt stable ovirt-engine-3.3.1-2.fc19.noarch
>> client from where I run cli is f19 with
>> ovirt-engine-sdk-python-3.3.0.7-1.fc19.noarch
>> ovirt-engine-cli-3.3.0.5-1.fc19.noarch
Uhm, strange.
From another client that is f19 too and incidentally contains an oVirt
AIO configuration and so has enabled the ovirt stable repo I have
ovirt-engine-sdk-python-3.3.0.8-1.fc19.noarch
ovirt-engine-cli-3.3.0.6-1.fc19.noarch
and I'm perfectly able to connect with the same steps as the not working one.
$ wget -O f18engine.crt
http://10.4.4.60:/ca.crt
--2013-11-26 22:03:41--
http://10.4.4.60/ca.crt
Connecting to 10.4.4.60:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1376 (1.3K) [application/x-x509-ca-cert]
Saving to: ‘f18engine.crt’
100%[====================================================================================================>]
1,376 --.-K/s in 0.001s
2013-11-26 22:03:42 (1.41 MB/s) - ‘f18engine.crt’ saved [1376/1376]
[g.cecchi@tekkaman ~]$ ovirt-shell -c -l
https://10.4.4.60:443/api -A
f18engine.crt -u "admin@internal"
Password:
[3;J
==========================================
>> connected to oVirt manager 3.3.0.0 <<<
==========================================
++++++++++++++++++++++++++++++++++++++++++
Welcome to oVirt shell
++++++++++++++++++++++++++++++++++++++++++
[oVirt shell (connected)]# exit
while on the not working standard f19 client (see above) I have
ovirt-engine-sdk-python-3.3.0.7-1.fc19.noarch
ovirt-engine-cli-3.3.0.5-1.fc19.noarch
as provided by upstream f19 (dated 10/10 in updates...)
Could it be this one the reason?
Anyone able to verify on standard f19 without ovirt repo against a
3.3.1 install?
Thanks,
Gianluca