- Infra - oVirt List Archives

[JIRA] (OVIRT-2132) can't connect to monitoring.ovirt.org
by sbonazzo (oVirt JIRA) 04 Jun '18

04 Jun '18

sbonazzo created OVIRT-2132: ------------------------------- Summary: can't connect to monitoring.ovirt.org Key: OVIRT-2132 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2132 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, today I can't connect to monitoring.ovirt.org. Can you please check its status and bring back it online? Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D 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#100086)

1 0

[JIRA] (OVIRT-2131) Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2131?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2131: ----------------------------- Summary: Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 (was: Cannot find a valid baseurl for repo: base/7/x86_64) > Master CQ: Cannot find a valid baseurl for repo: base/7/x86_64 > -------------------------------------------------------------- > > Key: OVIRT-2131 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > test failed. looking into it > '11:12:55 [basic-suit] > 11:12:55 [basic-suit] - STDERR > 11:12:55 [basic-suit] + HUGEPAGES=3 > 11:12:55 [basic-suit] + yum update -y iptables > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), > 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only > 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working > 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer > 11:12:55 [basic-suit] distribution release than is supported by the repository (and the > 11:12:55 [basic-suit] packages for the previous distribution release still work). > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled > 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum > 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it > 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --disable <repoid> > 11:12:55 [basic-suit] or > 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. > 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, > 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much > 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice > 11:12:55 [basic-suit] compromise: > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 > 11:12:55 [basic-suit] > 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:55 [basic-suit] Error while running thread > 11:12:55 [basic-suit] Traceback (most recent call last): > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue > 11:12:55 [basic-suit] queue.put({'return': func()}) > 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host > 11:12:55 [basic-suit] host.name(), > 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 > 11:12:57 [upgrade-from-release-suit] Finish: creating root cache > 11:12:57 [upgrade-from-release-suit] Finish: chroot init > 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: > 11:12:57 [upgrade-from-release-suit] Finish: run > 11:12:57 [upgrade-from-release-suit] Init took 208 seconds > 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by Gal Ben Haim (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2108: ------------------------------------- As stated, it will require building lago for ppc64. It's difficult to evaluate the amount of time that is needed for this task, but for sure it's not something immediate. > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: sbonazzo > Assignee: infra > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2131) Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

