permissions to https://hub.docker.com/u/ovirt
by Yaniv Bronheim
Hi,
I need to push images to docker.io/ovirt. can you please attach my account
to ovirt admins? Currently I have to ovirtorg, but we plan to use the ovirt
one
Thank you
--
Yaniv Bronhaim.
8 years, 1 month
[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Tal Nisan (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jir... ]
Tal Nisan commented on OVIRT-1381:
----------------------------------
Quoting amuerini:
"Hi guys,
There's a good chance that patch 07e7e962975fbd1b246d7e82561dfbfb1c6196c9
introduced the regression ans is responsible for the findbugs.xml.xml files.
Can we try reverting it and see what happens?
Thanks."
It's best if we find the cause that this file is generated by this name
instead of adding it as is
On Mon, May 22, 2017 at 5:17 PM, Daniel Belenky (oVirt JIRA) <
> Re: Findbugs issues not reported correctly on Jenkins master jobs?
> ------------------------------------------------------------------
>
> Key: OVIRT-1381
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Gil Shinar
> Assignee: Daniel Belenky
>
> Adding infra-support
> On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote:
> > Just a regular "mvn findbugs:findbugs" run on master, you can revert this
> > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/
> >
> > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com>
> > wrote:
> >
> >> Hi Tal,
> >> I'm checking this right now.
> >> Can you provide the log from your local run? which files were exported on
> >> your local run?
> >>
> >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote:
> >>
> >>> I've pushed this patch to master:
> >>> https://gerrit.ovirt.org/#/c/75994/
> >>> Jenkins showed no findbugs error and I moved on to merging it
> >>>
> >>> Then I've pushed the same patch to 4.1:
> >>> https://gerrit.ovirt.org/#/c/76803/
> >>> And it resulted in two findbugs errors (though minor and style related):
> >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea
> >>> ted/898/findbugsResult/new/
> >>>
> >>> Running findbugs manually in my environment on master did report these
> >>> two issues so I'd expect the master jobs to report them as well.
> >>>
> >>> _______________________________________________
> >>> Infra mailing list
> >>> Infra(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/infra
> >>>
> >> --
> >>
> >> DANIEL BELENKY
> >>
> >> RHV DEVOPS
> >>
> >> Red Hat EMEA <https://www.redhat.com/>
> >>
> >> IRC: #rhev-integ #rhev-dev
> >> <https://red.ht/sig>
> >>
> >
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1397) Switch all standard-CI JJB scripts to use 'include-raw-escape'
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1397?page=com.atlassian.jir... ]
Barak Korren reassigned OVIRT-1397:
-----------------------------------
Assignee: Barak Korren (was: infra)
> Switch all standard-CI JJB scripts to use 'include-raw-escape'
> --------------------------------------------------------------
>
> Key: OVIRT-1397
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1397
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: Barak Korren
>
> Currently some standard-CI JJB scripts are included from YAML with 'include-raw' in macros that accept parameters. This means that thos scripts are subject to JJB variable injection. As a result, one needs to double pairs of curly braces when written in those scripts.
> The above makes it hard to use these scripts outside of JJB, for example from pipelines.
> It seems like for most scripts, there is not actual variable injection going on in practice, so we should take the time to switch to using 'include-raw-escape' to make maintaining and using the script easier.
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1397) Switch all standard-CI JJB scripts to use 'include-raw-escape'
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1397?page=com.atlassian.jir... ]
Barak Korren updated OVIRT-1397:
--------------------------------
Epic Link: OVIRT-400
> Switch all standard-CI JJB scripts to use 'include-raw-escape'
> --------------------------------------------------------------
>
> Key: OVIRT-1397
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1397
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
>
> Currently some standard-CI JJB scripts are included from YAML with 'include-raw' in macros that accept parameters. This means that thos scripts are subject to JJB variable injection. As a result, one needs to double pairs of curly braces when written in those scripts.
> The above makes it hard to use these scripts outside of JJB, for example from pipelines.
> It seems like for most scripts, there is not actual variable injection going on in practice, so we should take the time to switch to using 'include-raw-escape' to make maintaining and using the script easier.
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1397) Switch all standard-CI JJB scripts to use 'include-raw-escape'
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-1397:
-----------------------------------
Summary: Switch all standard-CI JJB scripts to use 'include-raw-escape'
Key: OVIRT-1397
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1397
Project: oVirt - virtualization made easy
Issue Type: Improvement
Components: Jenkins
Reporter: Barak Korren
Assignee: infra
Currently some standard-CI JJB scripts are included from YAML with 'include-raw' in macros that accept parameters. This means that thos scripts are subject to JJB variable injection. As a result, one needs to double pairs of curly braces when written in those scripts.
The above makes it hard to use these scripts outside of JJB, for example from pipelines.
It seems like for most scripts, there is not actual variable injection going on in practice, so we should take the time to switch to using 'include-raw-escape' to make maintaining and using the script easier.
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1381) Re: Findbugs issues not reported correctly on Jenkins master jobs?
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1381?page=com.atlassian.jir... ]
Daniel Belenky commented on OVIRT-1381:
---------------------------------------
Ok, so with [~tnisan(a)redhat.com]'s help with sending a faulty patch for debugging, I was able to reproduce the issue and find the root cause.
There is another 'findbugsXml.xml' file that we were not catching in check-patch.sh due to a type.
I'll rebase my patch back to master and resend it to apply the fix.
I'll update here.
> Re: Findbugs issues not reported correctly on Jenkins master jobs?
> ------------------------------------------------------------------
>
> Key: OVIRT-1381
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1381
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Gil Shinar
> Assignee: Daniel Belenky
>
> Adding infra-support
> On Mon, May 15, 2017 at 3:55 PM, Tal Nisan <tnisan(a)redhat.com> wrote:
> > Just a regular "mvn findbugs:findbugs" run on master, you can revert this
> > patch and run it manually yourself: https://gerrit.ovirt.org/#/c/76820/
> >
> > On Mon, May 15, 2017 at 2:15 PM, Daniel Belenky <dbelenky(a)redhat.com>
> > wrote:
> >
> >> Hi Tal,
> >> I'm checking this right now.
> >> Can you provide the log from your local run? which files were exported on
> >> your local run?
> >>
> >> On Mon, May 15, 2017 at 11:51 AM Tal Nisan <tnisan(a)redhat.com> wrote:
> >>
> >>> I've pushed this patch to master:
> >>> https://gerrit.ovirt.org/#/c/75994/
> >>> Jenkins showed no findbugs error and I moved on to merging it
> >>>
> >>> Then I've pushed the same patch to 4.1:
> >>> https://gerrit.ovirt.org/#/c/76803/
> >>> And it resulted in two findbugs errors (though minor and style related):
> >>> http://jenkins.ovirt.org/job/ovirt-engine_4.1_find-bugs_crea
> >>> ted/898/findbugsResult/new/
> >>>
> >>> Running findbugs manually in my environment on master did report these
> >>> two issues so I'd expect the master jobs to report them as well.
> >>>
> >>> _______________________________________________
> >>> Infra mailing list
> >>> Infra(a)ovirt.org
> >>> http://lists.ovirt.org/mailman/listinfo/infra
> >>>
> >> --
> >>
> >> DANIEL BELENKY
> >>
> >> RHV DEVOPS
> >>
> >> Red Hat EMEA <https://www.redhat.com/>
> >>
> >> IRC: #rhev-integ #rhev-dev
> >> <https://red.ht/sig>
> >>
> >
> >
> > _______________________________________________
> > Infra mailing list
> > Infra(a)ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> >
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[ OST Manual Job ] Updated default fallback repo
by Daniel Belenky
Hi all,
Please note that we've updated the default fallback repo in manual job
<http://jenkins.ovirt.org/job/ovirt-system-tests_manual/>.
The fallback repo defines the source from which the RPMs that are not part
of the patch being tested are being taken.
Until today, the default source was 'latest_tested' repo, which is now
replaced by 'latest_release'.
*Note* that 'latest_tested' repository shouldn't be used on regular basis,
as this repository is changing as the
experimental flow runs, so in order to avoid failures - please use the
stable 'latest_release' repo, which contains all the
rpm's that were released in the last official release of oVirt.
Thanks,
--
DANIEL BELENKY
Associate sw engineer
RHEV DEVOPS
Red Hat Israel <https://www.redhat.com/>
dbelenky(a)redhat.com IRC: #rhev-integ, #rhev-dev
<https://red.ht/sig>
8 years, 1 month
[JIRA] (OVIRT-1395) CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
by Gil Shinar (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1395?page=com.atlassian.jir... ]
Gil Shinar reassigned OVIRT-1395:
---------------------------------
Assignee: Gil Shinar (was: infra)
> CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
> ----------------------------------------------------------------------------
>
> Key: OVIRT-1395
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1395
> Project: oVirt - virtualization made easy
> Issue Type: Outage
> Components: Jenkins
> Reporter: Allon Mureinik
> Assignee: Gil Shinar
>
> CI on patch https://gerrit.ovirt.org/#/c/77074/ failed due to yum missing a mirror(?). The error:
> 04:13:13 ERROR: Command failed:
> 04:13:13 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-24-x86_64-6b7e112425ed139d649817c1e6d666bb-20792/root/ --releasever 24 install @buildsys-build autoconf git java-1.8.0-openjdk-devel make maven net-tools otopi postgresql-jdbc postgresql-server pyflakes python2-mock python-psycopg2 python2-pytest python-devel python-isort python-pep8 yum-utils --setopt=tsflags=nocontexts
> 04:13:13 Yum command has been deprecated, use dnf instead.
> 04:13:13 See 'man dnf' and 'man yum2dnf' for more information.
> 04:13:13
> 04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
> 04:13:13 Trying other mirror.
> 04:13:13
> 04:13:13
> 04:13:13 One of the configured repositories failed ("Custom ovirt-snapshot-static"),
> 04:13:13 and yum doesn't have enough cached data to continue. At this point the only
> 04:13:13 safe thing yum can do is fail. There are a few ways to work "fix" this:
> 04:13:13
> 04:13:13 1. Contact the upstream for the repository and get them to fix the problem.
> 04:13:13
> 04:13:13 2. Reconfigure the baseurl/etc. for the repository, to point to a working
> 04:13:13 upstream. This is most often useful if you are using a newer
> 04:13:13 distribution release than is supported by the repository (and the
> 04:13:13 packages for the previous distribution release still work).
> 04:13:13
> 04:13:13 3. Disable the repository, so yum won't use it by default. Yum will then
> 04:13:13 just ignore the repository until you permanently enable it again or use
> 04:13:13 --enablerepo for temporary usage:
> 04:13:13
> 04:13:13 yum-config-manager --disable ovirt-snapshot-static
> 04:13:13
> 04:13:13 4. Configure the failing repository to be skipped, if it is unavailable.
> 04:13:13 Note that yum will try to contact the repo. when it runs most commands,
> 04:13:13 so will have to try and fail each time (and thus. yum will be be much
> 04:13:13 slower). If it is a very temporary problem though, this is often a nice
> 04:13:13 compromise:
> 04:13:13
> 04:13:13 yum-config-manager --save --setopt=ovirt-snapshot-static.skip_if_unavailable=true
> 04:13:13
> 04:13:13 failure: repodata/repomd.xml from ovirt-snapshot-static: [Errno 256] No more mirrors to try.
> 04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
> Link to the jenkins output: http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/108...
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
[JIRA] (OVIRT-1395) CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
by Gil Shinar (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1395?page=com.atlassian.jir... ]
Gil Shinar updated OVIRT-1395:
------------------------------
Status: In Progress (was: To Do)
> CI on 4.1 engine patch fails on FC24 due to yum not finding the right mirror
> ----------------------------------------------------------------------------
>
> Key: OVIRT-1395
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1395
> Project: oVirt - virtualization made easy
> Issue Type: Outage
> Components: Jenkins
> Reporter: Allon Mureinik
> Assignee: infra
>
> CI on patch https://gerrit.ovirt.org/#/c/77074/ failed due to yum missing a mirror(?). The error:
> 04:13:13 ERROR: Command failed:
> 04:13:13 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-24-x86_64-6b7e112425ed139d649817c1e6d666bb-20792/root/ --releasever 24 install @buildsys-build autoconf git java-1.8.0-openjdk-devel make maven net-tools otopi postgresql-jdbc postgresql-server pyflakes python2-mock python-psycopg2 python2-pytest python-devel python-isort python-pep8 yum-utils --setopt=tsflags=nocontexts
> 04:13:13 Yum command has been deprecated, use dnf instead.
> 04:13:13 See 'man dnf' and 'man yum2dnf' for more information.
> 04:13:13
> 04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
> 04:13:13 Trying other mirror.
> 04:13:13
> 04:13:13
> 04:13:13 One of the configured repositories failed ("Custom ovirt-snapshot-static"),
> 04:13:13 and yum doesn't have enough cached data to continue. At this point the only
> 04:13:13 safe thing yum can do is fail. There are a few ways to work "fix" this:
> 04:13:13
> 04:13:13 1. Contact the upstream for the repository and get them to fix the problem.
> 04:13:13
> 04:13:13 2. Reconfigure the baseurl/etc. for the repository, to point to a working
> 04:13:13 upstream. This is most often useful if you are using a newer
> 04:13:13 distribution release than is supported by the repository (and the
> 04:13:13 packages for the previous distribution release still work).
> 04:13:13
> 04:13:13 3. Disable the repository, so yum won't use it by default. Yum will then
> 04:13:13 just ignore the repository until you permanently enable it again or use
> 04:13:13 --enablerepo for temporary usage:
> 04:13:13
> 04:13:13 yum-config-manager --disable ovirt-snapshot-static
> 04:13:13
> 04:13:13 4. Configure the failing repository to be skipped, if it is unavailable.
> 04:13:13 Note that yum will try to contact the repo. when it runs most commands,
> 04:13:13 so will have to try and fail each time (and thus. yum will be be much
> 04:13:13 slower). If it is a very temporary problem though, this is often a nice
> 04:13:13 compromise:
> 04:13:13
> 04:13:13 yum-config-manager --save --setopt=ovirt-snapshot-static.skip_if_unavailable=true
> 04:13:13
> 04:13:13 failure: repodata/repomd.xml from ovirt-snapshot-static: [Errno 256] No more mirrors to try.
> 04:13:13 http://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc24/repo...: [Errno 14] HTTP Error 404 - Not Found
> Link to the jenkins output: http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc24-x86_64/108...
--
This message was sent by Atlassian JIRA
(v1000.990.2#100044)
8 years, 1 month
