- Infra - oVirt List Archives

engine 4.1 check-patch on FC24 is failing for missing packages
by Martin Perina 13 Feb '17

13 Feb '17

Hi, could you please take a look? http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/572 http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/573/ Thanks Martin

2 1

[JIRA] (OVIRT-1141) Engine CI fails on Fedora 24 due to failing dependencies
by Barak Korren (oVirt JIRA) 13 Feb '17

13 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1141?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1141: ----------------------------------- Assignee: Barak Korren (was: infra) > Engine CI fails on Fedora 24 due to failing dependencies > -------------------------------------------------------- > > Key: OVIRT-1141 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1141 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Allon Mureinik > Assignee: Barak Korren > > Engine CI on Fedora 24 seems to fail when attempting to yum install due to missing/borken dependencies(?): > 08:43:09 Getting requirements for ovirt-engine-4.2.0-0.0.master.20170213084126.git7ea17aa.fc24.src > 08:43:09 --> assertj-core-2.2.0-2.fc24.noarch > 08:43:10 --> hystrix-core-1.4.21-5.fc24.noarch > 08:43:10 --> hystrix-metrics-event-stream-1.4.21-5.fc24.noarch > 08:43:10 --> Already installed : 1:java-1.8.0-openjdk-devel-1.8.0.121-1.b14.fc24.x86_64 > 08:43:10 --> Already installed : javapackages-tools-4.6.0-15.fc24.noarch > 08:43:10 --> Already installed : 1:make-4.1-5.fc24.x86_64 > 08:43:10 --> Already installed : maven-3.3.9-4.fc24.noarch > 08:43:10 --> Already installed : python-2.7.13-1.fc24.x86_64 > 08:43:10 --> Already installed : python-devel-2.7.13-1.fc24.x86_64 > 08:43:10 --> python3-devel-3.5.1-7.fc24.x86_64 > 08:43:10 --> Already installed : systemd-229-18.fc24.x86_64 > 08:43:10 --> Already installed : unzip-6.0-31.fc24.x86_64 > 08:43:13 Error: Package: perl-Unicode-Normalize-1.25-2.fc24.x86_64 (@fedora) > 08:43:13 Requires: libperl.so.5.22()(64bit) > 08:43:13 Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24) > 08:43:13 ~libperl.so.5.24()(64bit) > 08:43:13 Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Error: Package: perl-PathTools-3.62-3.fc24.x86_64 (@updates) > 08:43:13 Requires: libperl.so.5.22()(64bit) > 08:43:13 Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24) > 08:43:13 ~libperl.so.5.24()(64bit) > 08:43:13 Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Error: Package: libselinux-2.5-13.fc25.i686 (fedora-updates-fc24) > 08:43:13 Requires: libsepol(x86-32) >= 2.5-10 > 08:43:13 Installing: libsepol-2.5-3.fc24.i686 (fedora-base-fc24) > 08:43:13 libsepol(x86-32) = 2.5-3.fc24 > 08:43:13 Installed: libsepol-2.5-10.fc24.x86_64 (@updates) > 08:43:13 ~libsepol(x86-64) = 2.5-10.fc24 > 08:43:13 Error: Package: python3-devel-3.5.1-7.fc24.x86_64 (fedora-base-fc24) > 08:43:13 Requires: python3-libs(x86-64) = 3.5.1-7.fc24 > 08:43:13 Installed: python3-libs-3.5.2-3.fc24.x86_64 (@updates) > 08:43:13 python3-libs(x86-64) = 3.5.2-3.fc24 > 08:43:13 Available: python3-libs-3.5.1-7.fc24.x86_64 (fedora-base-fc24) > 08:43:13 python3-libs(x86-64) = 3.5.1-7.fc24 > 08:43:13 Error: Package: perl-MIME-Base64-3.15-349.fc24.x86_64 (@fedora) > 08:43:13 Requires: libperl.so.5.22()(64bit) > 08:43:13 Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24) > 08:43:13 ~libperl.so.5.24()(64bit) > 08:43:13 Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Error: Package: 3:perl-Socket-2.024-1.fc24.x86_64 (@updates) > 08:43:13 Requires: libperl.so.5.22()(64bit) > 08:43:13 Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24) > 08:43:13 ~libperl.so.5.24()(64bit) > 08:43:13 Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Error: Package: perl-Data-Dumper-2.158-348.fc24.x86_64 (@fedora) > 08:43:13 Requires: libperl.so.5.22()(64bit) > 08:43:13 Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24) > 08:43:13 ~libperl.so.5.24()(64bit) > 08:43:13 Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Error: Package: perl-TermReadKey-2.33-4.fc24.x86_64 (@fedora) > 08:43:13 Requires: libperl.so.5.22()(64bit) > 08:43:13 Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24) > 08:43:13 ~libperl.so.5.24()(64bit) > 08:43:13 Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24) > 08:43:13 libperl.so.5.22()(64bit) > 08:43:13 Error: Package: ncurses-libs-6.0-5.20160116.fc24.i686 (fedora-base-fc24) > 08:43:13 Requires: ncurses-base = 6.0-5.20160116.fc24 > 08:43:13 Installed: ncurses-base-6.0-6.20160709.fc24.noarch (@updates) > 08:43:13 ncurses-base = 6.0-6.20160709.fc24 > 08:43:13 Available: ncurses-base-6.0-5.20160116.fc24.noarch (fedora-base-fc24) > 08:43:13 ncurses-base = 6.0-5.20160116.fc24 > 08:43:13 Error: Package: libselinux-2.5-13.fc25.i686 (fedora-updates-fc24) > 08:43:13 Requires: libsepol(x86-32) >= 2.5-10 > 08:43:13 Available: libsepol-2.5-3.fc24.i686 (fedora-base-fc24) > 08:43:13 libsepol(x86-32) = 2.5-3.fc24 > 08:43:13 Installed: libsepol-2.5-10.fc24.x86_64 (@updates) > 08:43:13 ~libsepol(x86-64) = 2.5-10.fc24 > 08:43:13 You could try using --skip-broken to work around the problem > 08:43:13 You could try running: rpm -Va --nofiles --nodigest > 08:43:13 Took 130 seconds > Link to failing CI job: > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/12… -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1145) Python SDK v4 check-patch job fails on fc24
by Ondra Machacek (oVirt JIRA) 13 Feb '17

