[JIRA] (OVIRT-1003) Ensure PHX proxy does not cache resources.ovirt.org

2017-03-09 Thread Evgheni Dereveanchin (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin reassigned OVIRT-1003:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> Ensure PHX proxy does not cache resources.ovirt.org 
> 
>
> Key: OVIRT-1003
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1003
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: Evgheni Dereveanchin
>
> Out proxy is currently caching packages from resources.ovirt.org when jobs 
> ask for then, since resources.ovirt.org is now in PHX, this is redundant and 
> places unnecessary load on the proxy.
> We need to configure the proxy to issue an HTTP permanent redirect (301) to 
> all requests for file from resource.ovirt.org.



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1243) HTTPS connection to ovirt.org causes HSTS pinning for subdomains

2017-03-09 Thread Evgheni Dereveanchin (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Evgheni Dereveanchin reassigned OVIRT-1243:
---

Assignee: Evgheni Dereveanchin  (was: infra)

> HTTPS connection to ovirt.org causes HSTS pinning for subdomains
> 
>
> Key: OVIRT-1243
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1243
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Evgheni Dereveanchin
>Assignee: Evgheni Dereveanchin
>
> After accessing https://ovirt.org modern browser will refuse to display 
> plaintext sites from all subdomains.
> Example:
> 1) go to https://ovirt.org in Chrome
> 2) try to access http://jenkins.ovirt.org
> Result: browser tries to connect to https so the connection fails
> (to revert this - go to chrome://net-internals/#hsts and delete ovirt.org 
> domain)
> This happens since the following header is sent by https://ovirt.org:
> Strict-Transport-Security:max-age=31536000; includeSubDomains; preload



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1243) HTTPS connection to ovirt.org causes HSTS pinning for subdomains

2017-03-09 Thread Evgheni Dereveanchin (oVirt JIRA) 
Evgheni Dereveanchin created OVIRT-1243:
---

 Summary: HTTPS connection to ovirt.org causes HSTS pinning for 
subdomains
 Key: OVIRT-1243
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1243
 Project: oVirt - virtualization made easy
  Issue Type: Improvement
Reporter: Evgheni Dereveanchin
Assignee: infra


After accessing https://ovirt.org modern browser will refuse to display 
plaintext sites from all subdomains.

Example:
1) go to https://ovirt.org in Chrome
2) try to access http://jenkins.ovirt.org

Result: browser tries to connect to https so the connection fails

(to revert this - go to chrome://net-internals/#hsts and delete ovirt.org 
domain)

This happens since the following header is sent by https://ovirt.org:
Strict-Transport-Security:max-age=31536000; includeSubDomains; preload



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.assign_hosts_network_label ]

2017-03-09 Thread Martin Perina 
On Thu, Mar 9, 2017 at 2:25 PM, Oved Ourfali  wrote:

> I do see the unrecognized message received beforehand.
> I do expect [1] to fix it.
> Martin - shall we merge [1] if it passed OST when you tested it?
> Do we want a few additional runs?
>

​I've run OST on the patch several times yesterday and today and all runs
were successful, so I think we are good with the patch.
​


