oVirt infra daily report - unstable production jobs - 82

2016-09-19 Thread jenkins 
Good morning!

Attached is the HTML page with the jenkins status report. You can see it also 
here:
 - 
http://jenkins.ovirt.org/job/system_jenkins-report/82//artifact/exported-artifacts/upstream_report.html

Cheers,
Jenkins


upstream_report.html
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to stable : ovirt_4.0_he-system-tests #289

2016-09-19 Thread jenkins 
See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : ovirt_master_system-tests #547

2016-09-19 Thread jenkins 
See 

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: [ovirt-devel] Dropping rpm build from ovirt-engine check-merged.sh

2016-09-19 Thread Eyal Edri 
On Mon, Sep 19, 2016 at 6:49 PM, Vojtech Szocs  wrote:

>
>
> - Original Message -
> > From: "Sandro Bonazzola" 
> > To: "Eyal Edri" 
> > Cc: "Juan Hernandez" , "infra" ,
> "devel" 
> > Sent: Monday, September 19, 2016 8:41:12 AM
> > Subject: Re: [ovirt-devel] Dropping rpm build from ovirt-engine
>  check-merged.sh
> >
> >
> >
> > On Sun, Sep 18, 2016 at 4:18 PM, Eyal Edri < ee...@redhat.com > wrote:
> >
> >
> >
> > Hi,
> >
> > Following [1] I'd like to propose to remove rpm building from the
> > 'check-merged.sh' script from ovirt-engine (master for now).
> >
> > The job [2] takes on avg 15 min while actually the rpms are built
> already in
> > check-patch
> > (with gwt draft mode if needed) and runs exactly the same build rpm
> command
> > as check-patch [3].
> >
> > So there isn't real value in running exactly the same rpm build post
> merge,
> > and we already build full permutation mode in 'build-artifacts.sh'.
> >
> > Any reason to keep it?
> > We can cut down valuable time in CI if we drop it and vacant more time
> for
> > more meaningful tests.
> >
> >
> > This depends on the flow: if we make check_merge gating to the merge and
> to
> > the build we should keep the rpm build becuase at merge a rebase is done
> > automatically.
> > If there's not gating process performed by check-merge then I agree in
> > dropping rpm build.
>
> First of all, for oVirt Engine snapshot (non-release) builds, we should
> avoid doing a full GWT compilation [all browsers x all locales]. That's
> simply because the full GWT compilation is too costly for CI to run on
> a regular basis.
>

+1, It also makes us find regressions slower because it takes more than 1
hour to build + consume very valuable resource which is BM slave.


>
> Doing [Firefox + Chrome x English = 2 permutations] && [draft GWT build
> option enabled] for snapshot builds should be enough.
>
> The *only* downside of not doing a full GWT build is that problems with
> localization resources [e.g. non-English .properties files] will not be
> reported by the GWT compiler. But we have Java unit tests to cover this,
> so it should be OK. (And if not, we must improve those tests.)
>
> In general, we should do a full GWT compilation only for release builds.
> Eyal mentioned at [1] that his team is working on
>
>   'build official manual' option to standard CI
>

Already merged and working for most projects.who requested it, also part of
standard CI.


>
> so that would be a great place to document & perform the full GWT build.
>
> As for build jobs: if `check-merged` is indeed acting as gate for merge
> [fail of `check-merged` => patch not merged


its not the case today, we'll need to install Zuul for that, which is in
the plan (including system tests).


> , `build-artifacts` does not
> execute], then it actually makes sense to:
>
> - keep `check-merged` doing a (draft) GWT build + Engine RPM build
> - maybe skip GWT build in `check-patch` [right now, there's detection
>   logic => if frontend files were changed, do GWT build]
>
> Otherwise, if `check-merged` doesn't act as gate for merge, we can just
> skip GWT build / Engine RPM build for that script.
>

Yea, doesn't act as gate, it just run post merge.


