[oVirt 4.2 Localization Question #3] VAR__ACTION__TRANSFER
by Yuko Katabami
Hello oVirt developers.
Here is our question #3.
*File: *AppErrors
*Resource ID: *VAR__ACTION__TRANSFER
*String: *$action transfer
*Question:* When this is used in "Cannot ${action} ${type}. ", what "type"
this action is combined with? (i.e. what is transferred?)
Thank you,
Yuko
7 years, 1 month
[ OST Failure Report ] [ oVirt master ] [ 26-10-2017 ] [ 004_basic_sanity.add_nic ]
by Shlomo Ben David
Hi,
Link to suspected patches: https://gerrit.ovirt.org/#/c/71622/6
Link to Job:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3476/console
Link to all logs:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3476/artifa...
(Relevant) error snippet from the log:
<error>
Traceback (most recent call last): File
"/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File
"/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg) File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, in
wrapped_test test() File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in
wrapper return func(get_test_prefix(), *args, **kwargs) File
"/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 68, in
wrapper return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs)
File
"/home/jenkins/workspace/ovirt-master_change-queue-tester/ovirt-system-tests/basic-suite-master/test-scenarios/004_basic_sanity.py",
line 147, in add_nic api.vms.get(VM2_NAME).nics.add(nic_params) File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line
33398, in add headers={"Correlation-Id":correlation_id, "Expect":expect}
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 79, in add return self.request('POST', url, body, headers, cls=cls)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py",
line 122, in request persistent_auth=self.__persistent_auth File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py",
line 79, in do_request persistent_auth) File
"/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py",
line 162, in __do_request raise errors.RequestError(response_code,
response_reason, response_body) RequestError: status: 400 reason: Bad
Request detail:
</error>
Best Regards,
Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
RHCSA | RHCE | RHCVA
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
7 years, 1 month
oVirt Guest Agent maintainer
by Tomáš Golembiovský
Hi,
I don't remember if this was properly announced before so here it goes.
Some of you already know that.
I've been maintaining the ovirt-guest-agent related things for about
half a year (Vinzenz Feenstra is no longer with us). Recently I've been
also granted merge rights to the project on Gerrit. You may still find
Vinzenz's name mentioned on lots of places, but if you need anything GA
related you should contact me and not him.
Cheers,
Tomas
--
Tomáš Golembiovský <tgolembi(a)redhat.com>
7 years, 1 month
taskset (in supervdsm) for all CPUs?
by Yaniv Kaul
I'm looking at some supervdsm log, and I'm seeing these commands:
/usr/bin/taskset --cpu-list 0-55 /usr/libexec/vdsm/fc-scan
and:
/usr/bin/taskset --cpu-list 0-55 /usr/bin/mount -t nfs -o
soft,nosharecache,timeo=600,retrans=6 10.10.10.1:/NFS/images
And so on (also for iscsiadm).
Why do we need to taskset commands if we allow them to run on all CPUs? Why
would we allow them to run on all CPUs anyway?
7 years, 1 month
[oVirt 4.2 Localization Question #1] ACTION_TYPE_FAILED_AFFINITY_HOSTS_RULES_COLLISION
by Yuko Katabami
Hello oVirt developers.
I have started translating Admin Portal strings for 4.2 from today and here
is my first question.
*File: *AppErrors
*Resource ID: *ACTION_TYPE_FAILED_AFFINITY_HOSTS_RULES_COLLISION
*String: *The following affinity groups, containing the indicated hosts and
VMs, have VM to host conflicts between positive and negative enforcing
affinity groups.
*Question:* Does "the indicated hosts and VMs" mean the hosts and VMs
specified by user? Could you please also explain what "VM to host
conflicts" mean?
Kind regards,
Yuko
7 years, 1 month
vdsm spec file rpmlint
by Sandro Bonazzola
Just an heads up we have improvement margin on vdsm spec file quality.
[sbonazzo@sbonazzo SPECS]$ rpmlint ./vdsm.spec
/var/lib/mock/epel-7-x86_64/result/*rpm
vdsm.x86_64: E: explicit-lib-dependency libnl3
vdsm.x86_64: E: explicit-lib-dependency libvirt-client
vdsm.x86_64: E: explicit-lib-dependency libvirt-daemon-config-nwfilter
vdsm.x86_64: E: explicit-lib-dependency libvirt-lock-sanlock
vdsm.x86_64: W: obsolete-not-provided vdsm-infra
vdsm.x86_64: E: no-binary
vdsm.x86_64: W: conffile-without-noreplace-flag /var/log/vdsm/mom.log
vdsm.x86_64: W: conffile-without-noreplace-flag /var/log/vdsm/supervdsm.log
vdsm.x86_64: W: conffile-without-noreplace-flag /var/log/vdsm/vdsm.log
vdsm.x86_64: W: non-conffile-in-etc /etc/NetworkManager/conf.d/vdsm.conf
vdsm.x86_64: W: non-conffile-in-etc
/etc/modprobe.d/vdsm-bonding-modprobe.conf
vdsm.x86_64: E: non-readable /etc/pki/vdsm/keys/libvirt_password 600
vdsm.x86_64: W: non-conffile-in-etc /etc/security/limits.d/99-vdsm.conf
vdsm.x86_64: W: non-conffile-in-etc /etc/sudoers.d/50_vdsm
vdsm.x86_64: W: systemd-unit-in-etc
/etc/systemd/system/libvirtd.service.d/unlimited-core.conf
vdsm.x86_64: W: non-conffile-in-etc
/etc/systemd/system/libvirtd.service.d/unlimited-core.conf
vdsm.x86_64: E: zero-length /etc/vdsm/mom.d/01-parameters.policy
vdsm.x86_64: E: wrong-script-interpreter /usr/libexec/vdsm/kvm2ovirt
/usr/bin/env python
vdsm.x86_64: E: wrong-script-interpreter
/usr/libexec/vdsm/vm_migrate_hook.py /usr/bin/env python
vdsm.x86_64: E: wrong-script-interpreter
/usr/share/vdsm/virt/vm_migrate_hook.py /usr/bin/env python
vdsm.x86_64: E: non-executable-script
/usr/share/vdsm/virt/vm_migrate_hook.py 644 /usr/bin/env python
vdsm.x86_64: E: non-standard-dir-perm /var/lib/libvirt/qemu/channels 775
vdsm.x86_64: E: non-standard-dir-perm /var/log/core 1777
vdsm.x86_64: E: dir-or-file-in-var-run /var/run/vdsm
vdsm.x86_64: E: dir-or-file-in-var-run /var/run/vdsm/payload
vdsm.x86_64: E: dir-or-file-in-var-run /var/run/vdsm/sourceRoutes
vdsm.x86_64: E: dir-or-file-in-var-run /var/run/vdsm/trackedInterfaces
vdsm.x86_64: E: dir-or-file-in-var-run /var/run/vdsm/v2v
vdsm.x86_64: W: log-files-without-logrotate ['/var/log/core',
'/var/log/vdsm']
vdsm.x86_64: W: dangerous-command-in-%pre rpm
vdsm.x86_64: W: dangerous-command-in-%post chmod
vdsm-api.noarch: E: wrong-script-interpreter
/usr/lib/python2.7/site-packages/vdsm/api/vdsmapi.py /usr/bin/env python
vdsm-api.noarch: E: non-executable-script
/usr/lib/python2.7/site-packages/vdsm/api/vdsmapi.py 644 /usr/bin/env python
vdsm-cli.noarch: W: non-conffile-in-etc /etc/bash_completion.d/vdsClient
vdsm-gluster.noarch: W: spelling-error %description -l en_US
functionalities -> functionalists, functionality, functionalist
vdsm-gluster.noarch: W: no-documentation
vdsm-hook-allocate_net.noarch: W: summary-not-capitalized C random_network
allocation hook for VDSM
vdsm-hook-allocate_net.noarch: W: spelling-error %description -l en_US vms
-> vs, ms, ems
vdsm-hook-allocate_net.noarch: W: no-documentation
vdsm-hook-allocate_net.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/before_device_create/10_allocate_net /usr/bin/env
python
vdsm-hook-checkimages.noarch: W: no-documentation
vdsm-hook-checkips.x86_64: W: no-documentation
vdsm-hook-checkips.x86_64: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/after_get_stats/10_checkips /usr/bin/env python
vdsm-hook-checkips.x86_64: E: non-executable-script
/usr/libexec/vdsm/hooks/after_get_stats/checkips_utils.py 644
/usr/bin/python2
vdsm-hook-diskunmap.noarch: W: spelling-error Summary(en_US) lun -> loon,
lung, sun
vdsm-hook-diskunmap.noarch: W: no-documentation
vdsm-hook-diskunmap.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/before_vm_start/50_diskunmap /usr/bin/env python2
vdsm-hook-ethtool-options.noarch: W: spelling-error Summary(en_US) nics ->
incs, mics, nicks
vdsm-hook-ethtool-options.noarch: W: spelling-error %description -l en_US
nics -> incs, mics, nicks
vdsm-hook-ethtool-options.noarch: W: no-documentation
vdsm-hook-ethtool-options.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/after_network_setup/30_ethtool_options /usr/bin/env
python
vdsm-hook-extnet.noarch: W: spelling-error Summary(en_US) vNIC -> Venice
vdsm-hook-extnet.noarch: W: spelling-error Summary(en_US) libvirt ->
liberty, ovirt
vdsm-hook-extnet.noarch: W: spelling-error %description -l en_US vNIC ->
Venice
vdsm-hook-extnet.noarch: W: spelling-error %description -l en_US libvirt ->
liberty, ovirt
vdsm-hook-extnet.noarch: W: spelling-error %description -l en_US
openvswitch -> switchboard
vdsm-hook-extnet.noarch: W: no-documentation
vdsm-hook-extra-ipv4-addrs.x86_64: W: summary-ended-with-dot C Set extra
ipv4 addresses for vdsm networks.
vdsm-hook-extra-ipv4-addrs.x86_64: W: no-documentation
vdsm-hook-extra-ipv4-addrs.x86_64: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/after_network_setup/40_extra_ipv4_addrs
/usr/bin/env python
vdsm-hook-fakesriov.x86_64: W: spelling-error %description -l en_US
hostdevListByCaps
vdsm-hook-fakesriov.x86_64: W: spelling-error %description -l en_US sriov
-> Rios
vdsm-hook-fakesriov.x86_64: W: spelling-error %description -l en_US conf ->
con, cone, cons
vdsm-hook-fakesriov.x86_64: W: no-documentation
vdsm-hook-fakevmstats.noarch: W: spelling-error %description -l en_US
vmstats -> stats
vdsm-hook-fakevmstats.noarch: W: spelling-error %description -l en_US conf
-> con, cone, cons
vdsm-hook-fakevmstats.noarch: W: no-documentation
vdsm-hook-faqemu.noarch: W: spelling-error Summary(en_US) qemu -> emu, q emu
vdsm-hook-faqemu.noarch: W: spelling-error %description -l en_US kvm -> km
vdsm-hook-faqemu.noarch: W: spelling-error %description -l en_US conf ->
con, cone, cons
vdsm-hook-faqemu.noarch: W: no-documentation
vdsm-hook-fcoe.noarch: W: no-documentation
vdsm-hook-fcoe.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/before_network_setup/50_fcoe /bin/env python
vdsm-hook-fileinject.noarch: W: no-documentation
vdsm-hook-floppy.noarch: W: no-documentation
vdsm-hook-hostusb.noarch: W: no-documentation
vdsm-hook-hostusb.noarch: E: non-readable
/etc/sudoers.d/50_vdsm_hook_hostusb 440
vdsm-hook-hostusb.noarch: W: non-conffile-in-etc
/etc/sudoers.d/50_vdsm_hook_hostusb
vdsm-hook-httpsisoboot.noarch: W: spelling-error Summary(en_US) https ->
HTTP
vdsm-hook-httpsisoboot.noarch: W: spelling-error %description -l en_US
https -> HTTP
vdsm-hook-httpsisoboot.noarch: W: spelling-error %description -l en_US http
-> HTTP
vdsm-hook-httpsisoboot.noarch: W: no-documentation
vdsm-hook-hugepages.noarch: W: summary-ended-with-dot C Huge pages enable
user to handle VM with 2048KB page files.
vdsm-hook-hugepages.noarch: W: no-documentation
vdsm-hook-hugepages.noarch: E: non-readable
/etc/sudoers.d/50_vdsm_hook_hugepages 440
vdsm-hook-hugepages.noarch: W: non-conffile-in-etc
/etc/sudoers.d/50_vdsm_hook_hugepages
vdsm-hook-ipv6.noarch: W: no-documentation
vdsm-hook-ipv6.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/before_network_setup/50_ipv6 /usr/bin/env python2
vdsm-hook-isolatedprivatevlan.noarch: W: spelling-error %description -l
en_US ip -> pi, up, op
vdsm-hook-isolatedprivatevlan.noarch: W: spelling-error %description -l
en_US filterref -> filter ref, filter-ref, filterer
vdsm-hook-isolatedprivatevlan.noarch: W: spelling-error %description -l
en_US xml -> XML, ml, x ml
vdsm-hook-isolatedprivatevlan.noarch: W: no-documentation
vdsm-hook-isolatedprivatevlan.noarch: E: executable-marked-as-config-file
/etc/libvirt/nwfilter/isolatedprivatevlan-vdsm.xml
vdsm-hook-isolatedprivatevlan.noarch: E: script-without-shebang
/etc/libvirt/nwfilter/isolatedprivatevlan-vdsm.xml
vdsm-hook-localdisk.noarch: W: spelling-error %description -l en_US lvm ->
lvi, lam, Lvov
vdsm-hook-localdisk.noarch: W: only-non-binary-in-usr-lib
vdsm-hook-localdisk.noarch: W: no-documentation
vdsm-hook-localdisk.noarch: E: non-readable
/etc/sudoers.d/50_vdsm_hook_localdisk 440
vdsm-hook-localdisk.noarch: W: non-conffile-in-etc
/etc/sudoers.d/50_vdsm_hook_localdisk
vdsm-hook-macbind.noarch: W: spelling-error Summary(en_US) vNIC -> Venice
vdsm-hook-macbind.noarch: W: spelling-error %description -l en_US vNIC ->
Venice
vdsm-hook-macbind.noarch: W: no-documentation
vdsm-hook-macbind.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/before_vm_start/50_macbind /usr/bin/env python2
vdsm-hook-macspoof.noarch: W: spelling-error %description -l en_US vnics ->
conics
vdsm-hook-macspoof.noarch: W: no-documentation
vdsm-hook-nestedvt.noarch: W: spelling-error %description -l en_US
virtualization -> visualization, actualization, vitalization
vdsm-hook-nestedvt.noarch: W: spelling-error %description -l en_US kvm -> km
vdsm-hook-nestedvt.noarch: W: no-documentation
vdsm-hook-nestedvt.noarch: W: non-conffile-in-etc
/etc/modprobe.d/vdsm-nestedvt.conf
vdsm-hook-noipspoof.noarch: W: no-documentation
vdsm-hook-numa.noarch: W: spelling-error %description -l en_US xml -> XML,
ml, x ml
vdsm-hook-numa.noarch: W: no-documentation
vdsm-hook-openstacknet.noarch: W: spelling-error Summary(en_US) vNICs ->
conics
vdsm-hook-openstacknet.noarch: W: spelling-error %description -l en_US
vNICs -> conics
vdsm-hook-openstacknet.noarch: W: no-documentation
vdsm-hook-openstacknet.noarch: E: non-readable
/etc/sudoers.d/50_vdsm_hook_openstacknet 440
vdsm-hook-openstacknet.noarch: W: non-conffile-in-etc
/etc/sudoers.d/50_vdsm_hook_openstacknet
vdsm-hook-openstacknet.noarch: E: wrong-script-interpreter
/usr/libexec/vdsm/hooks/before_device_migrate_destination/50_openstacknet
/usr/bin/env python2
vdsm-hook-pincpu.noarch: W: no-documentation
vdsm-hook-promisc.noarch: W: no-documentation
vdsm-hook-promisc.noarch: E: non-readable
/etc/sudoers.d/50_vdsm_hook_promisc 440
vdsm-hook-promisc.noarch: W: non-conffile-in-etc
/etc/sudoers.d/50_vdsm_hook_promisc
vdsm-hook-qemucmdline.noarch: W: spelling-error Summary(en_US) cmdline ->
decline
vdsm-hook-qemucmdline.noarch: W: spelling-error %description -l en_US
cmdline -> decline
vdsm-hook-qemucmdline.noarch: W: spelling-error %description -l en_US
libvirt's -> liberty's
vdsm-hook-qemucmdline.noarch: W: spelling-error %description -l en_US qemu
-> emu, q emu
vdsm-hook-qemucmdline.noarch: W: spelling-error %description -l en_US
commandline -> command line, command-line, commandment
vdsm-hook-qemucmdline.noarch: W: spelling-error %description -l en_US xml
-> XML, ml, x ml
vdsm-hook-qemucmdline.noarch: W: spelling-error %description -l en_US
namespace -> name space, name-space, names pace
vdsm-hook-qemucmdline.noarch: W: no-documentation
vdsm-hook-qos.noarch: W: no-documentation
vdsm-hook-scratchpad.noarch: W: no-documentation
vdsm-hook-smbios.noarch: W: spelling-error Summary(en_US) libvirt ->
liberty, ovirt
vdsm-hook-smbios.noarch: W: spelling-error %description -l en_US libvirt ->
liberty, ovirt
vdsm-hook-smbios.noarch: W: no-documentation
vdsm-hook-spiceoptions.noarch: W: spelling-error Summary(en_US) vm -> cm,
v, m
vdsm-hook-spiceoptions.noarch: W: no-documentation
vdsm-hook-vfio-mdev.noarch: W: summary-ended-with-dot C Hook to enable
mdev-capable devices.
vdsm-hook-vfio-mdev.noarch: W: no-documentation
vdsm-hook-vhostmd.noarch: W: no-documentation
vdsm-hook-vhostmd.noarch: E: non-readable
/etc/sudoers.d/50_vdsm_hook_vhostmd 440
vdsm-hook-vhostmd.noarch: W: non-conffile-in-etc
/etc/sudoers.d/50_vdsm_hook_vhostmd
vdsm-hook-vmdisk.noarch: W: no-documentation
vdsm-hook-vmfex.noarch: W: summary-not-capitalized C vmfex support for VDSM
vdsm-hook-vmfex.noarch: W: no-documentation
vdsm-hook-vmfex-dev.noarch: W: spelling-error Summary(en_US) vNIC -> Venice
vdsm-hook-vmfex-dev.noarch: W: spelling-error %description -l en_US vNIC ->
Venice
vdsm-hook-vmfex-dev.noarch: W: spelling-error %description -l en_US macvtap
-> madcap
vdsm-hook-vmfex-dev.noarch: W: no-documentation
vdsm-jsonrpc.noarch: W: spelling-error %description -l en_US libvdsm ->
liberalism
vdsm-jsonrpc.noarch: W: obsolete-not-provided vdsm-api
vdsm-jsonrpc.noarch: W: no-documentation
vdsm-python.noarch: E: non-executable-script
/usr/lib/python2.7/site-packages/vdsm/tool/dummybr.py 644 /usr/bin/python2
vdsm-python.noarch: E: non-executable-script
/usr/lib/python2.7/site-packages/vdsm/tool/nwfilter.py 644 /usr/bin/python2
vdsm-python.noarch: W: dangerous-command-in-%post rm
vdsm-tests.noarch: E: non-executable-script
/usr/share/vdsm/tests/alignmentScanTests.py 644 /usr/bin/python2
vdsm-tests.noarch: E: wrong-script-interpreter
/usr/share/vdsm/tests/fake-ssh-add /usr/bin/env python
vdsm-tests.noarch: E: non-executable-script
/usr/share/vdsm/tests/fake-ssh-add 644 /usr/bin/env python
vdsm-tests.noarch: E: wrong-script-interpreter
/usr/share/vdsm/tests/fake-ssh-agent /usr/bin/env python
vdsm-tests.noarch: E: non-executable-script
/usr/share/vdsm/tests/fake-ssh-agent 644 /usr/bin/env python
vdsm-tests.noarch: E: wrong-script-interpreter
/usr/share/vdsm/tests/fake-virt-v2v /usr/bin/env python
vdsm-tests.noarch: E: non-executable-script
/usr/share/vdsm/tests/fake-virt-v2v 644 /usr/bin/env python
vdsm-tests.noarch: E: script-without-shebang
/usr/share/vdsm/tests/testValidation.py
vdsm-tests.noarch: E: zero-length /usr/share/vdsm/tests/toolTests_empty.conf
vdsm-xmlrpc.noarch: W: spelling-error %description -l en_US vdsmd
vdsm-xmlrpc.noarch: W: spelling-error %description -l en_US vdsClient ->
clientele
vdsm-xmlrpc.noarch: W: no-documentation
vdsm-yajsonrpc.noarch: W: no-documentation
48 packages and 1 specfiles checked; 49 errors, 120 warnings.
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <https://www.redhat.com/>
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
<http://www.teraplan.it/redhat-osd-2017/>
7 years, 1 month
PCI device slot id allocation issue
by Mor Kalfon
Hello all,
My name is Mor, I am from the RHV networking team.
I am experiencing an issue with PCI device slot ID's and network interface
names that appear sometimes on my environment. I was advised to contact
this mailing-list in hope to get explanation or possible solution for this
issue.
The issue is the following:
On our oVirt 4.2 master environments, we create VM's from sealed template
that has only one vNIC attached to the ovirtmgmt network. Sometimes, and
now I am able to fully reproduce it on a specific VM, when I add new vNIC,
it gets allocated with lower PCI slot id, compared to what is allocated on
the default vNIC. For example, original one got slot id: 0xA, and newer one
got slot id: 0x3.
The order of slot ID's affects the network 'ethX' naming on the guest OS
(RHEL 7.4). Lower slot ID's gets numbered from 0 to N. The problem is that
if we had configuration for DHCP on 'eth0' and the order is changed, we can
lose connectivity to the host.
Can you please share your opinion on this issue?
Thanks,
--
Mor Kalfon
RHV Networking Team
Red Hat IL-Raanana
Tel: +972-54-6514148
7 years, 1 month
Slot ID allocation issue
by Mor Kalfon
Hello all,
My name is Mor, I am from the RHV networking team.
I am experiencing an issue with PCI device slot ID's and network interface
names that appear sometimes on my environment. I was advised to contact
this mailing-list in hope to get explanation or possible solution for this
issue.
The issue is the following:
On our oVirt 4.2 master environments, we create VM's from sealed template
that has only one vNIC attached to the ovirtmgmt network. Sometimes, and
now I am able to fully reproduce it on a specific VM, when I add new vNIC,
it gets allocated with lower PCI slot id, compared to what is allocated on
the default vNIC. For example, original one got slot id: 0xA, and newer one
got slot id: 0x3.
The order of slot ID's affects the network 'ethX' naming on the guest OS
(RHEL 7.4). Lower slot ID's gets numbered from 0 to N. The problem is that
if we had configuration for DHCP on 'eth0' and the order is changed, we can
lose connectivity to the host.
Can you please share your opinion on this issue?
Thanks,
--
Mor Kalfon
RHV Networking Team
Red Hat IL-Raanana
Tel: +972-54-6514148
7 years, 1 month
Host installation failure - master
by Yaniv Kaul
I'm failing to install hosts on o-s-t on Master.
What worries me is not that I'm failing (though it is a bit of a surprise,
perhaps something I've done?), but that there are no logs around it.
/var/log/ovirt-engine/host-deploy is empty and so is
/var/log/ovirt-engine/ansible.
All I'm seeing:
Host lago-basic-suite-master-host-0 installation failed. Unexpected
connection termination.
Server.log:
2017-10-23 12:16:33,041-04 WARN
[org.apache.sshd.client.session.ClientSessionImpl]
(sshd-SshClient[346b54f3]-nio2-thread-2) Exception caught:
java.io.IOException: Connection timed out
at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
[rt.jar:1.8.0_151]
at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
[rt.jar:1.8.0_151]
at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
[rt.jar:1.8.0_151]
at sun.nio.ch.IOUtil.write(IOUtil.java:65) [rt.jar:1.8.0_151]
at
sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishWrite(UnixAsynchronousSocketChannelImpl.java:582)
[rt.jar:1.8.0_151]
at
sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:190)
[rt.jar:1.8.0_151]
at
sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
[rt.jar:1.8.0_151]
at sun.nio.ch.EPollPort$EventHandlerTask.run(EPollPort.java:293)
[rt.jar:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_151]
Engine.log:
2017-10-23 12:16:33,046-04 DEBUG
[org.ovirt.engine.core.uutils.ssh.SSHClient]
(EE-ManagedThreadFactory-engine-Thread-1) [83a00e1] Executed: 'umask 0077;
MYTMP="$(TMPDIR="${OVIRT_TMPDIR}" mktemp -d -t ovirt-XXXXX
XXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr
\"${MYTMP}\" > /dev/null 2>&1" 0; tar --warning=no-timestamp -C "${MYTMP}"
-x && "${MYTMP}"/ovirt-host-deploy DIALOG/dialect=str:machine DIALO
G/customization=bool:True'
2017-10-23 12:16:33,056-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase] (VdsDeploy) [83a00e1]
Error during deploy dialog
2017-10-23 12:16:33,057-04 DEBUG
[org.ovirt.engine.core.uutils.ssh.SSHDialog]
(EE-ManagedThreadFactory-engine-Thread-1) [83a00e1] execute leave
2017-10-23 12:16:33,057-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(EE-ManagedThreadFactory-engine-Thread-1) [83a00e1] Error during host
lago-basic-suite-master-host-0 install
2017-10-23 12:16:33,065-04 ERROR
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(EE-ManagedThreadFactory-engine-Thread-1) [83a00e1] EVENT_ID:
VDS_INSTALL_IN_PROGRESS_ERROR(511), An error has occurred during
installation of Host lago-basic-suite-master-host-0: Unexpected connection
termination.
2017-10-23 12:16:33,065-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.VdsDeployBase]
(EE-ManagedThreadFactory-engine-Thread-1) [83a00e1] Error during host
lago-basic-suite-master-host-0 install, preferring first exception:
Unexpected connection termination
2017-10-23 12:16:33,065-04 ERROR
[org.ovirt.engine.core.bll.hostdeploy.InstallVdsInternalCommand]
(EE-ManagedThreadFactory-engine-Thread-1) [83a00e1] Host installation
failed for host 'c4138375-aa53-4c36-8907-306803ae4282',
'lago-basic-suite-master-host-0': Unexpected connection termination
7 years, 1 month