13 Feb '17

Ondra Machacek created OVIRT-1145: ------------------------------------- Summary: Python SDK v4 check-patch job fails on fc24 Key: OVIRT-1145 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1145 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Ondra Machacek Assignee: infra It's really hard to get any reasonable information why this[1], job fails. It's Python SDK v4 check-patch job on sdk_v41 branch on fc24. Can you point me to where should I take a look? No logs there. [1] http://jenkins.ovirt.org/job/python-ovirt-engine-sdk4_4.1_check-patch-fc24-… -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by eyal edri [Administrator] (oVirt JIRA) 13 Feb '17

13 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1143: --------------------------------------------- Resolution: Duplicate Status: Done (was: To Do) > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1144) Make projects support more than one CI system
by eyal edri [Administrator] (oVirt JIRA) 13 Feb '17

13 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1144?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1144: --------------------------------------------- Parent Issue: OVIRT-848 (was: OVIRT-1143) > Make projects support more than one CI system > --------------------------------------------- > > Key: OVIRT-1144 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1144 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > Today we use 'automation' dir for running all standard CI flows on oVirt CI. > We need to take into consideration future projects will use multiple CI systems and be a part of multiple projects. > So a question is raised on how will the structure of dirs/files served in oVirt will look like. > One suggestion was to use .ovirtci which will translate to all the needs the oVirt CI will need. > There can be other options, this is the place to discuss them. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1144) Make projects support more than one CI system
by eyal edri [Administrator] (oVirt JIRA) 13 Feb '17