>
> [1] https://gerrit.ovirt.org/#/c/73745/
>
> On Thu, Mar 9, 2017 at 3:10 PM, Oved Ourfali  wrote:
>
>> Both hosts are Up.
>> When you try to add the label the host is still not up, but a few seconds
>> later it moves to Up.
>>
>>
>> On Thu, Mar 9, 2017 at 2:55 PM, Dan Kenigsberg  wrote:
>>
>>> On Thu, Mar 9, 2017 at 1:50 PM, Daniel Belenky 
>>> wrote:
>>> > Test failed: basic_sanity.assign_hosts_network_label
>>> >
>>> > Link to failed job: test-repo_ovirt_experimental_master/5754
>>> >
>>> > Link to all logs: logs from Jenkins
>>> >
>>> > Error snippet from log:
>>> >
>>> > lago.utils: ERROR: Error while running thread
>>> > Traceback (most recent call last):
>>> >   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
>>> > _ret_via_queue
>>> > queue.put({'return': func()})
>>> >   File
>>> > "/home/jenkins/workspace/test-repo_ovirt_experimental_master
>>> /ovirt-system-tests/basic-suite-master/test-scenarios/005_
>>> network_by_label.py",
>>> > line 56, in _assign_host_network_label
>>> > host_nic=nic
>>> >   File
>>> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
>>> line
>>> > 16231, in add
>>> > headers={"Correlation-Id":correlation_id, "Expect":expect}
>>> >   File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/pr
>>> oxy.py",
>>> > line 79, in add
>>> > return self.request('POST', url, body, headers, cls=cls)
>>> >   File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/pr
>>> oxy.py",
>>> > line 122, in request
>>> > persistent_auth=self.__persistent_auth
>>> >   File
>>> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/co
>>> nnectionspool.py",
>>> > line 79, in do_request
>>> > persistent_auth)
>>> >   File
>>> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/co
>>> nnectionspool.py",
>>> > line 162, in __do_request
>>> > raise errors.RequestError(response_code, response_reason,
>>> response_body)
>>> > RequestError:
>>> > status: 409
>>> > reason: Conflict
>>> > detail: Cannot add Label. Operation can be performed only when Host
>>> status
>>> > is  Maintenance, Up, NonOperational.
>>>
>>> Leon, could you look into this job's engine.log? I suspect that the
>>> added log entry there would state that the host has fallen off to
>>> non-responding. If so, I suspect a bug in the transport layer.
>>> ___
>>> Infra mailing list
>>> Infra@ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/infra
>>>
>>>
>>>
>>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1162) Make sure cron failure email from resources.ovirt.org reach the infra list

2017-03-09 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-1162:
-
Priority: Medium  (was: High)

> Make sure cron failure email from resources.ovirt.org reach the infra list
> --
>
> Key: OVIRT-1162
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1162
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>
> There are quite a few things that run there with cron and we need to know 
> when they fail.



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Ducks blurred

2017-03-09 Thread Duck 
Quack,

So I'm soon taking my flight back Pond. I'll be back home late on
Friday, and Monday is my company health check. So I'll be at full speed
again on Tuesday.

See you around.
\_o<



signature.asc
Description: OpenPGP digital signature
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.assign_hosts_network_label ]

2017-03-09 Thread Yaniv Kaul 
On Thu, Mar 9, 2017, 3:11 PM Oved Ourfali  wrote:

> Both hosts are Up.
> When you try to add the label the host is still not up, but a few seconds
> later it moves to Up.
>

We are not sure why they were not up though.
Y.


>
> On Thu, Mar 9, 2017 at 2:55 PM, Dan Kenigsberg  wrote:
>
> On Thu, Mar 9, 2017 at 1:50 PM, Daniel Belenky 
> wrote:
> > Test failed: basic_sanity.assign_hosts_network_label
> >
> > Link to failed job: test-repo_ovirt_experimental_master/5754
> >
> > Link to all logs: logs from Jenkins
> >
> > Error snippet from log:
> >
> > lago.utils: ERROR: Error while running thread
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
> > _ret_via_queue
> > queue.put({'return': func()})
> >   File
> >
> "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/005_network_by_label.py",
> > line 56, in _assign_host_network_label
> > host_nic=nic
> >   File
> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
> line
> > 16231, 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: 409
> > reason: Conflict
> > detail: Cannot add Label. Operation can be performed only when Host
> status
> > is  Maintenance, Up, NonOperational.
>
> Leon, could you look into this job's engine.log? I suspect that the
> added log entry there would state that the host has fallen off to
> non-responding. If so, I suspect a bug in the transport layer.
> ___
>
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>
> ___
> Devel mailing list
> de...@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1003) Ensure PHX proxy does not cache resources.ovirt.org

2017-03-09 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-1003:
-
Priority: Medium  (was: High)

We didn't see errors from this front for a while, and IIRC we also stopped 
using the proxy in OST, so its only relevant for non OST jobs.

reducing priority for now.

> Ensure PHX proxy does not cache resources.ovirt.org 
> 
>
> Key: OVIRT-1003
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1003
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>  Components: Repositories Mgmt
>Reporter: Barak Korren
>Assignee: infra
>
> Out proxy is currently caching packages from resources.ovirt.org when jobs 
> ask for then, since resources.ovirt.org is now in PHX, this is redundant and 
> places unnecessary load on the proxy.
> We need to configure the proxy to issue an HTTP permanent redirect (301) to 
> all requests for file from resource.ovirt.org.



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1195) Unexplained failure in CI job

