[OST Failure Report] [oVirt master] [09.02.2017] [test-repo_ovirt_experimental_master]
by Shlomo Ben David
Hi,
*Test failed:* [test-repo_ovirt_experimental_master]
*Link to suspected patches:* n/a
*Link to Job:*
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217
*Link to all logs:*
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5217/art...
*Error snippet from the log: *
<error>
ifup/VLAN100_Network::ERROR::2017-02-09
06:21:15,236::concurrent::189::root::(run) FINISH thread
<Thread(ifup/VLAN100_Network, started daemon 140189099861760)> failed
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 185, in run
ret = func(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py",
line 949, in _exec_ifup
_exec_ifup_by_name(iface.name, cgroup)
File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py",
line 935, in _exec_ifup_by_name
raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '')
ConfigNetworkError: (29, 'Determining IPv6 information for
VLAN100_Network... failed.')
</error>
Best Regards,
Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
RHCSA | RHCVA | RHCE
IRC: shlomibendavid (on #rhev-integ, #rhev-dev, #rhev-ci)
OPEN SOURCE - 1 4 011 && 011 4 1
7 years, 1 month
Ruby SDK NIC search
by Marc Young
Is there something malformed in this? Based on previous usages of
`.list(search: "...")` this does not seem like correct behavior
> env[:connection].system_service.vnic_profiles_service.list(search:
"name=#{iface_options[:network_name]}").map(&:name)
=> ["ovirtmgmt", "ovirtmgmt"]
> env[:connection].system_service.vnic_profiles_service.list(search:
"name=foo").map(&:name)
=> ["ovirtmgmt", "ovirtmgmt"]
> env[:connection].system_service.vnic_profiles_service.list.map(&:name)
=> ["ovirtmgmt", "ovirtmgmt"]
No matter what I provide it always returns all
Search works for other services:
> env[:connection].system_service.vms_service.list(search:
'name=myvm').map(&:name)
=> []
> env[:connection].system_service.vms_service.list(search:
'name=testing').map(&:name)
=> ["testing"]
> env[:connection].system_service.vms_service.list(search:
'name=e').map(&:name)
=> []
7 years, 1 month
oVirt Cloud-init
by Marc Young
Are there limitations to cloud-init and oVirt? I wouldn't think so,
but i"m having a weird issue.
If i use the cloud-init yaml from the ovirt4 ruby sdk examples (ignore
formatting, gmail is messing with it):
write_files:
- content: |
Hello, world!
path: /tmp/greeting.txt
permissions: '0644'
it works, that file exists, and it shows in the /var/lib/cloud where i'd expect
$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
output:
all: '>> /var/log/cloud-init-output.log'
disable_root: 0
runcmd:
- 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo
''datasource_list:
["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg'
ssh_pwauth: true
chpasswd:
expire: false
user: root
write_files:
- content: |
Hello, world!
path: /tmp/greeting.txt
permissions: '0644'
If i use this:
manage-resolv-conf: true
resolv_conf:
nameservers: ['192.168.2.113']
searchdomains:
- blindrage.local
- bar.example.com
resolv_conf does not get modified. It looks as expected in /var/lib/cloud:
$ sudo cat /var/lib/cloud/instance/user-data.txt
#cloud-config
output:
all: '>> /var/log/cloud-init-output.log'
disable_root: 0
runcmd:
- 'sed -i ''/^datasource_list: /d'' /etc/cloud/cloud.cfg; echo
''datasource_list:
["NoCloud", "ConfigDrive"]'' >> /etc/cloud/cloud.cfg'
ssh_pwauth: true
chpasswd:
expire: false
user: root
manage-resolv-conf: true
resolv_conf:
nameservers: ['192.168.2.113']
searchdomains:
- foo.local
- bar.example.com
I also don't see anything in /var/log/cloud-init.log or
/var/log/cloud-init-output.log on either run even though the
write_files yaml worked.
7 years, 1 month
Cant get yum update "ovirt-*-setup*" packages to upgrade from 4.0 to 4.1
by Lynn Dixon
I am following the three simple steps in the release notes here:
https://www.ovirt.org/release/4.1.0/
I have added the repo fine, and did a yum clean all just to be cautions.
However, when I try to run the yum update "ovirt-*-setup*" command it just
returns no updates found. Likewise, if I even try to do a yum update
ovirt-engine-setup it returns no updates found.
I am currently running oVirt 4.0.6.3-1.el7.centos on a CentOS machine. I
feel like I am missing something really simple here, but I can not get it
to update any packages beyond the 4.0 repos. I have even tried disabling
the 4.0 repos, but no luck.
Any suggestions?
*Lynn Dixon* | Red Hat Certified Architect #100-006-188
*Sr. Cloud Consultant* | Cloud Management Practice
Google Voice: 423-618-1414
Cell/Text: 423-774-3188
Click here to view my Certification Portfolio <http://red.ht/1XMX2Mi>
7 years, 1 month
oVirt packages for JavaScript development have been updated
by Vojtech Szocs
Hello devs,
following packages, intended as build-time dependencies of oVirt
JavaScript projects, have been updated:
* ovirt-engine-nodejs
* ovirt-engine-nodejs-modules
* ovirt-engine-yarn
If you use those packages, please read on to learn how to adapt your
project. oVirt Dashboard (master) is already adapted and you can use
it as your reference.
==
1, move your project from npm to Yarn:
- using nodejs-modules implies that your project moves from npm to
Yarn, please do this as your first step
- make sure to add yarn.lock file to source control: rm -rf
node_modules && yarn install # generates yarn.lock
- your automation/*.packages should contain something like this:
ovirt-engine-nodejs-6.9.4
ovirt-engine-nodejs-modules-1.0.3
ovirt-engine-yarn-0.19.1
- since oVirt CI uses yum cache, always specify exact version of
nodejs-modules in your automation/*.packages
- in your RPM build script, make sure to set up Node.js env.: source
/usr/share/ovirt-engine-nodejs-modules/setup-env.sh
==
2a, dependency handling - 1st time:
- clone nodejs-modules repo & update the projects.list file - add
URL(s) to your project's files (package.json + yarn.lock)
- bump .z in RPM Version and reset the RPM Release number, submit
patch to Gerrit
- in your project, update automation/*.packages to use the right
nodejs-modules version
2b, dependency handling - whenever your dependencies change:
- clone nodejs-modules repo & bump RPM Release number, submit patch to Gerrit
- in your project, update automation/*.packages to use the right
nodejs-modules version
==
Q: how does the new nodejs-modules work?
A: instead of maintaining one big package.json file to specify all
dependencies of all projects (effectively forcing all projects to use
single dependency tree), it contains the projects.list file with
URL(s) to specific project files.
When building nodejs-modules RPM, it goes through the list of URL(s),
downloading project's files (package.json + yarn.lock), then
downloading required dependencies (using Yarn) and collecting their
.tar.gz sources. The nodejs-modules RPM therefore contains a flat list
of all .tar.gz sources of all dependencies of all projects.
When you source the setup-env.sh script, it does, among other things,
tell Yarn to use
/usr/share/ovirt-engine-nodejs-modules/yarn-offline-cache containing
all .tar.gz sources. Then, it runs Yarn in offline mode to populate
your project's node_modules directory.
==
Hope this helps.
Regards,
Vojtech
7 years, 1 month