>
> >
> >
> >
> >
> >
> >
> > [1] https://ovirt-jira.atlassian.net/browse/OVIRT-416
> > [2]
> > http://jenkins.ovirt.org/job/ovirt-engine_master_check-
> merged-el7-x86_64/buildTimeTrend
> > [3]
> > rpmbuild \
> > -D "_rpmdir $PWD/output" \
> > -D "_topmdir $PWD/rpmbuild" \
> > -D "release_suffix ${SUFFIX}" \
> > -D "ovirt_build_ut $BUILD_UT" \
> > -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \
> > -D "ovirt_build_draft 1" \
> > --rebuild output/*.src.rpm
> >
> >
> > --
> > Eyal Edri
> > Associate Manager
> > RHV DevOps
> > EMEA ENG Virtualization R
> > Red Hat Israel
> >
> > phone: +972-9-7692018
> > irc: eedri (on #tlv #rhev-dev #rhev-integ)
> >
> >
> >
> > --
> > Sandro Bonazzola
> > Better technology. Faster innovation. Powered by community collaboration.
> > See how it works at redhat.com
> >
> >
> > ___
> > Devel mailing list
> > de...@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/devel
>



-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Dropping rpm build from ovirt-engine check-merged.sh

2016-09-19 Thread Eyal Edri 
On Mon, Sep 19, 2016 at 9:41 AM, Sandro Bonazzola 
wrote:

>
>
> On Sun, Sep 18, 2016 at 4:18 PM, Eyal Edri  wrote:
>
>> Hi,
>>
>> Following [1] I'd like to propose to remove rpm building from the
>> 'check-merged.sh' script from ovirt-engine (master for now).
>>
>> The job [2] takes on avg 15 min while actually the rpms are built already
>> in check-patch
>> (with gwt draft mode if needed) and runs exactly the same build rpm
>> command as check-patch [3].
>>
>> So there isn't real value in running exactly the same rpm build post
>> merge, and we already build full permutation mode in 'build-artifacts.sh'.
>>
>> Any reason to keep it?
>> We can cut down valuable time in CI if we drop it and vacant more time
>> for more meaningful tests.
>>
>
>
> This depends on the flow: if we make check_merge gating to the merge and
> to the build we should keep the rpm build becuase at merge a rebase is done
> automatically.
>

What do you mean by 'gating to the merge'? I'm not sure I understand what
it means.
Isn't check-patch.sh does the gating? check-merge runs post merge so its
already too late to gate the code ...
And I think check-merge and check-patch currently runs the same rpmbuild
command, so I don't see how check-merged has any value over check-patch.


> If there's not gating process performed by check-merge then I agree in
> dropping rpm build.
>
>
>
>>
>>
>> [1] https://ovirt-jira.atlassian.net/browse/OVIRT-416
>> [2] http://jenkins.ovirt.org/job/ovirt-engine_master_check-m
>> erged-el7-x86_64/buildTimeTrend
>> [3]
>> rpmbuild \
>> -D "_rpmdir $PWD/output" \
>> -D "_topmdir $PWD/rpmbuild" \
>> -D "release_suffix ${SUFFIX}" \
>> -D "ovirt_build_ut $BUILD_UT" \
>> -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \
>> -D "ovirt_build_draft 1" \
>> --rebuild output/*.src.rpm
>>
>>
>> --
>> Eyal Edri
>> Associate Manager
>> RHV DevOps
>> EMEA ENG Virtualization R
>> Red Hat Israel
>>
>> phone: +972-9-7692018
>> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
>



-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Re: Jenkins build became unstable: ovirt_4.0_he-system-tests #288

2016-09-19 Thread Eyal Edri 
Is this the usual Sanlock issue?

Error Message

status: 400
reason: Bad Request
detail: Cannot add VM: Storage Domain cannot be accessed.
-Please check that at least one Host is operational and Data Center state is up.

Stacktrace

Traceback (most recent call last):
  File "/usr/lib64/python2.7/unittest/case.py", line 367, 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
120, in wrapped_test
return test()
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
52, in wrapper
return func(get_test_prefix(), *args, **kwargs)
  File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line
61, in wrapper
return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs)
  File 
"/home/jenkins/workspace/ovirt_4.0_he-system-tests/ovirt-system-tests/he_basic_suite_4.0/test-scenarios/004_basic_sanity.py",
line 78, in add_vm_blank
api.vms.add(vm_params)
  File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py",
line 35701, 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: Cannot add VM: Storage Domain cannot be accessed.
-Please check that at least one Host is operational and Data Center state is up.


On Mon, Sep 19, 2016 at 8:22 PM,  wrote:

> See 
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>
>


-- 
Eyal Edri
Associate Manager
RHV DevOps
EMEA ENG Virtualization R
Red Hat Israel

phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Build failed in Jenkins: ovirt_master_system-tests #546

2016-09-19 Thread jenkins 
See 

Changes:

[Yaniv Kaul] Speedup for master reposync

--
[...truncated 766 lines...]
##  took 1847 seconds
##  rc = 1
##
##! ERROR v
##! Last 20 log enties: 
logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
##!
+ true
+ env_cleanup
+ echo '#'
#
+ local res=0
+ local uuid
+ echo ' Cleaning up'
 Cleaning up
+ [[ -e 

 ]]
+ echo '--- Cleaning with lago'
--- Cleaning with lago
+ lago --workdir 

 destroy --yes --all-prefixes
+ echo '--- Cleaning with lago done'
--- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo ' Cleanup done'
 Cleanup done
+ exit 0
Took 1682 seconds
===
##!
##! ERROR ^^
##!
##
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'

#
# Required jjb vars:
#version
#
VERSION=master
SUITE_TYPE=

WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"

rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"

if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi

[ovirt_master_system-tests] $ /bin/bash -xe /tmp/hudson8435450025895863597.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=
+ OVIRT_SUITE=master
+ 
TESTS_LOGS=
+ rm -rf 

+ mkdir -p 

+ [[ -d 

 ]]
+ mv 

 

 

 

 

 

POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script  : #!/bin/bash -xe
echo "shell-scripts/mock_cleanup.sh"

shopt -s nullglob


WORKSPACE="$PWD"

# Make clear this is the cleanup, helps reading the jenkins logs
cat 
+ cat
___
###
# #
#   CLEANUP   #
# #
###
+ logs=(./*log ./*/logs)
+ [[ -n ./ovirt-system-tests/logs ]]
+ tar cvzf exported-artifacts/logs.tgz ./ovirt-system-tests/logs
./ovirt-system-tests/logs/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.basic_suite_master.sh/basic_suite_master.sh.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/stdout_stderr.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/state.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/build.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.init/root.log
./ovirt-system-tests/logs/mocker-fedora-24-x86_64.fc24.clean_rpmdb/