2017-03-09 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-1195:
-
Resolution: Fixed
Status: Done  (was: To Do)

changed repo to tested, shouldn't happen again.
Please reopen if you see it again.

> Unexplained failure in CI job
> -
>
> Key: OVIRT-1195
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1195
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>  Components: Jenkins
>Reporter: Yaniv Kaul
>Assignee: infra
>Priority: High
>
> See 
> http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_64/197/console
>  
> I'm not sure what the failure is. All I see is:
> 18:50:23 Start: yum install
> 18:50:37 ERROR: Command failed. See logs for output.



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1073) Gradually remove jobs from master publisher

2017-03-09 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] updated OVIRT-1073:
-
Summary: Gradually remove jobs from master publisher  (was: Drop nightly 
publishers in oVirt CI)

> Gradually remove jobs from master publisher
> ---
>
> Key: OVIRT-1073
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1073
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>Reporter: eyal edri [Administrator]
>Assignee: infra
>
> We saw how destructive using the current publishers can be during 4.1 cycle, 
> Problems we encountered:
> 1. It hides missing RPMs from experimental flows 
> 2. It hides projects that needs to branch or using previous version released
> 3. It creates confusion of which RPMs are really tested in OST and give 
> different results than experimental instead of having a single source of RPMs 
> for oVirt.
> We should aim to drop it for 4.2 and use only experimental deployment.
> However, since we have errors on deploy to experimental flow, we can't 
> progress with this until they will be solved.



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1160) Sort search results in Jenkins Manual Trigger

2017-03-09 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] reassigned OVIRT-1160:


Assignee: Evgheni Dereveanchin  (was: infra)

This will be possible only after Gerrit will support the open feature, so we'll 
monitor this and see which version it will be included.

> Sort search results in Jenkins Manual Trigger
> -
>
> Key: OVIRT-1160
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1160
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: Allon Mureinik
>Assignee: Evgheni Dereveanchin
>
> When searching for a change in Jenkins Manual Retrigger, the results return 
> in a seemingly random order.
> Sorting them by Change Id (or frankly, any logical sorting) would be great, 
> and make this tool easier to use.
> [not sure if this can be done with this plugin, but thought I'd ask just in 
> case]
> See example of unsorted changes: http://imgur.com/a/JdYQ6



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1047) Build and check KubeVirt Demo image

2017-03-09 Thread eyal edri [Administrator] (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

eyal edri [Administrator] reassigned OVIRT-1047:


Assignee: Daniel Belenky  (was: infra)

> Build and check KubeVirt Demo image
> ---
>
> Key: OVIRT-1047
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1047
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Jenkins
>Reporter: Fabian Deutsch
>Assignee: Daniel Belenky
>Priority: High
>  Labels: kubevirt
>
> Hey,
> a job is needed which will build the following image:
> https://github.com/kubevirt/demo
> $ make clean build check
> should do the job. virt-builder and guestfish are used.



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.assign_hosts_network_label ]

2017-03-09 Thread Oved Ourfali 
I do see the unrecognized message received beforehand.
I do expect [1] to fix it.
Martin - shall we merge [1] if it passed OST when you tested it?
Do we want a few additional runs?

[1] https://gerrit.ovirt.org/#/c/73745/

On Thu, Mar 9, 2017 at 3:10 PM, Oved Ourfali  wrote:

> Both hosts are Up.
> When you try to add the label the host is still not up, but a few seconds
> later it moves to Up.
>
>
> On Thu, Mar 9, 2017 at 2:55 PM, Dan Kenigsberg  wrote:
>
>> On Thu, Mar 9, 2017 at 1:50 PM, Daniel Belenky 
>> wrote:
>> > Test failed: basic_sanity.assign_hosts_network_label
>> >
>> > Link to failed job: test-repo_ovirt_experimental_master/5754
>> >
>> > Link to all logs: logs from Jenkins
>> >
>> > Error snippet from log:
>> >
>> > lago.utils: ERROR: Error while running thread
>> > Traceback (most recent call last):
>> >   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
>> > _ret_via_queue
>> > queue.put({'return': func()})
>> >   File
>> > "/home/jenkins/workspace/test-repo_ovirt_experimental_master
>> /ovirt-system-tests/basic-suite-master/test-scenarios/
>> 005_network_by_label.py",
>> > line 56, in _assign_host_network_label
>> > host_nic=nic
>> >   File
>> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
>> line
>> > 16231, 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/co
>> nnectionspool.py",
>> > line 79, in do_request
>> > persistent_auth)
>> >   File
>> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/co
>> nnectionspool.py",
>> > line 162, in __do_request
>> > raise errors.RequestError(response_code, response_reason,
>> response_body)
>> > RequestError:
>> > status: 409
>> > reason: Conflict
>> > detail: Cannot add Label. Operation can be performed only when Host
>> status
>> > is  Maintenance, Up, NonOperational.
>>
>> Leon, could you look into this job's engine.log? I suspect that the
>> added log entry there would state that the host has fallen off to
>> non-responding. If so, I suspect a bug in the transport layer.
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>>
>>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.assign_hosts_network_label ]

2017-03-09 Thread Oved Ourfali 
Both hosts are Up.
When you try to add the label the host is still not up, but a few seconds
later it moves to Up.


On Thu, Mar 9, 2017 at 2:55 PM, Dan Kenigsberg  wrote:

> On Thu, Mar 9, 2017 at 1:50 PM, Daniel Belenky 
> wrote:
> > Test failed: basic_sanity.assign_hosts_network_label
> >
> > Link to failed job: test-repo_ovirt_experimental_master/5754
> >
> > Link to all logs: logs from Jenkins
> >
> > Error snippet from log:
> >
> > lago.utils: ERROR: Error while running thread
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
> > _ret_via_queue
> > queue.put({'return': func()})
> >   File
> > "/home/jenkins/workspace/test-repo_ovirt_experimental_
> master/ovirt-system-tests/basic-suite-master/test-
> scenarios/005_network_by_label.py",
> > line 56, in _assign_host_network_label
> > host_nic=nic
> >   File
> > "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
> line
> > 16231, 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: 409
> > reason: Conflict
> > detail: Cannot add Label. Operation can be performed only when Host
> status
> > is  Maintenance, Up, NonOperational.
>
> Leon, could you look into this job's engine.log? I suspect that the
> added log entry there would state that the host has fallen off to
> non-responding. If so, I suspect a bug in the transport layer.
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.hotplug_nic ]

2017-03-09 Thread Dan Kenigsberg 
On Thu, Mar 9, 2017 at 10:00 AM, Daniel Belenky  wrote:
> Test failed: basic_sanity.hotplug_nic
>
> Link to failed job: test-repo_ovirt_experimental_4.1/917/
>
> Link to all logs: logs from Jenkins
>
> 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:  = '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';  = 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.')

Yes, this seems to be a reproduction of Vdsm bug 1417595 - hotplug_nic
test fails in OST

Eddy, can you tell how could it be that the VLAN100_NETWORK bridge
does not exist when ifup is called?
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.assign_hosts_network_label ]

2017-03-09 Thread Dan Kenigsberg 
On Thu, Mar 9, 2017 at 1:50 PM, Daniel Belenky  wrote:
> Test failed: basic_sanity.assign_hosts_network_label
>
> Link to failed job: test-repo_ovirt_experimental_master/5754
>
> Link to all logs: logs from Jenkins
>
> Error snippet from log:
>
> lago.utils: ERROR: Error while running thread
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
> _ret_via_queue
> queue.put({'return': func()})
>   File
> "/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/005_network_by_label.py",
> line 56, in _assign_host_network_label
> host_nic=nic
>   File
> "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line
> 16231, 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: 409
> reason: Conflict
> detail: Cannot add Label. Operation can be performed only when Host status
> is  Maintenance, Up, NonOperational.

Leon, could you look into this job's engine.log? I suspect that the
added log entry there would state that the host has fallen off to
non-responding. If so, I suspect a bug in the transport layer.
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.assign_hosts_network_label ]

2017-03-09 Thread Daniel Belenky 
*Test failed: *basic_sanity.assign_hosts_network_label

