- Infra - oVirt List Archives

[ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.hotplug_nic ]
by Daniel Belenky 12 Mar '17

12 Mar '17

*Test failed: *basic_sanity.hotplug_nic *Link to failed job: *test-repo_ovirt_experimental_4.1/917/ <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…> *Link to all logs: *logs from Jenkins <http://jenkins.ovirt.org/view/experimental%20jobs/job/test-repo_ovirt_exper…> *May be related to: *https://bugzilla.redhat.com/show_bug.cgi?id=1417595 *Error snippet from log: *(from supervdsm.log): ifup/VLAN100_Network::DEBUG::2017-03-08 22:24:22,832::commands::93::root::(execCmd) FAILED: <err> = 'Running scope as unit ff994cde-b66d-4d54-9e36-fc253682608f.scope.\n/etc/sysconfig/network-scripts/ifup-eth: line 297: 16985 Terminated /sbin/dhclient ${DHCLIENTARGS} ${DEVICE}\nCannot find device "VLAN100_Network"\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\nDevice "VLAN100_Network" does not exist.\n'; <rc> = 1 ifup/VLAN100_Network::ERROR::2017-03-08 22:24:22,832::utils::371::root::(wrapper) Unhandled exception Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 368, in wrapper return f(*a, **kw) File "/usr/lib/python2.7/site-packages/vdsm/concurrent.py", line 180, in run return func(*args, **kwargs) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 924, in _exec_ifup _exec_ifup_by_name(iface.name, cgroup) File "/usr/lib/python2.7/site-packages/vdsm/network/configurators/ifcfg.py", line 910, in _exec_ifup_by_name raise ConfigNetworkError(ERR_FAILED_IFUP, out[-1] if out else '') ConfigNetworkError: (29, 'Determining IPv6 information for VLAN100_Network... failed.') -- *Daniel Belenky* *RHV DevOps* *Red Hat Israel*

2 2

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by Barak Korren (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1250: ------------------------------------- We probably shouldn't just add everyone to the oVirt org. instead we should probably instruct the maintainers to run 'ci test please' to confirm the PR. (Or add to the org of they choose to) > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1250) Github PR builder plugin generates too many messages
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1250?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1250: -------------------------------------------------- Until we fix this, can we replace the message with something like: You're not part of the oVirt organization, please request one of the oVirt infra members to add you to be able to send PR requests. > Github PR builder plugin generates too many messages > ---------------------------------------------------- > > Key: OVIRT-1250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1250 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Pavel Zhukov > Assignee: infra > > Seems like GH PR builder plugin posts one message like: > Can one of the admins verify this patch? > Per job which should be triggered. For example if we have el7/fc25/fc24/master jobs to be triggered by Pull Request it means message will appear 4 times in the GH UI which is useless and annoying. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1252: --------------------------------------------- Labels: standard-ci (was: ) > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA) 12 Mar '17

12 Mar '17

Barak Korren created OVIRT-1252: ----------------------------------- Summary: post-merge build-artifacts jobs can run out of order Key: OVIRT-1252 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order
by Barak Korren (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1252: -------------------------------- Epic Link: OVIRT-400 > post-merge build-artifacts jobs can run out of order > ---------------------------------------------------- > > Key: OVIRT-1252 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel. > The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order. > To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1251) create status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1251?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1251: -------------------------------------------------- https://cachethq.io/ looks like a cool OSS project we can use for it. > create status.ovirt.org > ----------------------- > > Key: OVIRT-1251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > Similar to other projects: > https://status.newrelic.com/ > https://status.centos.org/ > It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1251) create status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1251?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1251: --------------------------------------------- Epic Link: OVIRT-840 > create status.ovirt.org > ----------------------- > > Key: OVIRT-1251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > Similar to other projects: > https://status.newrelic.com/ > https://status.centos.org/ > It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OVIRT-1251) create status.ovirt.org
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

eyal edri [Administrator] created OVIRT-1251: ------------------------------------------------ Summary: create status.ovirt.org Key: OVIRT-1251 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1251 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra Similar to other projects: https://status.newrelic.com/ https://status.centos.org/ It should run probably using local storage so it won't get affected by a storage outage. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 12 Mar '17

12 Mar '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] updated OST-39: ----------------------------------------- Status: In Review (was: To Do) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.815.2#100035)

1 0