Dafna Ron created OVIRT-2131: -------------------------------- Summary: Cannot find a valid baseurl for repo: base/7/x86_64 Key: OVIRT-2131 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2131 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra test failed. looking into it '11:12:55 [basic-suit] 11:12:55 [basic-suit] - STDERR 11:12:55 [basic-suit] + HUGEPAGES=3 11:12:55 [basic-suit] + yum update -y iptables 11:12:55 [basic-suit] 11:12:55 [basic-suit] 11:12:55 [basic-suit] One of the configured repositories failed (Unknown), 11:12:55 [basic-suit] and yum doesn't have enough cached data to continue. At this point the only 11:12:55 [basic-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: 11:12:55 [basic-suit] 11:12:55 [basic-suit] 1. Contact the upstream for the repository and get them to fix the problem. 11:12:55 [basic-suit] 11:12:55 [basic-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working 11:12:55 [basic-suit] upstream. This is most often useful if you are using a newer 11:12:55 [basic-suit] distribution release than is supported by the repository (and the 11:12:55 [basic-suit] packages for the previous distribution release still work). 11:12:55 [basic-suit] 11:12:55 [basic-suit] 3. Run the command with the repository temporarily disabled 11:12:55 [basic-suit] yum --disablerepo=<repoid> ... 11:12:55 [basic-suit] 11:12:55 [basic-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum 11:12:55 [basic-suit] will then just ignore the repository until you permanently enable it 11:12:55 [basic-suit] again or use --enablerepo for temporary usage: 11:12:55 [basic-suit] 11:12:55 [basic-suit] yum-config-manager --disable <repoid> 11:12:55 [basic-suit] or 11:12:55 [basic-suit] subscription-manager repos --disable=<repoid> 11:12:55 [basic-suit] 11:12:55 [basic-suit] 5. Configure the failing repository to be skipped, if it is unavailable. 11:12:55 [basic-suit] Note that yum will try to contact the repo. when it runs most commands, 11:12:55 [basic-suit] so will have to try and fail each time (and thus. yum will be be much 11:12:55 [basic-suit] slower). If it is a very temporary problem though, this is often a nice 11:12:55 [basic-suit] compromise: 11:12:55 [basic-suit] 11:12:55 [basic-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true 11:12:55 [basic-suit] 11:12:55 [basic-suit] Cannot find a valid baseurl for repo: base/7/x86_64 11:12:55 [basic-suit] 11:12:55 [basic-suit] * [Thread-3] Deploy VM lago-basic-suite-master-host-1: ERROR (in 0:00:30) 11:12:55 [basic-suit] Error while running thread 11:12:55 [basic-suit] Traceback (most recent call last): 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 11:12:55 [basic-suit] queue.put({'return': func()}) 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host 11:12:55 [basic-suit] host.name(), 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 11:12:55 [basic-suit] Error while running thread 11:12:55 [basic-suit] Traceback (most recent call last): 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/utils.py", line 58, in _ret_via_queue 11:12:55 [basic-suit] queue.put({'return': func()}) 11:12:55 [basic-suit] File "/usr/lib/python2.7/site-packages/lago/prefix.py", line 1660, in _deploy_host 11:12:55 [basic-suit] host.name(), 11:12:55 [basic-suit] RuntimeError: /dev/shm/ost/deployment-basic-suite-master/default/scripts/_home_jenkins_workspace_ovirt-master_change-queue-tester_ovirt-system-tests_basic-suite-master_deploy-scripts_setup_host_el7.sh failed with status 1 on lago-basic-suite-master-host-1 11:12:57 [upgrade-from-release-suit] Finish: creating root cache 11:12:57 [upgrade-from-release-suit] Finish: chroot init 11:12:57 [upgrade-from-release-suit] INFO: Installed packages: 11:12:57 [upgrade-from-release-suit] Finish: run 11:12:57 [upgrade-from-release-suit] Init took 208 seconds 11:12:57 [upgrade-from-release-suit] ============================' -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1466) Switch to deploying JJB via PIP
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1466?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1466: ----------------------------------- Assignee: Barak Korren (was: infra) > Switch to deploying JJB via PIP > ------------------------------- > > Key: OVIRT-1466 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1466 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > Labels: jjb, standard-ci > > Since the JJB deployment job runs directly on the Jenkins master, we've been creating and using an RPM package for JJB. This made it hard to switch JJB versions. > Once we implement OVIRT-1465, we gain sufficient isolation via mock to allow ourselves to install JJB via pip. > We can set things up so that pip installs a specific JJB version, that way we can gate JJB version updates and have then checked by check-patch. We can even expand the upstream polling system to track JJB versions for us and create update patches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2077) Clicking Reply doesn't display Documentation in the dialog window
by Evgheni Dereveanchin (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2077?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2077: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Clicking Reply doesn't display Documentation in the dialog window > ----------------------------------------------------------------- > > Key: OVIRT-2077 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2077 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Gerrit/git > Reporter: Emma Heftman > Assignee: Evgheni Dereveanchin > Attachments: image.png, image.png, image.png > > > My name appears correctly as the committer and uploader but as the Assignee > it appears without an icon...which is strange. > When i hit Reply to do +1 for Documentation, there is no Documentation > option in the dialog. > Also,there is an icon next to Uploader saying it was uploaded without a > certificate. > It also says uploader emmahef > while committer is Emma Heftman > I recently changed my Full Name from emmahef to Emma Heftman. But when i > log out and log in, the Full Name in Profile goes back to emmahef, while > the Full Name that appears in the Contact Information window is Emma > Heftman. > In my .ssh config file it says: > host gerrit.ovirt.org > HostName gerrit.ovirt.org > Port 29418 > User emmahef > The change I'm assigned to is: https://gerrit.ovirt.org/#/c/91103/ > -- > Thanks a lot, > Emma > *Emma Heftman* > Technical Writer, Red Hat Israel > [image: Inline image 1] -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1626
by jenkins＠jenkins.phx.ovirt.org 04 Jun '18

04 Jun '18

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Sandro Bonazzola] guest agent: move to fc28 [Martin Perina] ovirt-engine: Drop FC28 build from 4.2 [arachmani] ovirt-engine-api-explorer: move from fc27 to fc 28 ------------------------------------------ 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_64/…> > 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 72898b0f612cfb12bc7b860c4eeb90d0efcb49b7 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 72898b0f612cfb12bc7b860c4eeb90d0efcb49b7 Commit message: "ovirt-engine-api-explorer: move from fc27 to fc 28" > git rev-list --no-walk 6bd80c8c7d578e02cc43e27ad05ef41fe6796c91 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4626862510290130928.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 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/fedora-base-fc25/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2108: ---------------------------------- [~gbenhaim(a)redhat.com] I remember this wasn't possible due to missing pkgs on power, but I don't remember any details. Is it possible given the time and resources? > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: sbonazzo > Assignee: infra > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2078: ---------------------------------- [~sbonazzo(a)redhat.com] and [~mskrivanek] were the original requestors for this user story, they might help add more info. > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2130) Support for private changes in Gerrit
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2130?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2130: ----------------------------- Resolution: Duplicate Status: Done (was: To Do) https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Support for private changes in Gerrit > ------------------------------------- > > Key: OVIRT-2130 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2130 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > Hi, > can you please upgrade gerrit to latest version so we can leverage support > for private changes when working on security related patches? > Thanks, > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > 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#100086)

1 0