[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2
by eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jir... ]
eyal edri commented on OVIRT-2175:
----------------------------------
I agree, let's start tracking which projects are on V1 and schedule dates for moving at least 2 projects a week.
If a project maintainer can't / won't move, we need to document the reason and possibly open JIRA tickets to research the gap or document the missing feature.
I suggest starting opening tickets to each project we plan to move and document progress there, start reaching out to the project maintainers.
This might also help speed up adding downstream jobs.
> Move oVirt projects to STDCI V2
> -------------------------------
>
> Key: OVIRT-2175
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2175
> Project: oVirt - virtualization made easy
> Issue Type: Epic
> Components: oVirt CI
> Reporter: Daniel Belenky
> Assignee: infra
>
> As STDCI V2 is live and production for a while now, it's time to proactively push and assist oVirt projects to move to STDCI V2. Projects will benefit from new STDCI V2 features such as the ability to modify the distributions and architectures they build on without having to send patches to the 'Jenkins' repo.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jir... ]
Daniel Belenky commented on OVIRT-2175:
---------------------------------------
We need to add more tasks with more projects that we find appropriate and applicable for migration to V2.
[~bkorren(a)redhat.com] [~eedri] WDYT? we need to be much more proactive on this.
I think that migrating 1 or even 2 projects per week (at least setting V2 jobs) is a good goal to start with.
> Move oVirt projects to STDCI V2
> -------------------------------
>
> Key: OVIRT-2175
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2175
> Project: oVirt - virtualization made easy
> Issue Type: Epic
> Components: oVirt CI
> Reporter: Daniel Belenky
> Assignee: infra
>
> As STDCI V2 is live and production for a while now, it's time to proactively push and assist oVirt projects to move to STDCI V2. Projects will benefit from new STDCI V2 features such as the ability to modify the distributions and architectures they build on without having to send patches to the 'Jenkins' repo.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
Fwd: [CQ]: 92362, 1 (ovirt-jboss-modules-maven-plugin) failed
"ovirt-master" system tests
by Dafna Ron
Build-artifacts failed.
Sent mail to Sandro
---------- Forwarded message ----------
From: Dafna Ron <dron(a)redhat.com>
Date: Tue, Jun 19, 2018 at 12:14 PM
Subject: Fwd: [CQ]: 92362, 1 (ovirt-jboss-modules-maven-plugin) failed
"ovirt-master" system tests
To: Sandro Bonazzola <sbonazzo(a)redhat.com>
Hi,
Can you have a look? we are failing build-artifacts.
https://jenkins.ovirt.org/job/ovirt-jboss-modules-maven-
plugin_standard-on-merge/2/consoleFull
thanks,
Dafna
---------- Forwarded message ----------
From: oVirt Jenkins <jenkins(a)ovirt.org>
Date: Tue, Jun 19, 2018 at 12:03 PM
Subject: [CQ]: 92362, 1 (ovirt-jboss-modules-maven-plugin) failed
"ovirt-master" system tests
To: infra(a)ovirt.org
Change 92362,1 (ovirt-jboss-modules-maven-plugin) is probably the reason
behind
recent system test failures in the "ovirt-master" change queue and needs to
be
fixed.
This change had been removed from the testing queue. Artifacts build from
this
change will not be released until it is fixed.
For further details about the change see:
https://gerrit.ovirt.org/#/c/92362/1
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8276/
_______________________________________________
Infra mailing list -- infra(a)ovirt.org
To unsubscribe send an email to infra-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/communit
y/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/infra@ovirt.org/messag
e/PVILMHGC4DTIY7ZRSTWOW73FZMZVZBWI/
6 years, 7 months
[JIRA] (OVIRT-2180) Missing packages when trying to create
reposync-config ovirt-master on Fedora 28
by sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2180?page=com.atlassian.jir... ]
sbonazzo commented on OVIRT-2180:
---------------------------------
We already dropped fluentd support on Fedora 28, you can go ahead.
> Missing packages when trying to create reposync-config ovirt-master on Fedora 28
> --------------------------------------------------------------------------------
>
> Key: OVIRT-2180
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2180
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: OST
> Reporter: Gal Ben Haim
> Assignee: infra
>
> When trying to create reposync-config for ovirt-master on FC28 the following packges are missing:
> {code:java}
> Error:
> Problem 1: conflicting requests
> - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180308070539.git35a6428.fc28.x86_64
> - package ovirt-host-4.3.0-0.0.master.20180530065728.git836691d.fc28.s390x does not have a compatible architecture
> - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180530070102.git836691d.fc28.x86_64
> - package ovirt-host-4.3.0-0.0.master.20180604121623.git6aeb275.fc28.s390x does not have a compatible architecture
> - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180604121713.git6aeb275.fc28.x86_64
> - package ovirt-host-4.3.0-0.0.master.20180607122548.gitbdfe919.fc28.s390x does not have a compatible architecture
> - nothing provides katello-agent needed by ovirt-host-4.3.0-0.0.master.20180607122828.gitbdfe919.fc28.x86_64
> Problem 2: conflicting requests
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch
> Problem 3: conflicting requests
> - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed
> - package ovirt-engine-extension-aaa-ldap-setup-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.6, but none of the providers can be installed
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch
> Problem 4: conflicting requests
> - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitf069cb9.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed
> - package ovirt-engine-extension-aaa-ldap-1.3.8-0.0.master.gitff6678b.fc28.noarch requires ovirt-engine >= 3.5, but none of the providers can be installed
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180306070711.git2d3047c73c.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180530170515.git426823eb4a1.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601113423.git27f22ec3801.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601125541.gita6e87e15f8e.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180601151553.git588d48026c5.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603153247.git23ea19a71b9.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603185407.git60b31ae4ff6.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180603200841.git0b63d547fb2.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604071126.git524908b0e26.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604084747.git8b9ad6a435e.fc28.noarch
> - nothing provides fluentd needed by ovirt-engine-4.3.0-0.0.master.20180604135226.git3e394fa5ef3.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180607083125.git21907ef1790.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608075105.gitff92e12aed8.fc28.noarch
> - nothing provides ovirt-cockpit-sso needed by ovirt-engine-4.3.0-0.0.master.20180608115732.gita4bbacb7277.fc28.noarch
> {code}
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs
for different branches
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-2201:
-------------------------------------
{quote}
* get the general CI health of a release (master vs 4.2)
{quote}
How is that different then checking the latest CQ/OST status?
Also why is that important if you know you have a tested composite in 'tested'?
{quote}
* take immediate action on the specific branch of a project
{quote}
Assuming you can know the CQ/OST status of a branch, why would you need the pre-CQ/OST post-merge status?
> [regression] STDCI v2 doesn't distinguish jobs for different branches
> ---------------------------------------------------------------------
>
> Key: OVIRT-2201
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Standard CI (Pipelines)
> Reporter: sbonazzo
> Assignee: infra
>
> In V1 we had jobs with different name based on branches they were building.
> In V2 we have single job building all branches.
> As an example for imgbased:
> https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu...
> will contain randomly 4.2 or master builds.
> This won't allow to filter jenkins to see which branches are failing to
> build, forcing developers to check manually.
> This also won't allow to check if latest build landed in tested repo
> because thee build may be targeted to a different branch than the one under
> check.
> To me this is a regression that will make me rethink about the switching to
> v2 and considering reverting to v1.
> --
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
> Red Hat EMEA <https://www.redhat.com/>
> sbonazzo(a)redhat.com
> <https://red.ht/sig>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs
for different branches
by sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ]
sbonazzo commented on OVIRT-2201:
---------------------------------
{quote}"As an oVirt developer, I want to see the build status for the HEAD commit of a particular branch of my project so that I can <need to fill in reason here>"{quote}
- get the general CI health of a release (master vs 4.2)
- take immediate action on the specific branch of a project
{quote}"As an oVirt developer I want to have a way to acquire the lasted CI build on a particular branch on a particular project so that I can use it as a dependency for other jobs".
About this last one - I guess we can ask people in devel if "tested" would be a good enough compromise?
{quote}
Issue with this is that you may have a change which depends on a change in another package (example: ovirt-host-deploy with otopi) and having to rely on tested instead of lastSuccessfullBuild means you need to wait for change queue to succeed and publish to tested before being able to run check-patch. This means a delay on the handling of the patch of ~1 hour which is suboptimal.
> [regression] STDCI v2 doesn't distinguish jobs for different branches
> ---------------------------------------------------------------------
>
> Key: OVIRT-2201
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Standard CI (Pipelines)
> Reporter: sbonazzo
> Assignee: infra
>
> In V1 we had jobs with different name based on branches they were building.
> In V2 we have single job building all branches.
> As an example for imgbased:
> https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu...
> will contain randomly 4.2 or master builds.
> This won't allow to filter jenkins to see which branches are failing to
> build, forcing developers to check manually.
> This also won't allow to check if latest build landed in tested repo
> because thee build may be targeted to a different branch than the one under
> check.
> To me this is a regression that will make me rethink about the switching to
> v2 and considering reverting to v1.
> --
> SANDRO BONAZZOLA
> ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
> Red Hat EMEA <https://www.redhat.com/>
> sbonazzo(a)redhat.com
> <https://red.ht/sig>
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100087)
6 years, 7 months
Build failed in Jenkins:
system-sync_mirrors-centos-updates-el7-x86_64 #1673
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...>
Changes:
[Sandro Bonazzola] automation: add missing python-six package
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_6...>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git
> git --version # timeout=10
> git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 16730ba6637684961f7acf86a07cce81c0dd19f8 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 16730ba6637684961f7acf86a07cce81c0dd19f8
Commit message: "automation: add missing python-six package"
> git rev-list --no-walk f68ee1c69229c9244eba01bcac4c409b9049e49f # timeout=10
[system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1639502393174931532.sh
+ jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf
Checking if mirror needs a resync
Traceback (most recent call last):
File "/usr/bin/reposync", line 343, in <module>
main()
File "/usr/bin/reposync", line 175, in main
my.doRepoSetup()
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup
return self._getRepos(thisrepo, True)
File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos
self._repos.doSetup(thisrepo)
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup
self.retrieveAllMD()
File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD
dl = repo._async and repo._commonLoadRepoXML(repo)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML
local = self.cachedir + '/repomd.xml'
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda>
cachedir = property(lambda self: self._dirGetAttr('cachedir'))
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr
self.dirSetup()
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup
self._dirSetupMkdir_p(dir)
File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p
raise Errors.RepoError, msg
yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7'
Build step 'Execute shell' marked build as failure
6 years, 7 months