[JIRA] (OVIRT-733) ovirt-node-ng leftover libvirt settings

2016-09-19 Thread Evgheni Dereveanchin (oVirt JIRA) 

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

Evgheni Dereveanchin reassigned OVIRT-733:
--

Assignee: Evgheni Dereveanchin  (was: infra)

> ovirt-node-ng leftover libvirt settings
> ---
>
> Key: OVIRT-733
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-733
> Project: oVirt - virtualization made easy
>  Issue Type: Bug
>Reporter: Evgheni Dereveanchin
>Assignee: Evgheni Dereveanchin
>Priority: Low
>
> I was working on node updates and troubleshooting OVIRT-630 when I came 
> across errors like this in the logs on a freshly booted EL7 slave:
> {{
> Sep 19 15:10:07 el7-vm16 libvirtd[1239]: libvirt version: 1.2.17, package: 
> 13.el7_2.5 (CentOS BuildSystem , 2016-06-23-14:23:27, 
> worker1.bsys.centos.org)
> Sep 19 15:10:07 el7-vm16 libvirtd[1239]: cannot open path 
> '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng':
>  No such file or directory
> Sep 19 15:10:07 el7-vm16 libvirtd[1239]: Failed to autostart storage pool 
> 'ovirt-node-ng': cannot open path 
> '/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng':
>  No such file or directory
> }}
> Looks like ovirt-node-ng_master_build-artifacts-el7-x86_64 is leaving behind 
> storage pool configurations. Opening this to investigate further, even though 
> I doubt it affects anything at the moment.



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

