On Thu, Nov 9, 2017 at 5:38 PM, Stephen Liu <satimis(a)yahoo.com> wrote:
> What do you mean by that? What error message do you get?
> Can you ssh from the engine machine to this address manually?
> If not, first solve this, then try again to add it.
> Perhaps it's the firewall blocking or something like that.
Status - Install Failed
Nov 9, 2017 7:01:44 PM
Host
ovirtnode.example.com installation failed. Command returned failure
code 1 during SSH session 'root(a)192.168.8.5'.
Nov 9, 2017 7:01:43 PM
Failed to install Host
ovirtnode.example.com. Failed to execute stage 'Setup
validation': Hardware does not support virtualization.
OK. So it can be connected, but fails later on.
Nov 9, 2017 7:01:43 PM
Host
ovirtnode.example.com installation in progress . Machine does not
support constant timestamp counter, this may effect performance.
Perhaps you want to check that too, but can be done later.
On Host Terminal:
$ ssh root(a)192.168.8.5 (ovirt node IP)
The authenticity of host '192.168.8.5 (192.168.8.5)' can't be established.
ECDSA key fingerprint is SHA256:J2gMI1fvZj5dNC36YClUjAGHQrnszQ23y46xjNcJnYw.
Are you sure you want to continue connecting (yes/no)?
Whether I have to proceed here first, connecting "ovirt note"?
$ egrep -c '(vmx|svm)' /proc/cpuinfo
8
$ uname -m
x86_64
$ kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used
Please check/share the host-deploy log.
You can find it on the engine machine, under /var/log/ovirt-engine/host-deploy.
Search there for 'Hardware does not support virtualization' and look at the
checks before that line. Or just upload the file somewhere and share a link.
Thanks,
Regards
SL
On Thursday, November 9, 2017, 11:18:06 PM GMT+8, Yedidyah Bar David
<didi(a)redhat.com> wrote:
On Thu, Nov 9, 2017 at 5:03 PM, Stephen Liu <satimis(a)yahoo.com> wrote:
>>> if running;
>>> 192.168.8.8 (IP of vm1)
>>> I can connect 'oVirt Open Virtualization Manager' but I can't
login with
>>> following warning:
>>>'The client is not authorized to request an authorization. It's
required
>>> to
>>>access the system using FQDN.'
>
>> Indeed, see the other thread.
>
>> If this isn't enough, please provide more details - the name you provided
>> as engine FQDN during engine-setup, whether you fixed name resolution -
>> by updating the dns or the hosts file, etc.
>
> Hi,
>
> I solved the problem with following steps:-
>
> # nano /etc/ovirt-engine/engine.conf.d/11-setup-sso.conf
>
> Change:
> SSO_ALTERNATE_ENGINE_FQDNS=""
> To:
> SSO_ALTERNATE_ENGINE_FQDNS="192.168.8.8" (ovirtengine IP)
>
> # systemctl restart ovirt-engine.service
>
> Now I can remote login ovirtengine on Host's browser running:
>
http://ovirtengine.example.com
>
> On ovirtengine
> $ cat /etc/hosts
> 127.0.0.1 localhost localhost.localdomain localhost4
> localhost4.localdomain4
> ::1 localhost localhost.localdomain localhost6
> localhost6.localdomain6
>
> 192.168.8.8
ovirtengine.example.com
> 192.168.8.5
ovirtnode.example.com
> [/end]
>
> Now I encounter another problem in "Add oVirt Node (ovirtnode.example) to
> ovirt engine from Web Administrator Portal", failure to add new host
> "ovirt
> node".
>
> To connect/login "ovirt node" on Host I must run;
> 192.168.8.5:9090
>
> Adding 192.168.8.5 to the new host, "ovirt node" can't be connected.
What do you mean by that? What error message do you get?
Can you ssh from the engine machine to this address manually?
If not, first solve this, then try again to add it.
Perhaps it's the firewall blocking or something like that.
> But
> I'm not allowed adding "192.168.8.5:9090" to Address there.
>
> Please advise is there any solution to delete ":9090"?
>
> Thanks
>
> Regards
> SL
>
>
> On Thursday, November 9, 2017, 8:34:30 PM GMT+8, Yedidyah Bar David
> <didi(a)redhat.com> wrote:
>
>
> On Thu, Nov 9, 2017 at 1:57 PM, Stephen Liu <satimis(a)yahoo.com> wrote:
>> Hi all,
>>
>> Problem to login virtengine on remote browser
>> client is not authorized to request an authorization
>
> Please check recent thread on this list, with subject "[ovirt-users]
> engine FQDN".
>
>>
>> vm1 - ovirtengine on CentOS 7, Gnome desktop (internal IP 192.168.8.8)
>> vm2 - ovirt node on CentOS 7, minimal (internal IP 192.168.8.5)
>> Host - Ubuntu 16.04 Gnome desktop
>> KVM
>>
>> vm1
>> ===
>> on Firefox running;
>>
ovirtengine.example.com
>> I can login 'oVirt Open Virtualization Manager'
>>
>> on Firefox running;
>> 192.168.8.5:9090 (ovirt node IP)
>> I can login ovirt node as root
>>
>> Host
>> ====
>> on Firefox running;
>>
ovirtengine.example.com
>> Server not found
>> (Firewall of vm1 already stopped running;
>> # systemctl stop firewalld )
>
> "Server not found" is usually unrelated to the firewall, but is a result
> of bad/missing name resolution.
>
>>
>> if running;
>> 192.168.8.8 (IP of vm1)
>> I can connect 'oVirt Open Virtualization Manager' but I can't login
with
>> following warning:
>> 'The client is not authorized to request an authorization. It's required
>> to
>> access the system using FQDN.'
>
> Indeed, see the other thread.
>
> If this isn't enough, please provide more details - the name you provided
> as engine FQDN during engine-setup, whether you fixed name resolution -
> by updating the dns or the hosts file, etc.
>
> Regards,
>
>
>>
>> on Firefox running;
>> 192.168.8.5:9090 (ovirt node IP)
>> I can login ovirt node as root
>>
>>
>> Please help. Thanks in advice.
>>
>>
>> Regards
>> SL
>
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org
>>
http://lists.ovirt.org/mailman/listinfo/users
>>
>
>
>
> --
> Didi
>
--
Didi
--
Didi