13 Feb '17

eyal edri [Administrator] created OVIRT-1144: ------------------------------------------------ Summary: Make projects support more than one CI system Key: OVIRT-1144 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1144 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra Today we use 'automation' dir for running all standard CI flows on oVirt CI. We need to take into consideration future projects will use multiple CI systems and be a part of multiple projects. So a question is raised on how will the structure of dirs/files served in oVirt will look like. One suggestion was to use .ovirtci which will translate to all the needs the oVirt CI will need. There can be other options, this is the place to discuss them. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by eyal edri [Administrator] (oVirt JIRA) 13 Feb '17

13 Feb '17

eyal edri [Administrator] created OVIRT-1143: ------------------------------------------------ Summary: Standard CI V2 Key: OVIRT-1143 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: eyal edri [Administrator] Assignee: infra There are a few things we need to consider for oVirt Standard CI V2, This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1143) Standard CI V2
by eyal edri [Administrator] (oVirt JIRA) 13 Feb '17

13 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1143?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1143: --------------------------------------------- Epic Link: OVIRT-403 > Standard CI V2 > --------------- > > Key: OVIRT-1143 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1143 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: standard-ci > > There are a few things we need to consider for oVirt Standard CI V2, > This ticket will be a parent ticket for all of them and will serve as main RFE. -- This message was sent by Atlassian JIRA (v1000.747.1#100028)

1 0

[JIRA] (OVIRT-1047) Build and check KubeVirt Demo image
by eyal edri [Administrator] (oVirt JIRA) 13 Feb '17

13 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1047: -------------------------------------------------- [~fdeutsch] OK, so you can also understand that changing existing framework that we've been using in the past years has a certain toll in terms of time & resources, So I would like to know what is the main blocker or issue from your perspective from not using existing tools and for the need to develop a new standard which will require time, time that is taken from other projects, just to satisfy a single project. Putting aside (silly) names, I think we deserve to know the reason why 'automation' dir can't be used and then we can discuss if/how we can support anything different. > 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: infra > 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.747.1#100028)

1 0

[JIRA] (OVIRT-1047) Build and check KubeVirt Demo image
by Fabian Deutsch (oVirt JIRA) 13 Feb '17

13 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jira.… ] Fabian Deutsch edited comment on OVIRT-1047 at 2/13/17 1:28 PM: ---------------------------------------------------------------- You know - I don't disagree - if I was reading the ticket (as a 3rd person), then I'd say it's silly as well - to just discuss names. But to be a good citizen, I'd say an ovirtci file would make sense. [~eedri] the .ovirtci file could -in the easiest case - effectively have the same structure as the dir, it would just be fields in the yaml file. {code} toYaml() { for F in automation/*; do echo $F: |" ; sed "s/^/ /" < $F ; echo -e "\n---" done echo } $ toYaml > .ovirtci {code} and back {code} fromYaml() { sed -e "s/^automation/cat <<EOF > automation/ ; s/---/EOF/ ; s/: |// ; s/^ //" } $ fromYaml < .ovirtci {code} And from there it could be gracefully improved - if wanted. was (Author: fdeutsch): You know - I don't disagree - if I was reading the ticket, then I'd say it's silly as well - to just discuss names. But to be a good citizen, I'd say an ovirtci file would make sense. [~eedri] the .ovirtci file could -in the easiest case - effectively have the same structure as the dir, it would just be fields in the yaml file. {code} toYaml() { for F in automation/*; do echo $F: |" ; sed "s/^/ /" < $F ; echo -e "\n---" done echo } $ toYaml > .ovirtci {code} and back {code} fromYaml() { sed -e "s/^automation/cat <<EOF > automation/ ; s/---/EOF/ ; s/: |// ; s/^ //" } $ fromYaml < .ovirtci {code} And from there it could be gracefully improved - if wanted. > 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: infra > 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.747.1#100028)

1 0