[JIRA] (OVIRT-733) ovirt-node-ng leftover libvirt settings

2016-09-19 Thread Evgheni Dereveanchin (oVirt JIRA) 
Evgheni Dereveanchin created OVIRT-733:
--

 Summary: ovirt-node-ng leftover libvirt settings
 Key: OVIRT-733
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-733
 Project: oVirt - virtualization made easy
  Issue Type: Bug
Reporter: Evgheni Dereveanchin
Assignee: infra
Priority: Low


I was working on node updates and troubleshooting OVIRT-630 when I came across 
errors like this in the logs on a freshly booted EL7 slave:

{{
Sep 19 15:10:07 el7-vm16 libvirtd[1239]: libvirt version: 1.2.17, package: 
13.el7_2.5 (CentOS BuildSystem , 2016-06-23-14:23:27, 
worker1.bsys.centos.org)
Sep 19 15:10:07 el7-vm16 libvirtd[1239]: cannot open path 
'/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng':
 No such file or directory
Sep 19 15:10:07 el7-vm16 libvirtd[1239]: Failed to autostart storage pool 
'ovirt-node-ng': cannot open path 
'/home/jenkins/workspace/ovirt-node-ng_master_build-artifacts-el7-x86_64/ovirt-node-ng':
 No such file or directory
}}

Looks like ovirt-node-ng_master_build-artifacts-el7-x86_64 is leaving behind 
storage pool configurations. Opening this to investigate further, even though I 
doubt it affects anything at the moment.



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

Re: [ovirt-devel] Dropping rpm build from ovirt-engine check-merged.sh

2016-09-19 Thread Vojtech Szocs 


- Original Message -
> From: "Sandro Bonazzola" 
> To: "Eyal Edri" 
> Cc: "Juan Hernandez" , "infra" , 
> "devel" 
> Sent: Monday, September 19, 2016 8:41:12 AM
> Subject: Re: [ovirt-devel] Dropping rpm build from ovirt-engine   
> check-merged.sh
> 
> 
> 
> On Sun, Sep 18, 2016 at 4:18 PM, Eyal Edri < ee...@redhat.com > wrote:
> 
> 
> 
> Hi,
> 
> Following [1] I'd like to propose to remove rpm building from the
> 'check-merged.sh' script from ovirt-engine (master for now).
> 
> The job [2] takes on avg 15 min while actually the rpms are built already in
> check-patch
> (with gwt draft mode if needed) and runs exactly the same build rpm command
> as check-patch [3].
> 
> So there isn't real value in running exactly the same rpm build post merge,
> and we already build full permutation mode in 'build-artifacts.sh'.
> 
> Any reason to keep it?
> We can cut down valuable time in CI if we drop it and vacant more time for
> more meaningful tests.
> 
> 
> This depends on the flow: if we make check_merge gating to the merge and to
> the build we should keep the rpm build becuase at merge a rebase is done
> automatically.
> If there's not gating process performed by check-merge then I agree in
> dropping rpm build.

First of all, for oVirt Engine snapshot (non-release) builds, we should
avoid doing a full GWT compilation [all browsers x all locales]. That's
simply because the full GWT compilation is too costly for CI to run on
a regular basis.

Doing [Firefox + Chrome x English = 2 permutations] && [draft GWT build
option enabled] for snapshot builds should be enough.