*Link to failed job: *test-repo_ovirt_experimental_master/5754


*Link to all logs: *logs from Jenkins


*Error snippet from log:*

lago.utils: ERROR: Error while running thread
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/lago/utils.py", line 57, in
_ret_via_queue
queue.put({'return': func()})
  File 
"/home/jenkins/workspace/test-repo_ovirt_experimental_master/ovirt-system-tests/basic-suite-master/test-scenarios/005_network_by_label.py",
line 56, in _assign_host_network_label
host_nic=nic
  File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
line 16231, 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: 409
reason: Conflict
detail: Cannot add Label. Operation can be performed only when Host
status is  Maintenance, Up, NonOperational.


-- 

*Daniel Belenky*

*RHV DevOps*

*Red Hat Israel*
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5755 - SUCCESS!

2017-03-09 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5755/,
Build Number: 5755,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1242) Re: ovirt_4.1_he-system-tests Failed!

2017-03-09 Thread Daniel Belenky (oVirt JIRA) 

 [ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Belenky reassigned OVIRT-1242:
-

Assignee: Daniel Belenky  (was: infra)

> Re: ovirt_4.1_he-system-tests Failed!
> -
>
> Key: OVIRT-1242
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1242
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: Daniel Belenky
>
> http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/artifact/exported-artifacts/failure_msg.txt
> "Failed to prepare environment on step env_deploy, please contact the CI
> team."
> CI team, can you please have a look?
> On Thu, Mar 9, 2017 at 3:37 AM,  wrote:
> > Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/
> > Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/
> > Build Number: 34
> > Build Status:  Still Failing
> > Triggered By: Started by timer
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #29
> > [Ondra Machacek] Add Ansible modules tests
> >
> > [Sandro Bonazzola] pywin32-py2.7: drop fc24 on master
> >
> > [Sandro Bonazzola] nsis-simple-service-plugin: drop fc24 on master
> >
> > [Eyal Edri] adding job for master ansible suite
> >
> >
> > Changes for Build #30
> > [Ondra Machacek] Add Ansible modules tests
> >
> >
> > Changes for Build #31
> > [Yaniv Kaul] Remove cockpit-ovirt installation test
> >
> >
> > Changes for Build #32
> > [Yaniv Kaul] Remove cockpit-ovirt installation test
> >
> > [Yedidyah Bar David] ovirt-wgt: Built master only on fc25
> >
> > [Greg Sheremeta] ovirt-engine-phantomjs: configure jobs
> >
> >
> > Changes for Build #33
> > [Yaniv Kaul] Slim down the amount of packages we sync
> >
> >
> > Changes for Build #34
> > [Yaniv Kaul] Slim down the amount of packages we sync
> >
> > [Eyal Edri] remove emails from repo closure jobs
> >
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1242) Re: ovirt_4.1_he-system-tests Failed!

2017-03-09 Thread Daniel Belenky (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=28411#comment-28411
 ] 

Daniel Belenky edited comment on OVIRT-1242 at 3/9/17 11:17 AM:


Hey Sando :)
I've looked in the console output, and it seems that the job is failing because 
hosted engine deploy fail.

{code:java}
02:36:29 [ INFO  ] Checking OVF archive content (could take a few minutes 
depending on archive size)
02:36:54 [ INFO  ] Checking OVF XML content (could take a few minutes depending 
on archive size)
02:37:20 [ INFO  ] Detecting host timezone.
02:37:20 [WARNING] Minimum requirements to fit the disk from the appliance OVF 
not met (required 50 GiB)
02:37:20 [ ERROR ] Failed to execute stage 'Environment customization': Minimum 
requirements to fit the disk from the appliance OVF not met (required 50 GiB)
02:37:20 [ INFO  ] Stage: Clean up
02:37:20 [ INFO  ] Generating answer file 
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20170308213720.conf'
02:37:20 [ INFO  ] Stage: Pre-termination
02:37:21 [ INFO  ] Stage: Termination
02:37:21 [ ERROR ] Hosted Engine deployment failed
02:37:21   Log file is located at 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170308213605-nzmi5d.log
02:37:21 hosted-engine deploy on lago-he-basic-suite-4-1-host0 failed with 
status 1.
{code}



was (Author: dbele...@redhat.com):
Hey Sando :)
I've looked in the console output, and it seems that the job is failing because 
hosted engine deploy fail.

{code:java}
02:36:29 [ INFO  ] Checking OVF archive content (could take a few minutes 
depending on archive size)
02:36:54 [ INFO  ] Checking OVF XML content (could take a few minutes depending 
on archive size)
02:37:20 [ INFO  ] Detecting host timezone.
02:37:20 [WARNING] Minimum requirements to fit the disk from the appliance OVF 
not met (required 50 GiB)
02:37:20 [ ERROR ] Failed to execute stage 'Environment customization': Minimum 
requirements to fit the disk from the appliance OVF not met (required 50 GiB)
02:37:20 [ INFO  ] Stage: Clean up
02:37:20 [ INFO  ] Generating answer file 
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20170308213720.conf'
02:37:20 [ INFO  ] Stage: Pre-termination
02:37:21 [ INFO  ] Stage: Termination
02:37:21 {color:red}[ ERROR ] Hosted Engine deployment failed{color}
02:37:21   Log file is located at 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170308213605-nzmi5d.log
02:37:21 hosted-engine deploy on lago-he-basic-suite-4-1-host0 failed with 
status 1.
{code}


> Re: ovirt_4.1_he-system-tests Failed!
> -
>
> Key: OVIRT-1242
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1242
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/artifact/exported-artifacts/failure_msg.txt
> "Failed to prepare environment on step env_deploy, please contact the CI
> team."
> CI team, can you please have a look?
> On Thu, Mar 9, 2017 at 3:37 AM,  wrote:
> > Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/
> > Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/
> > Build Number: 34
> > Build Status:  Still Failing
> > Triggered By: Started by timer
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #29
> > [Ondra Machacek] Add Ansible modules tests
> >
> > [Sandro Bonazzola] pywin32-py2.7: drop fc24 on master
> >
> > [Sandro Bonazzola] nsis-simple-service-plugin: drop fc24 on master
> >
> > [Eyal Edri] adding job for master ansible suite
> >
> >
> > Changes for Build #30
> > [Ondra Machacek] Add Ansible modules tests
> >
> >
> > Changes for Build #31
> > [Yaniv Kaul] Remove cockpit-ovirt installation test
> >
> >
> > Changes for Build #32
> > [Yaniv Kaul] Remove cockpit-ovirt installation test
> >
> > [Yedidyah Bar David] ovirt-wgt: Built master only on fc25
> >
> > [Greg Sheremeta] ovirt-engine-phantomjs: configure jobs
> >
> >
> > Changes for Build #33
> > [Yaniv Kaul] Slim down the amount of packages we sync
> >
> >
> > Changes for Build #34
> > [Yaniv Kaul] Slim down the amount of packages we sync
> >
> > [Eyal Edri] remove emails from repo closure jobs
> >
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1242) Re: ovirt_4.1_he-system-tests Failed!

2017-03-09 Thread Daniel Belenky (oVirt JIRA) 

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=28411#comment-28411
 ] 

Daniel Belenky edited comment on OVIRT-1242 at 3/9/17 11:17 AM:


Hey Sando :)
I've looked in the console output, and it seems that the job is failing because 
hosted engine deploy fail.

{code:java}
02:36:29 [ INFO  ] Checking OVF archive content (could take a few minutes 
depending on archive size)
02:36:54 [ INFO  ] Checking OVF XML content (could take a few minutes depending 
on archive size)
02:37:20 [ INFO  ] Detecting host timezone.
02:37:20 [WARNING] Minimum requirements to fit the disk from the appliance OVF 
not met (required 50 GiB)
02:37:20 [ ERROR ] Failed to execute stage 'Environment customization': Minimum 
requirements to fit the disk from the appliance OVF not met (required 50 GiB)
02:37:20 [ INFO  ] Stage: Clean up
02:37:20 [ INFO  ] Generating answer file 
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20170308213720.conf'
02:37:20 [ INFO  ] Stage: Pre-termination
02:37:21 [ INFO  ] Stage: Termination
02:37:21 {color:red}[ ERROR ] Hosted Engine deployment failed{color}
02:37:21   Log file is located at 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170308213605-nzmi5d.log
02:37:21 hosted-engine deploy on lago-he-basic-suite-4-1-host0 failed with 
status 1.
{code}



was (Author: dbele...@redhat.com):
Hey Sando :)
I've looked in the console output, and it seems that the job is failing because 
hosted engine deploy fail.

{code:java}
02:36:29 [ INFO  ] Checking OVF archive content (could take a few minutes 
depending on archive size)
02:36:54 [ INFO  ] Checking OVF XML content (could take a few minutes depending 
on archive size)
02:37:20 [ INFO  ] Detecting host timezone.
02:37:20 [WARNING] Minimum requirements to fit the disk from the appliance OVF 
not met (required 50 GiB)
02:37:20 [ ERROR ] Failed to execute stage 'Environment customization': Minimum 
requirements to fit the disk from the appliance OVF not met (required 50 GiB)
02:37:20 [ INFO  ] Stage: Clean up
02:37:20 [ INFO  ] Generating answer file 
'/var/lib/ovirt-hosted-engine-setup/answers/answers-20170308213720.conf'
02:37:20 [ INFO  ] Stage: Pre-termination
02:37:21 [ INFO  ] Stage: Termination
02:37:21 [ ERROR ] Hosted Engine deployment failed
02:37:21   Log file is located at 
/var/log/ovirt-hosted-engine-setup/ovirt-hosted-engine-setup-20170308213605-nzmi5d.log
02:37:21 hosted-engine deploy on lago-he-basic-suite-4-1-host0 failed with 
status 1.
{code}


> Re: ovirt_4.1_he-system-tests Failed!
> -
>
> Key: OVIRT-1242
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1242
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/artifact/exported-artifacts/failure_msg.txt
> "Failed to prepare environment on step env_deploy, please contact the CI
> team."
> CI team, can you please have a look?
> On Thu, Mar 9, 2017 at 3:37 AM,  wrote:
> > Project: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/
> > Build: http://jenkins.ovirt.org/job/ovirt_4.1_he-system-tests/34/
> > Build Number: 34
> > Build Status:  Still Failing
> > Triggered By: Started by timer
> >
> > -
> > Changes Since Last Success:
> > -
> > Changes for Build #29
> > [Ondra Machacek] Add Ansible modules tests
> >
> > [Sandro Bonazzola] pywin32-py2.7: drop fc24 on master
> >
> > [Sandro Bonazzola] nsis-simple-service-plugin: drop fc24 on master
> >
> > [Eyal Edri] adding job for master ansible suite
> >
> >
> > Changes for Build #30
> > [Ondra Machacek] Add Ansible modules tests
> >
> >
> > Changes for Build #31
> > [Yaniv Kaul] Remove cockpit-ovirt installation test
> >
> >
> > Changes for Build #32
> > [Yaniv Kaul] Remove cockpit-ovirt installation test
> >
> > [Yedidyah Bar David] ovirt-wgt: Built master only on fc25
> >
> > [Greg Sheremeta] ovirt-engine-phantomjs: configure jobs
> >
> >
> > Changes for Build #33
> > [Yaniv Kaul] Slim down the amount of packages we sync
> >
> >
> > Changes for Build #34
> > [Yaniv Kaul] Slim down the amount of packages we sync
> >
> > [Eyal Edri] remove emails from repo closure jobs
> >
> >
> >
> >
> > -
> > Failed Tests:
> > -
> > No tests ran.
> >
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



--
This message was sent by Atlassian JIRA
(v1000.815.1#100035)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #918 - SUCCESS!

2017-03-09 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/918/,
Build Number: 918,
Build Status: SUCCESS___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5754 - FAILURE!

2017-03-09 Thread jenkins 
Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5754/,
Build Number: 5754,
Build Status: FAILURE___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[ OST Failure Report ] [ oVirt 4.1 ] [ 09/02/17 ] [ basic_sanity.hotplug_nic ]

2017-03-09 Thread Daniel Belenky 
*Test failed: *basic_sanity.hotplug_nic

*Link to failed job: *test-repo_ovirt_experimental_4.1/917/


*Link to all logs: *logs from Jenkins


*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:  = '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';  = 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*
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra