Re: [ovirt-users] problem after rebooting the node
Sorry for the late reply. Actually the problem is with only one of my three nodes. So I think that it is an issue with the upgrade. I am using Ovirt-ng node OS. I will just re-install ovirt-ng OS on this node and upgrade it the way I did others. Actually, I upgraded my storage node (NFS) and lost all my data since it was in a separate folder in root (/iso and /vm) which got deleted after I upgraded my node. So I will have to start all over again. :( Anyway thanks for the help. Please just update the documentation on how to upgrade the Ovirt-ng nodes properly (I did ask about that but never got a reply :P). On Mon, Feb 6, 2017 at 5:00 PM, Edward Haas <eh...@redhat.com> wrote: > The ones you mentioned before, we just need the whole files and not > snippets of them. > vdsm.log, supervdsm.log, messages.log and the ovs ones you previously > mentioned. > > On Mon, Feb 6, 2017 at 1:14 PM, Shalabh Goel <shalabhgoe...@gmail.com> > wrote: > >> which all log files? Actually I am new to Ovirt, so it would be really >> helpful if you can tell me which ones?? >> >> Thanks >> >> On Mon, Feb 6, 2017 at 4:39 PM, Edward Haas <eh...@redhat.com> wrote: >> >>> Please package the logs (tar or zip) and send them. >>> >>> On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel <shalabhgoe...@gmail.com> >>> wrote: >>> >>>> Yes, I am using OVS as the switch type and I did not know that it was >>>> not supported officially. >>>> >>>> The output of ovs-vsctl show is as follows: >>>> >>>> f634d53e-4849-488b-8454-6b1fafa7c6ac >>>> ovs_version: "2.6.90" >>>> >>>> I am attaching OVS switch logs below: >>>> >>>> /var/log/openvswitch/ovsdb-server.log >>>> >>>> >>>> 2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file >>>> /var/log/openvswitch/ovsdb-server.log >>>> 2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open >>>> vSwitch) 2.6.90 >>>> 2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set >>>> size after 10.0 seconds >>>> 2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1 >>>> monitors:1 sessions:1 >>>> >>>> ovs-vswitchd.log >>>> >>>> >>>> 2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file >>>> /var/log/openvswitch/ovs-vswitchd.log >>>> 2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores >>>> on NUMA node 0 >>>> 2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores >>>> on NUMA node 1 >>>> 2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes >>>> and 48 CPU cores >>>> 2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >>>> connecting... >>>> 2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >>>> connected >>>> 2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch) >>>> 2.6.90 >>>> >>>> What should I do now? >>>> >>>> The engine says that "Host host2 does not comply with the cluster >>>> Default networks, the following networks are missing on host: 'ovirtmgmt' >>>> " >>>> >>>> What other logs should I attach? >>>> >>>> Thanks >>>> >>>> Shalabh Goel >>>> >>>> On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas <eh...@redhat.com> wrote: >>>> >>>>> Based on what I can see, you used OVS as the switch type and it seems >>>>> ovs (openvswitch) is not properly installed on your host. >>>>> Make sure that you have ovs operational by issuing "ovs-vsctl show". >>>>> >>>>> You should note that OVS network support is not an official release >>>>> feature, and you should use it on 4.1 and up versions. >>>>> Fixes will be probably submitted to master (appearing in nightly >>>>> builds). >>>>> >>>>> Next time please include the mailing-list in your replies and attach >>>>> the log files, it is less spamming. >>>>> >>>>> Thanks, >>>>> Edy. >>>>> >>>>> On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel <shalabhgoe...@gmail.com> >>>>> wrote: >>>>> >>>>>> log from messages >>>
Re: [ovirt-users] How to update ovirt nodes
nvocation(CurrentInvocationContextInterceptor.java:41)
[wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47)
[wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)
[wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22)
[wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)
[wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67)
[wildfly-ejb3-10.1.0.Final.jar:10.1.0.Final]
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
at
org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)
at
org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)
at
org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at
org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198)
at
org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)
at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)
at
org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)
at
org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)
at
org.ovirt.engine.core.bll.interfaces.BackendCommandObjectsHandler$$$view5.runAction(Unknown
Source) [bll.jar:]
at
org.ovirt.engine.core.bll.tasks.CommandExecutor.executeCommand(CommandExecutor.java:57)
[bll.jar:]
at
org.ovirt.engine.core.bll.tasks.CommandExecutor.lambda$executeAsyncCommand$0(CommandExecutor.java:46)
[bll.jar:]
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[rt.jar:1.8.0_121]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[rt.jar:1.8.0_121]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[rt.jar:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_121]
2017-02-06 16:47:26,411+05 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-5-thread-8)
[2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] START,
SetVdsStatusVDSCommand(HostName = NFShost-235.6,
SetVdsStatusVDSCommandParameters:{runAsync='true',
hostId='f6aeb334-6081-479b-bf69-c5d869941aa0', status='InstallFailed',
nonOperationalReason='NONE', stopSpmFailureLogged='false',
maintenanceReason='null'}), log id: 18edb8b3
2017-02-06 16:47:26,415+05 INFO
[org.ovirt.engine.core.vdsbroker.SetVdsStatusVDSCommand] (pool-5-thread-8)
[2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] FINISH, SetVdsStatusVDSCommand, log
id: 18edb8b3
2017-02-06 16:47:26,448+05 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(pool-5-thread-8) [2a3cb164-9fe7-4487-9837-1c84c9a6a2d3] EVENT_ID:
HOST_UPGRADE_FAILED(841), Correlation ID:
2a3cb164-9fe7-4487-9837-1c84c9a6a2d3, Call Stack: null, Custom Event ID:
-1, Message: Failed to upgrade Host NFShost-235.6 (User:
admin@internal-authz).
Thanks
On Mon, Feb 6, 2017 at 4:31 PM, Shalabh Goel <shalabhgoe...@gmail.com>
wrote:
> Hi,
>
> I have 3 nodes. 2 compute and 1 storage (NFS) and separate server for
> engine. I upgraded the engine first. I went on smoothly without any errors.
>
> Then I started upgrade on all 3 of them by ins
Re: [ovirt-users] problem after rebooting the node
which all log files? Actually I am new to Ovirt, so it would be really helpful if you can tell me which ones?? Thanks On Mon, Feb 6, 2017 at 4:39 PM, Edward Haas <eh...@redhat.com> wrote: > Please package the logs (tar or zip) and send them. > > On Mon, Feb 6, 2017 at 12:05 PM, Shalabh Goel <shalabhgoe...@gmail.com> > wrote: > >> Yes, I am using OVS as the switch type and I did not know that it was not >> supported officially. >> >> The output of ovs-vsctl show is as follows: >> >> f634d53e-4849-488b-8454-6b1fafa7c6ac >> ovs_version: "2.6.90" >> >> I am attaching OVS switch logs below: >> >> /var/log/openvswitch/ovsdb-server.log >> >> >> 2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file >> /var/log/openvswitch/ovsdb-server.log >> 2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open >> vSwitch) 2.6.90 >> 2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set >> size after 10.0 seconds >> 2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1 >> monitors:1 sessions:1 >> >> ovs-vswitchd.log >> >> >> 2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file >> /var/log/openvswitch/ovs-vswitchd.log >> 2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores on >> NUMA node 0 >> 2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores on >> NUMA node 1 >> 2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes and >> 48 CPU cores >> 2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >> connecting... >> 2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock: >> connected >> 2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch) >> 2.6.90 >> >> What should I do now? >> >> The engine says that "Host host2 does not comply with the cluster Default >> networks, the following networks are missing on host: 'ovirtmgmt'" >> >> What other logs should I attach? >> >> Thanks >> >> Shalabh Goel >> >> On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas <eh...@redhat.com> wrote: >> >>> Based on what I can see, you used OVS as the switch type and it seems >>> ovs (openvswitch) is not properly installed on your host. >>> Make sure that you have ovs operational by issuing "ovs-vsctl show". >>> >>> You should note that OVS network support is not an official release >>> feature, and you should use it on 4.1 and up versions. >>> Fixes will be probably submitted to master (appearing in nightly builds). >>> >>> Next time please include the mailing-list in your replies and attach the >>> log files, it is less spamming. >>> >>> Thanks, >>> Edy. >>> >>> On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel <shalabhgoe...@gmail.com> >>> wrote: >>> >>>> log from messages >>>> >>>> Feb 3 08:27:53 ovirtnode3 ovs-vsctl: >>>> ovs|1|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: >>>> database connection failed (No such file or directory) >>>> Feb 3 08:27:53 ovirtnode3 journal: vdsm vds ERROR Executing commands >>>> failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database >>>> connection failed (No su >>>> ch file or directory)#012Traceback (most recent call last):#012 File >>>> "/usr/share/vdsm/API.py", line 1531, in setupNetworks#012 >>>> supervdsm.getProxy().setup >>>> Networks(networks, bondings, options)#012 File >>>> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in >>>> __call__#012return callMethod()#012 Fi >>>> le "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in >>>> #012**kwargs)#012 File "", line 2, in >>>> setupNetworks#012 File "/usr >>>> /lib64/python2.7/multiprocessing/managers.py", line 773, in >>>> _callmethod#012raise convert_to_error(kind, >>>> result)#012ConfigNetworkError: (21, 'Executing co >>>> mmands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database >>>> connection failed (No such file or directory)') >>>> >>>> Log from vdsm.log >>>> >>>> Reactor thread::INFO::2017-02-03 08:32:24,638::protocoldetector >>>> ::72::ProtocolDetector.AcceptorImpl::(handle_accept) Accepted >>>> connection from ::1:5
Re: [ovirt-users] How to update ovirt nodes
ncy: libvirt-python >= 2.0.0-2 for package: vdsm-4.19.4-1.el7.centos.x86_64--> Processing Dependency: libvirt-daemon-kvm >= 2.0.0-10.el7_3.4 for package: vdsm-4.19.4-1.el7.centos.x86_64--> Processing Dependency: /usr/bin/ruby for package: rubygem-proxifier-1.0.3-1.el7.noarch--> Processing Dependency: /usr/bin/ruby for package: fluentd-0.12.26-1.el7.noarch--> Processing Dependency: /usr/bin/ruby for package: rubygem-fluent-plugin-secure-forward-0.4.3-1.el7.noarch--> Finished Dependency ResolutionError: Package: rubygem-thread_safe-0.3.4-1.el7.noarch (centos-opstools-testing) Requires: ruby(release)Error: Package: vdsm-4.19.4-1.el7.centos.x86_64 (ovirt-4.1) Requires: sanlock >= 3.4.0-1 Installed: sanlock-3.2.4-2.el7_2.x86_64 (installed) sanlock = 3.2.4-2.el7_2Error: Package: rubygem-msgpack-0.5.11-1.el7.x86_64 (centos-opstools-testing) Requires: libruby.so.2.0()(64bit)Error: Package: rubygem-cool.io-1.2.4-2.el7.x86_64 (centos-opstools-testing) Requires: libruby.so.2.0()(64bit)Error: Package: 10:qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64 (ovirt-4.1) Requires: libusbx >= 1.0.19 Installed: libusbx-1.0.15-4.el7.x86_64 (installed) libusbx = 1.0.15-4.el7Error: Package: ovirt-release-host-node-4.1.0-1.el7.centos.noarch (ovirt-4.1) Requires: screenError: Package: ovirt-release-host-node-4.1.0-1.el7.centos.noarch (ovirt-4.1) Requires: tcpdumpError: Package: vdsm-4.19.4-1.el7.centos.x86_64 (ovirt-4.1) Requires: libvirt-daemon-kvm >= 2.0.0-10.el7_3.4 Installed: libvirt-daemon-kvm-1.2.17-13.el7_2.5.x86_64 (installed) libvirt-daemon-kvm = 1.2.17-13.el7_2.5Error: Package: ovirt-release-host-node-4.1.0-1.el7.centos.noarch (ovirt-4.1) Requires: rng-toolsError: Package: 10:qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64 (ovirt-4.1) Requires: seavgabios-bin >= 1.9.1-4 Installed: seavgabios-bin-1.7.5-11.el7.noarch (installed) seavgabios-bin = 1.7.5-11.el7Error: Package: collectd-5.7.0-2.el7.x86_64 (centos-opstools-testing) Requires: libltdl.so.7()(64bit)Error: Package: fluentd-0.12.26-1.el7.noarch (centos-opstools-testing) Requires: /usr/bin/rubyError: Package: vdsm-4.19.4-1.el7.centos.x86_64 (ovirt-4.1) Requires: libvirt-python >= 2.0.0-2 Installed: libvirt-python-1.2.17-2.el7.x86_64 (installed) libvirt-python = 1.2.17-2.el7Error: Package: 10:qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64 (ovirt-4.1) Requires: usbredir >= 0.7.1 Installed: usbredir-0.6-7.el7.x86_64 (installed) usbredir = 0.6-7.el7Error: Package: rubygem-proxifier-1.0.3-1.el7.noarch (centos-opstools-testing) Requires: /usr/bin/rubyError: Package: rubygem-thread_safe-0.3.4-1.el7.noarch (centos-opstools-testing) Requires: ruby(rubygems)Error: Package: rubygem-http_parser.rb-0.6.0-1.el7.x86_64 (centos-opstools-testing) Requires: libruby.so.2.0()(64bit)Error: Package: 10:qemu-kvm-ev-2.6.0-28.el7_3.3.1.x86_64 (ovirt-4.1) Requires: ipxe-roms-qemu >= 20160127-4 Installed: ipxe-roms-qemu-20130517-8.gitc4bce43.el7_2.1.noarch (installed) ipxe-roms-qemu = 20130517-8.gitc4bce43.el7_2.1Error: Package: rubygem-fluent-plugin-secure-forward-0.4.3-1.el7.noarch (centos-opstools-testing) Requires: /usr/bin/rubyError: Package: ovirt-release-host-node-4.1.0-1.el7.centos.noarch (ovirt-4.1) Requires: sysstatError: Package: ovirt-release-host-node-4.1.0-1.el7.centos.noarch (ovirt-4.1) Requires: net-snmpError: Package: rubygem-string-scrub-0.0.5-1.el7.x86_64 (centos-opstools-testing) Requires: libruby.so.2.0()(64bit)Error: Package: rubygem-yajl-ruby-1.2.1-1.el7.x86_64 (centos-opstools-testing) Requires: libruby.so.2.0()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest* But then I activated the node again and now I could check and start the upgrade from the engine portal. I faced this last time also. This is the reason I wanted to know the exact procedure of upgrading the ovirt-ng nodes. On Sun, Feb 5, 2017 at 4:09 PM, Yedidyah Bar David <d...@redhat.com> wrote: > (Re-adding the list) > > On Sun, Feb 5, 2017 at 12:23 PM, Shalabh Goel <shalabhgoe...@gmail.com> > wrote: > > Yes and no. First I did install ovirtrelease41 rpm in both nodes. Then in > > one of the nodes, I started upgrade from the court engine administration > > portal. > > The second node developed some other problem and hence I had to remove it > > from the court engine and I reinstalled ovirt 4.0.3 ng and then upgraded > it > > before adding it to the engine. It got upgraded successfully and I > rebooted > > and logged into 4.1 too. > > > > But I am getting the same error for both the nodes. The first one was > moved > > to non operational state by the engine. The second one is not getting > added. > > > &g
Re: [ovirt-users] problem after rebooting the node
Yes, I am using OVS as the switch type and I did not know that it was not
supported officially.
The output of ovs-vsctl show is as follows:
f634d53e-4849-488b-8454-6b1fafa7c6ac
ovs_version: "2.6.90"
I am attaching OVS switch logs below:
/var/log/openvswitch/ovsdb-server.log
2017-02-06T09:46:07.788Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovsdb-server.log
2017-02-06T09:46:07.791Z|2|ovsdb_server|INFO|ovsdb-server (Open
vSwitch) 2.6.90
2017-02-06T09:46:17.802Z|3|memory|INFO|2296 kB peak resident set size
after 10.0 seconds
2017-02-06T09:46:17.802Z|4|memory|INFO|cells:16 json-caches:1
monitors:1 sessions:1
ovs-vswitchd.log
2017-02-06T09:46:07.999Z|1|vlog|INFO|opened log file
/var/log/openvswitch/ovs-vswitchd.log
2017-02-06T09:46:08.036Z|2|ovs_numa|INFO|Discovered 24 CPU cores on
NUMA node 0
2017-02-06T09:46:08.036Z|3|ovs_numa|INFO|Discovered 24 CPU cores on
NUMA node 1
2017-02-06T09:46:08.036Z|4|ovs_numa|INFO|Discovered 2 NUMA nodes and 48
CPU cores
2017-02-06T09:46:08.037Z|5|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connecting...
2017-02-06T09:46:08.037Z|6|reconnect|INFO|unix:/var/run/openvswitch/db.sock:
connected
2017-02-06T09:46:08.039Z|7|bridge|INFO|ovs-vswitchd (Open vSwitch)
2.6.90
What should I do now?
The engine says that "Host host2 does not comply with the cluster Default
networks, the following networks are missing on host: 'ovirtmgmt'"
What other logs should I attach?
Thanks
Shalabh Goel
On Sun, Feb 5, 2017 at 1:10 PM, Edward Haas <eh...@redhat.com> wrote:
> Based on what I can see, you used OVS as the switch type and it seems ovs
> (openvswitch) is not properly installed on your host.
> Make sure that you have ovs operational by issuing "ovs-vsctl show".
>
> You should note that OVS network support is not an official release
> feature, and you should use it on 4.1 and up versions.
> Fixes will be probably submitted to master (appearing in nightly builds).
>
> Next time please include the mailing-list in your replies and attach the
> log files, it is less spamming.
>
> Thanks,
> Edy.
>
> On Fri, Feb 3, 2017 at 5:07 AM, Shalabh Goel <shalabhgoe...@gmail.com>
> wrote:
>
>> log from messages
>>
>> Feb 3 08:27:53 ovirtnode3 ovs-vsctl:
>> ovs|1|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock:
>> database connection failed (No such file or directory)
>> Feb 3 08:27:53 ovirtnode3 journal: vdsm vds ERROR Executing commands
>> failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
>> connection failed (No su
>> ch file or directory)#012Traceback (most recent call last):#012 File
>> "/usr/share/vdsm/API.py", line 1531, in setupNetworks#012
>> supervdsm.getProxy().setup
>> Networks(networks, bondings, options)#012 File
>> "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 53, in
>> __call__#012return callMethod()#012 Fi
>> le "/usr/lib/python2.7/site-packages/vdsm/supervdsm.py", line 51, in
>> #012**kwargs)#012 File "", line 2, in
>> setupNetworks#012 File "/usr
>> /lib64/python2.7/multiprocessing/managers.py", line 773, in
>> _callmethod#012raise convert_to_error(kind,
>> result)#012ConfigNetworkError: (21, 'Executing co
>> mmands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database
>> connection failed (No such file or directory)')
>>
>> Log from vdsm.log
>>
>> Reactor thread::INFO::2017-02-03 08:32:24,638::protocoldetector
>> ::72::ProtocolDetector.AcceptorImpl::(handle_accept) Accepted connection
>> from ::1:53082
>> Reactor thread::DEBUG::2017-02-03 08:32:24,643::protocoldetector
>> ::91::ProtocolDetector.Detector::(__init__) Using required_size=11
>> Reactor thread::INFO::2017-02-03 08:32:24,643::protocoldetector
>> ::127::ProtocolDetector.Detector::(handle_read) Detected protocol xml
>> from ::1:53082
>> Reactor thread::DEBUG::2017-02-03 08:32:24,643::bindingxmlrpc::1
>> 317::XmlDetector::(handle_socket) xml over http detected from ('::1',
>> 53082)
>> BindingXMLRPC::INFO::2017-02-03
>> 08:32:24,643::xmlrpc::73::vds.XMLRPCServer::(handle_request)
>> Starting request handler for ::1:53082
>> Thread-20::INFO::2017-02-03 08:32:24,644::xmlrpc::83::vds.
>> XMLRPCServer::(_process_requests) Request handler for ::1:53082 started
>> Thread-20::DEBUG::2017-02-03
>> 08:32:24,644::bindingxmlrpc::1263::vds::(wrapper)
>> client [::1]::call getAllVmStats with () {}
>> Thread-20::DEBUG::2017-02-03
>> 08:32:24,644::bindingxmlrpc::1270::vds::(wrapper)
>> return getAllVmStats with {'status': {'message': 'Done', 'code': 0},
>> 'statsLis
>> t': (suppr
Re: [ovirt-users] [Call for feedback] did you install/update to 4.1.0?
HI, I am having the following issue in two of my nodes after upgrading. The ovirt engine says that it is not able to find ovirtmgmt network on the nodes and hence the nodes are set to non-operational. More details are in the following message. Thanks Shalabh Goel > -- > > Message: 2 > Date: Thu, 2 Feb 2017 17:40:05 +0530 > From: Shalabh Goel <shalabhgoe...@gmail.com> > To: users <users@ovirt.org> > Subject: [ovirt-users] problem after rebooting the node > Message-ID: >
Re: [ovirt-users] How to update ovirt nodes
Hi can u just confirm something for me? I had to change the existing ovirt-4.0 repos to ovirt 4.1 (by replacing 40 by 41 in the repo files). And then I ran yum update. And rebooted the nodes and booted into ovirt-node4.1. Is the procedure correct? Thanks Shalabh Goel On Thu, Feb 2, 2017 at 2:02 PM, Yedidyah Bar David <d...@redhat.com> wrote: > On Thu, Feb 2, 2017 at 8:14 AM, Shalabh Goel <shalabhgoe...@gmail.com> > wrote: > > Hi > > > > Ovirt 4.1 has been released, I want to to know how to upgrade the Ovirt > > nodes to 4.1. I was able to upgrade ovirt-engine but I could not find > how to > > upgrade node. > > Something like: > > 1. Move node to maintenance > 2. Add 4.1 repos > 3. yum update > 4. reboot > 5. Activate (exit maintenance) > > See also: > > https://www.ovirt.org/node/ > http://www.ovirt.org/node/faq/ > > If in "node" you referred to ovirt-node, and not a regular OS install, then > the flow is exactly the same, but what actually happens inside it is very > different - the entire OS image is replaced. > > You might want to check also: > > http://www.ovirt.org/develop/release-management/features/ > engine/upgrademanager/ > > Best, > -- > Didi > -- Shalabh Goel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] problem after rebooting the node
HI, I am getting the following error on my node after rebooting it. VDSM ovirtnode2 command HostSetupNetworksVDS failed: Executing commands failed: ovs-vsctl: unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) To solve this, I am trying to restart ovsdb-server using the following command, ovsdb-server --remote=punix:*/var/run/openvswitch/db.sock* --remote=db:Open_vSwitch,Open_vSwitch,manager_options --private-key=db:Open_vSwitch,SSL,private_key--certificate=db:Open_vSwitch,SSL,certificate --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --pidfile --detach But I am getting the following error. ovsdb-server: /var/run/openvswitch/ovsdb-server.pid.tmp: create failed (No such file or directory) How to restart the ovsdb-server?? Also ovirtmgmt network is missing from my node. It happened after I rebooted my node after it got upgraded to Ovirt 4.1 -- Shalabh Goel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] How to update ovirt nodes
Hi Ovirt 4.1 has been released, I want to to know how to upgrade the Ovirt nodes to 4.1. I was able to upgrade ovirt-engine but I could not find how to upgrade node. Thank You -- Shalabh Goel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Video performance
More from the output of top command: %Cpu(s): 2.4 us, 0.4 sy, 0.0 ni, 97.1 id, 0.1 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 13182395+total, 10438806+free, 4205056 used, 23230840 buff/cache KiB Swap: 4194300 total, 4194300 free,0 used. 12692883+avail Mem -- Shalabh Goel On Thu, Jan 5, 2017 at 3:32 PM, Shalabh Goel <shalabhgoe...@gmail.com> wrote: > One more thing. When I close the video, the CPU usage by qemu reduces to 6 > % or lesser. > > -- > Shalabh Goel > > > On Thu, Jan 5, 2017 at 3:31 PM, Shalabh Goel <shalabhgoe...@gmail.com> > wrote: > >> Hi, >> >> I have installed ovirt engine 4.0.5 on centos 7.3. I installed ovirt-node >> on a separate phyical system and added it to ovirt-engine. I installed >> windows 7 in a VM on the node. I installed all the virtio drivers in the >> guest. The protocol used by me to access VM is Spice QXL. I have installed >> virt-viewer on the clients to access (one is windows and othe ris ubuntu) >> Now, when I pay the sample video "wildlife" in the windows the video >> frame rate is very low and it is skipping a aot of frames. I tested it on >> both of the clients. The screen resolution is 1280x1024 on ubuntu and >> 1366x768 on windows. >> >> The *lscpu* output of the node is: >> >> Architecture: x86_64 >> CPU op-mode(s):32-bit, 64-bit >> Byte Order:Little Endian >> CPU(s):48 >> On-line CPU(s) list: 0-47 >> Thread(s) per core:2 >> Core(s) per socket:12 >> Socket(s): 2 >> NUMA node(s): 2 >> Vendor ID: GenuineIntel >> CPU family:6 >> Model: 62 >> Model name:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz >> Stepping: 4 >> CPU MHz: 3047.097 >> BogoMIPS: 5406.43 >> Virtualization:VT-x >> L1d cache: 32K >> L1i cache: 32K >> L2 cache: 256K >> L3 cache: 30720K >> NUMA node0 CPU(s): 0-11,24-35 >> NUMA node1 CPU(s): 12-23,36-47 >> >> The top command output is showing the following on the node: >> >> PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ >> COMMAND >> >> 30219 qemu 20 0 5040176 4.048g 13564 S 113.2 3.2 16:05.49 >> qemu-kvm >> >> 6178 root 15 -5 1495476 48092 10676 S 28.1 0.0 300:58.82 >> supervdsmServer >> >> 361 root 25 5 0 0 0 S 7.0 0.0 333:14.58 >> ksmd >> >> 265 root rt 0 0 0 0 S 2.6 0.0 0:06.80 >> migration/32 >> >> 27504 qemu 20 0 5137240 4.412g 13516 S 2.6 3.5 10:53.39 >> qemu-kvm >> >> 30222 root 20 0 0 0 0 S 2.0 0.0 0:11.98 >> vhost-30219 >> >> 6329 vdsm 0 -20 3258204 151772 13004 S 0.7 0.1 65:29.75 vdsm >> >> - >> Please suggest what should I do to improve the video performance. >> >> Thank You >> >> Shalabh Goel >> > > > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Video performance
One more thing. When I close the video, the CPU usage by qemu reduces to 6 % or lesser. -- Shalabh Goel On Thu, Jan 5, 2017 at 3:31 PM, Shalabh Goel <shalabhgoe...@gmail.com> wrote: > Hi, > > I have installed ovirt engine 4.0.5 on centos 7.3. I installed ovirt-node > on a separate phyical system and added it to ovirt-engine. I installed > windows 7 in a VM on the node. I installed all the virtio drivers in the > guest. The protocol used by me to access VM is Spice QXL. I have installed > virt-viewer on the clients to access (one is windows and othe ris ubuntu) > Now, when I pay the sample video "wildlife" in the windows the video > frame rate is very low and it is skipping a aot of frames. I tested it on > both of the clients. The screen resolution is 1280x1024 on ubuntu and > 1366x768 on windows. > > The *lscpu* output of the node is: > > Architecture: x86_64 > CPU op-mode(s):32-bit, 64-bit > Byte Order:Little Endian > CPU(s):48 > On-line CPU(s) list: 0-47 > Thread(s) per core:2 > Core(s) per socket:12 > Socket(s): 2 > NUMA node(s): 2 > Vendor ID: GenuineIntel > CPU family:6 > Model: 62 > Model name:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz > Stepping: 4 > CPU MHz: 3047.097 > BogoMIPS: 5406.43 > Virtualization:VT-x > L1d cache: 32K > L1i cache: 32K > L2 cache: 256K > L3 cache: 30720K > NUMA node0 CPU(s): 0-11,24-35 > NUMA node1 CPU(s): 12-23,36-47 > > The top command output is showing the following on the node: > > PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ > COMMAND > > 30219 qemu 20 0 5040176 4.048g 13564 S 113.2 3.2 16:05.49 > qemu-kvm > > 6178 root 15 -5 1495476 48092 10676 S 28.1 0.0 300:58.82 > supervdsmServer > > 361 root 25 5 0 0 0 S 7.0 0.0 333:14.58 > ksmd > > 265 root rt 0 0 0 0 S 2.6 0.0 0:06.80 > migration/32 > > 27504 qemu 20 0 5137240 4.412g 13516 S 2.6 3.5 10:53.39 > qemu-kvm > > 30222 root 20 0 0 0 0 S 2.0 0.0 0:11.98 > vhost-30219 > > 6329 vdsm 0 -20 3258204 151772 13004 S 0.7 0.1 65:29.75 vdsm > > - > Please tell me what should I do to improve the video performance. > > Thank You > > Shalabh Goel > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Video performance
Hi, I have installed ovirt engine 4.0.5 on centos 7.3. I installed ovirt-node on a separate phyical system and added it to ovirt-engine. I installed windows 7 in a VM on the node. I installed all the virtio drivers in the guest. The protocol used by me to access VM is Spice QXL. I have installed virt-viewer on the clients to access (one is windows and othe ris ubuntu) Now, when I pay the sample video "wildlife" in the windows the video frame rate is very low and it is skipping a aot of frames. I tested it on both of the clients. The screen resolution is 1280x1024 on ubuntu and 1366x768 on windows. The *lscpu* output of the node is: Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):48 On-line CPU(s) list: 0-47 Thread(s) per core:2 Core(s) per socket:12 Socket(s): 2 NUMA node(s): 2 Vendor ID: GenuineIntel CPU family:6 Model: 62 Model name:Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz Stepping: 4 CPU MHz: 3047.097 BogoMIPS: 5406.43 Virtualization:VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 30720K NUMA node0 CPU(s): 0-11,24-35 NUMA node1 CPU(s): 12-23,36-47 The top command output is showing the following on the node: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 30219 qemu 20 0 5040176 4.048g 13564 S 113.2 3.2 16:05.49 qemu-kvm 6178 root 15 -5 1495476 48092 10676 S 28.1 0.0 300:58.82 supervdsmServer 361 root 25 5 0 0 0 S 7.0 0.0 333:14.58 ksmd 265 root rt 0 0 0 0 S 2.6 0.0 0:06.80 migration/32 27504 qemu 20 0 5137240 4.412g 13516 S 2.6 3.5 10:53.39 qemu-kvm 30222 root 20 0 0 0 0 S 2.0 0.0 0:11.98 vhost-30219 6329 vdsm 0 -20 3258204 151772 13004 S 0.7 0.1 65:29.75 vdsm - Please tell me what should I do to improve the video performance. Thank You Shalabh Goel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Unable to connect to console in user portal
This is the rpm installed in my server. *ovirt-release40-4.0.5-2.noarch*Looks like I have ovirt 4.0.5 installed. How to upgrade to 4.0.6? @Pavel, yes disabling Single sign-on worked. Thanks a lot everyone. Shalabh Goel On Thu, Jan 5, 2017 at 2:46 PM, Tomas Jelinek <tjeli...@redhat.com> wrote: > It looks like you are hitting this bug: https://bugzilla.redhat. > com/show_bug.cgi?id=1391146 > > It should have been fixed in 4.0.6. What exact version of ovirt-engine do > you have? > > On Thu, Jan 5, 2017 at 8:16 AM, Pavel Gashev <p...@acronis.com> wrote: > >> Shalabh, >> >> >> >> Does it help to disable SSO on that VM? >> >> >> >> >> >> *From: *<users-boun...@ovirt.org> on behalf of Shalabh Goel < >> shalabhgoe...@gmail.com> >> *Date: *Wednesday 4 January 2017 at 14:55 >> *To: *users <users@ovirt.org> >> *Subject: *[ovirt-users] Unable to connect to console in user portal >> >> >> >> Hi, >> >> I have created two VMs on a node. Then I created a user and gave >> permission to the user for both as UserRole from the web console. Now when >> I login as the user to the user portal, I can see both the VMs. But when I >> click connect or double-click on a particular VM, I get an error message >> "Error while executing action VmLogon: Internal Engine Error". >> >> The ovirt engine and node version is 4.0. >> >> >> >> Please help >> >> >> >> Thank You >> >> Shalabh Goel >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Unable to connect to console in user portal
[org.ovirt.engine.core.vdsbroker.vdsbroker.VmLogonVDSCommand] (default task-121) [29e83352] FINISH, VmLogonVDSCommand, log id: 24f3041c 2017-01-05 16:35:55,369 ERROR [org.ovirt.engine.core.bll.VmLogonCommand] (default task-121) [29e83352] Unable to execute VmLogon with message EngineException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to VmLogonVDS, error = Guest agent non-responsive, code = 19 (Failed with error nonresp and code 19) 2017-01-05 16:35:55,376 ERROR [org.ovirt.engine.core.bll.VmLogonCommand] (default task-121) [29e83352] Transaction rolled-back for command 'org.ovirt.engine.core.bll.VmLogonCommand'. 2017-01-05 16:36:02,070 WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData] (DefaultQuartzScheduler3) [] Domain 'f04c189e-c3a8-414d-822a-5846488773b3:iso-win10host' report isn't an actual report 2017-01-05 16:36:02,070 WARN [org.ovirt.engine.core.vdsbroker.irsbroker.IrsProxyData] (DefaultQuartzScheduler3) [] Domain '2f039ab5-6f76-4461-bb19-5a0272ce5520:vmdata-hostwin10' report isn't an actual report The log from server.log file is as follows: 2017-01-05 16:35:51,813 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-106) Skipped sending the field org.ovirt.engine.core.common.migration.MigrationPolicy.config because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:51,814 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-106) Skipped sending the field org.ovirt.engine.core.common.migration.ConvergenceConfig.convergenceItems because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:51,814 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-106) Skipped sending the field org.ovirt.engine.core.common.migration.ConvergenceConfig.initialItems because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:51,814 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-106) Skipped sending the field org.ovirt.engine.core.common.migration.ConvergenceConfig.lastItems because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:51,815 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-106) Skipped sending the field org.ovirt.engine.core.common.migration.ConvergenceItemWithStallingLimit.convergenceItem because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:51,815 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-106) Skipped sending the field org.ovirt.engine.core.common.migration.ConvergenceItem.params because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:55,403 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-121) Skipped sending the field org.ovirt.engine.core.common.errors.EngineFault.privateDetails because it's unused in the client. It should either be changed to transient or removed. 2017-01-05 16:35:55,404 WARNING [com.google.gwt.rpc.server.WebModePayloadSink] (default task-121) Skipped sending the field org.ovirt.engine.core.common.errors.EngineFault.privateSessionID because it's unused in the client. It should either be changed to transient or removed. Thank You Shalabh Goel On Wed, Jan 4, 2017 at 9:56 PM, Alexander Wels <aw...@redhat.com> wrote: > On Wednesday, January 4, 2017 5:25:56 PM EST Shalabh Goel wrote: > > Hi, > > > > I have created two VMs on a node. Then I created a user and gave > permission > > to the user for both as UserRole from the web console. Now when I login > as > > the user to the user portal, I can see both the VMs. But when I click > > connect or double-click on a particular VM, I get an error message "Error > > while executing action VmLogon: Internal Engine Error". > > > > Can you provide us with the engine logs. The engine is giving an internal > server error which is bad and shouldn't happen, but obviously it did and > its > highly likely there is a stack trace in the logs that will give us some > idea > what is going on. > > > The ovirt engine and node version is 4.0. > > > > Please help > > > > Thank You > > > > Shalabh Goel > > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Unable to connect to console in user portal
Hi, I have created two VMs on a node. Then I created a user and gave permission to the user for both as UserRole from the web console. Now when I login as the user to the user portal, I can see both the VMs. But when I click connect or double-click on a particular VM, I get an error message "Error while executing action VmLogon: Internal Engine Error". The ovirt engine and node version is 4.0. Please help Thank You Shalabh Goel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] Ovirt node host installation failing in engine
Thanks it worked. The host was installed and added to the cluster
successfully.
On Wed, Nov 30, 2016 at 6:33 PM, Yedidyah Bar David <d...@redhat.com> wrote:
> (Replying to the list and Fabian as well)
>
> On Wed, Nov 30, 2016 at 12:45 PM, Shalabh Goel <shalabhgoe...@gmail.com>
> wrote:
> > Thanks for the reply. I looked into the logs in ovirt-engine server. The
> log
> > is as follows:
> >
> > File "/usr/lib/python2.7/site-packages/yum/repos.py", line 344, in
> > populateSack
> > self.doSetup()
> > File "/usr/lib/python2.7/site-packages/yum/repos.py", line 158, in
> doSetup
> > self.ayum.plugins.run('postreposetup')
> > File "/usr/lib/python2.7/site-packages/yum/plugins.py", line 188, in
> run
> > func(conduitcls(self, self.base, conf, **kwargs))
> > File "/usr/lib/yum-plugins/fastestmirror.py", line 197, in
> > postreposetup_hook
> > if downgrade_ftp and _len_non_ftp(repo.urls) == 1:
> > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 871, in
> >
> > urls = property(fget=lambda self: self._geturls(),
> > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 868, in
> > _geturls
> > self._baseurlSetup()
> > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 834, in
> > _baseurlSetup
> > self.check()
> > File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 554, in
> check
> > 'Cannot find a valid baseurl for repo: %s' % self.ui_id
> > RepoError: Cannot find a valid baseurl for repo: ovirt-4.0/7
> > 2016-11-24 11:24:24 ERROR otopi.context context._executeMethod:151
> Failed to
> > execute stage 'Environment packages setup': Cannot find a valid baseurl
> for
> > repo
> > : ovirt-4.0/7
> > 2016-11-24 11:24:24 DEBUG otopi.transaction transaction.abort:119
> aborting
> > 'Yum Transaction'
> > 2016-11-24 11:24:24 INFO otopi.plugins.otopi.packagers.yumpackager
> > yumpackager.info:80 Yum Performing yum transaction rollback
> > Could not retrieve mirrorlist
> > http://resources.ovirt.org/pub/yum-repo/mirrorlist-ovirt-4.0-el7 error
> was
> > 14: curl#7 - "Failed to connect to 66.187.230.28: Network is
> unreachable"
> > Loaded plugins: fastestmirror
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:760
> > ENVIRONMENT DUMP - BEGIN
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:770 ENV
> > BASE/error=bool:'True'
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:770 ENV
> > BASE/exceptionInfo=list:'[(, RepoError(),
> > > ject at 0x2e88c20>)]'
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:774
> > ENVIRONMENT DUMP - END
> > 2016-11-24 11:24:24 INFO otopi.context context.runSequence:687 Stage:
> > Pre-termination
> > 2016-11-24 11:24:24 DEBUG otopi.context context.runSequence:691 STAGE
> > pre-terminate
> > 2016-11-24 11:24:24 DEBUG otopi.context context._executeMethod:128 Stage
> > pre-terminate METHOD otopi.plugins.otopi.core.misc.Plugin._preTerminate
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:760
> > ENVIRONMENT DUMP - BEGIN
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:770 ENV
> > BASE/aborted=bool:'False'
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:770 ENV
> > BASE/debug=int:'0'
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:770 ENV
> > BASE/error=bool:'True'
> > 2016-11-24 11:24:24 DEBUG otopi.context context.dumpEnvironment:770 ENV
> > BASE/exceptionInfo=list:'[(, RepoError(),
> > > :
> >
> > So my question is that if yum is the reason for the host install
> failing? Do
> > I absolutely need Internet connectivity for the node also? What if the
> > python file can be edited to prevent it? I have installed the node using
> the
> > node ISO available on the ovirt website
>
> Not sure about node specifically.
>
> You can try preventing host-deploy from trying to update packages using:
>
> https://gerrit.ovirt.org/gitweb?p=ovirt-host-deploy.git;a=blob;f=README
>
> Search there for 'OFFLINE'.
>
> Best,
>
> >
> > Thank You
> >
> > Shalabh Goel
> >
> > On Wed, Nov 30, 2016 at 2:03 PM, Yedidyah Bar David <d...@redhat.com>
> wrote:
> >>
> >> On Wed, Nov 30, 2016 at 9:44 AM, Shalabh Goel <shalabhgoe...@gmail.com>
> >> wrote:
> >> > Hi
> >> >
> >> > I just want to kno
[ovirt-users] Ovirt node host installation failing in engine
Hi I have installed ovirt engine (version 4) on Centos 7.2 in one server system and 1 ovirt node (version 4) using ovirt node iso in another system. But when am adding the node in the engine from web portal, the installation is failing on the node. There is no Internet connectivity to the node. When I checked the logs, I found that it is trying to connect to a repo using yum. My questions are: 1. Is internet connectivity required on the node? 2. If I cannot provide internet connectivity to the node. Please suggest a work around. Thank You Shalabh Goel ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