The *only* downside of not doing a full GWT build is that problems with
localization resources [e.g. non-English .properties files] will not be
reported by the GWT compiler. But we have Java unit tests to cover this,
so it should be OK. (And if not, we must improve those tests.)

In general, we should do a full GWT compilation only for release builds.
Eyal mentioned at [1] that his team is working on

  'build official manual' option to standard CI

so that would be a great place to document & perform the full GWT build.

As for build jobs: if `check-merged` is indeed acting as gate for merge
[fail of `check-merged` => patch not merged, `build-artifacts` does not
execute], then it actually makes sense to:

- keep `check-merged` doing a (draft) GWT build + Engine RPM build
- maybe skip GWT build in `check-patch` [right now, there's detection
  logic => if frontend files were changed, do GWT build]

Otherwise, if `check-merged` doesn't act as gate for merge, we can just
skip GWT build / Engine RPM build for that script.

> 
> 
> 
> 
> 
> 
> [1] https://ovirt-jira.atlassian.net/browse/OVIRT-416
> [2]
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/buildTimeTrend
> [3]
> rpmbuild \
> -D "_rpmdir $PWD/output" \
> -D "_topmdir $PWD/rpmbuild" \
> -D "release_suffix ${SUFFIX}" \
> -D "ovirt_build_ut $BUILD_UT" \
> -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \
> -D "ovirt_build_draft 1" \
> --rebuild output/*.src.rpm
> 
> 
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
> 
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
> 
> 
> 
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
> 
> 
> ___
> 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-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any

2016-09-19 Thread Vojtech Szocs (oVirt JIRA) 

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

Vojtech Szocs commented on OVIRT-416:
-

> So the question is, can we reduce this to 1-2 permutations? if this is just 
> going to nightly / hourly repo then we don't need all these permutations and 
> we'll enjoy a much faster verification on the experimental flow which 
> collects artifacts from build-artifacts jobs.

+1

Full GWT build (all browsers & languages) is not needed for oVirt nightly 
(snapshot) builds. It's only needed for oVirt official (release) builds.

> We are now adding the 'build official manual' option to standard CI, so we 
> can keep the 27 permutations there for official builds. 

Sounds good to me.

> [standard-ci] build-artifacts should reuse the artifacts built on 
> check-merged if any
> -
>
> Key: OVIRT-416
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416
> Project: oVirt - virtualization made easy
>  Issue Type: Improvement
>Reporter: David Caro Estevez
>Assignee: infra
>
> Right now most projects just rebuild twice the artifacts, what for some means 
> a big waste of resources, if we could just reuse what was built previously 
> there would be no rebuilding.
> Something to take into account is that the distributions that check-merged 
> and build-artifacts run for might not match, so you can be running 
> check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an 
> example), maybe we should not allow different distros on each stage?|



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

[JIRA] (OVIRT-732) Build oVirt 4.0.4 RC4

2016-09-19 Thread sbonazzo (oVirt JIRA) 
sbonazzo created OVIRT-732:
--

 Summary: Build oVirt 4.0.4 RC4
 Key: OVIRT-732
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-732
 Project: oVirt - virtualization made easy
  Issue Type: Task
  Components: Repositories Mgmt
Reporter: sbonazzo
Assignee: infra
Priority: Highest






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

[JIRA] (OVIRT-732) Build oVirt 4.0.4 RC4

2016-09-19 Thread sbonazzo (oVirt JIRA) 

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

sbonazzo updated OVIRT-732:
---
Epic Link: OVIRT-411

> Build oVirt 4.0.4 RC4
> -
>
> Key: OVIRT-732
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-732
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: infra
>Priority: Highest
>




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

[JIRA] (OVIRT-732) Build oVirt 4.0.4 RC4

2016-09-19 Thread sbonazzo (oVirt JIRA) 

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

sbonazzo updated OVIRT-732:
---
Assignee: sbonazzo  (was: infra)
  Status: In Progress  (was: To Do)

> Build oVirt 4.0.4 RC4
> -
>
> Key: OVIRT-732
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-732
> Project: oVirt - virtualization made easy
>  Issue Type: Task
>  Components: Repositories Mgmt
>Reporter: sbonazzo
>Assignee: sbonazzo
>Priority: Highest
>




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

Vdsm source packages signed with an expired key?

2016-09-19 Thread Milan Zamazal 
Hi, on Vdsm packages downloaded from
http://resources.ovirt.org/pub/ovirt-4.0/src/vdsm/ :

% gpg --verify vdsm-4.18.13.tar.gz.sig
gpg: assuming signed data in 'vdsm-4.18.13.tar.gz'
gpg: Signature made Wed 14 Sep 2016 04:38:26 PM CEST using RSA key ID FE590CB7
gpg: Good signature from "oVirt " [expired]
gpg: Note: This key has expired!
Primary key fingerprint: 31A5 D783 7FAD 7CB2 86CD  3469 AB8C 4F9D FE59 0CB7

% gpg --list-keys infra@ovirt.org
pub   2048R/FE590CB7 2014-03-30 [expired: 2016-04-02]
uid   [ expired] oVirt 

Either I download fake packages signed with a cracked expired key, or
you sign the packages with an expired key.  Not good in any case.
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-226) Add new checks to ovirt-system-test to ensure no sensitive data leak in logs

2016-09-19 Thread sbonazzo (oVirt JIRA) 

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

sbonazzo commented on OVIRT-226:


[~eedri] this is handed by QE, see referenced bugzilla.

> Add new checks to ovirt-system-test to ensure no sensitive data leak in logs
> 
>
> Key: OVIRT-226
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-226
> Project: oVirt - virtualization made easy
>  Issue Type: New Feature
>  Components: Jenkins
>Reporter: sbonazzo
>Assignee: infra
>
> Original request is on bugzilla: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1118354
> Not sure how to implement the test using jenkins.



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

Re: Dropping rpm build from ovirt-engine check-merged.sh

2016-09-19 Thread Sandro Bonazzola 
On Sun, Sep 18, 2016 at 4:18 PM, Eyal Edri  wrote:

> Hi,
>
> Following [1] I'd like to propose to remove rpm building from the
> 'check-merged.sh' script from ovirt-engine (master for now).
>
> The job [2] takes on avg 15 min while actually the rpms are built already
> in check-patch
> (with gwt draft mode if needed) and runs exactly the same build rpm
> command as check-patch [3].
>
> So there isn't real value in running exactly the same rpm build post
> merge, and we already build full permutation mode in 'build-artifacts.sh'.
>
> Any reason to keep it?
> We can cut down valuable time in CI if we drop it and vacant more time for
> more meaningful tests.
>


This depends on the flow: if we make check_merge gating to the merge and to
the build we should keep the rpm build becuase at merge a rebase is done
automatically.
If there's not gating process performed by check-merge then I agree in
dropping rpm build.



>
>
> [1] https://ovirt-jira.atlassian.net/browse/OVIRT-416
> [2] http://jenkins.ovirt.org/job/ovirt-engine_master_check-
> merged-el7-x86_64/buildTimeTrend
> [3]
> rpmbuild \
> -D "_rpmdir $PWD/output" \
> -D "_topmdir $PWD/rpmbuild" \
> -D "release_suffix ${SUFFIX}" \
> -D "ovirt_build_ut $BUILD_UT" \
> -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \
> -D "ovirt_build_draft 1" \
> --rebuild output/*.src.rpm
>
>
> --
> Eyal Edri
> Associate Manager
> RHV DevOps
> EMEA ENG Virtualization R
> Red Hat Israel
>
> phone: +972-9-7692018
> irc: eedri (on #tlv #rhev-dev #rhev-integ)
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra