December 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-935) Unable to build fc25 chroots with mock
by Nadav Goldin (oVirt JIRA) 12 Dec '16

12 Dec '16

Nadav Goldin created OVIRT-935: ---------------------------------- Summary: Unable to build fc25 chroots with mock Key: OVIRT-935 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-935 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Nadav Goldin Assignee: infra Mock fails when trying to build the chroot for fedora25, on installing '@buildsys-build' group(with dnf) stage. Open bug: https://bugzilla.redhat.com/show_bug.cgi?id=1360781 Temporarily workaround: add the 'libcrypt' package to '.packages.fc25' file. Possible solution: patch mock-*fc25*.cfg file in Jenkins repository to always install 'libcrypt' first. Until fixed this will block us from building anything with mock on fc25(hit it when trying to build fc25 RPMs for lago). Error logs: {code} DEBUG util.py:502: Executing command: ['/usr/bin/yum-deprecated', '--installroot', '/var/lib/mock/fedora-25-x86_64-2474d86945a1de9c6d14549ec2401b9c-8291/root/', '--releasever', '25', 'install', '@buildsys-build', 'git', 'python', 'python-dulwich', 'python-setuptools', 'yum', 'yum-utils', '--setopt=tsflags=nocontexts'] with env {'PS1': '<mock-chroot> \\s-\\v\\$ ', .... DEBUG util.py:421: Yum command has been deprecated, use dnf instead. DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. DEBUG util.py:421: Error: libcrypt conflicts with libcrypt-nss-2.24-3.fc25.x86_64 DEBUG util.py:421: Error: libcrypt-nss conflicts with libcrypt-2.24-3.fc25.x86_64 DEBUG util.py:421: You could try using --skip-broken to work around the problem DEBUG util.py:421: You could try running: rpm -Va --nofiles --nodigest DEBUG util.py:557: Child return code was: 1 DEBUG util.py:180: kill orphans {code} -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

Re: http://lists.ovirt.org/pipermail/announce/ is not reachable
by Eyal Edri 12 Dec '16

12 Dec '16

I'm not sure who gets emails sent to infra-owner list. best to send it to infra or infra support. Adding Evgheni and Duck who are working on migration of the mm server. On Dec 12, 2016 2:58 PM, "Sandro Bonazzola" <sbonazzo(a)redhat.com> wrote: > The lists server is not reachable anymore. Looks like a dns issue: > > $ traceroute lists.ovirt.org > lists.ovirt.org: Name or service not known > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com >

4 3

mirrors errors
by Eyal Edri 12 Dec '16

12 Dec '16

Doesn't seem to be we're over the unavailable mirrors issue with the new repos added to STD CI: Lets start working on mirroring the relevant repos to mirrors.phx.ovirt.org and get control over the update process. http://jenkins.ovirt.org/job/jenkins_master_check-patch-fc24-x86_64/16/arti… DEBUG util.py:421: https://mirrors.cat.pdx.edu/fedora/linux/updates/24/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: https://dl.fedoraproject.org/pub/fedora/linux/updates/24/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: http://fedora.bhs.mirrors.ovh.net/linux/updates/24/x86_64/repodata/repomd.x…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: http://mirror.its.dal.ca/pub/fedora/linux/updates/24/x86_64/repodata/repomd…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: https://mirror.csclub.uwaterloo.ca/fedora/linux/updates/24/x86_64/repodata/…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: One of the configured repositories failed (updates), DEBUG util.py:421: and yum doesn't have enough cached data to continue. At this point the only DEBUG util.py:421: safe thing yum can do is fail. There are a few ways to work "fix" this: DEBUG util.py:421: 1. Contact the upstream for the repository and get them to fix the problem. DEBUG util.py:421: 2. Reconfigure the baseurl/etc. for the repository, to point to a working DEBUG util.py:421: upstream. This is most often useful if you are using a newer DEBUG util.py:421: distribution release than is supported by the repository (and the DEBUG util.py:421: packages for the previous distribution release still work). DEBUG util.py:421: 3. Disable the repository, so yum won't use it by default. Yum will then DEBUG util.py:421: just ignore the repository until you permanently enable it again or use DEBUG util.py:421: --enablerepo for temporary usage: DEBUG util.py:421: yum-config-manager --disable updates DEBUG util.py:421: 4. Configure the failing repository to be skipped, if it is unavailable. DEBUG util.py:421: Note that yum will try to contact the repo. when it runs most commands, DEBUG util.py:421: so will have to try and fail each time (and thus. yum will be be much DEBUG util.py:421: slower). If it is a very temporary problem though, this is often a nice DEBUG util.py:421: compromise: DEBUG util.py:421: yum-config-manager --save --setopt=updates.skip_if_unavailable=true DEBUG util.py:421: failure: repodata/repomd.xml from updates: [Errno 256] No more mirrors to try. DEBUG util.py:421: http://mirror.math.princeton.edu/pub/fedora/linux/updates/24/x86_64/repodat…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://linux.mirrors.es.net/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.cs.pitt.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirrors.mit.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://ftp.uci.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: https://mirror.chpc.utah.edu/pub/fedora/linux/updates/24/x86_64/repodata/re…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://repo.atlantic.net/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.cs.princeton.edu/pub/mirrors/fedora/linux/updates/24/x86_64/r…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.uoregon.edu/fedora/linux/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.cc.vt.edu/pub/fedora/linux/updates/24/x86_64/repodata/repomd.…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: https://mirrors.kernel.org/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: https://pubmirror2.math.uh.edu/fedora-buffet/fedora/linux/updates/24/x86_64…: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.nexcess.net/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.sjc02.svwh.net/fedora/updates/24/x86_64/repodata/repomd.xml: [Errno -1] repomd.xml does not match metalink for updates DEBUG util.py:421: http://mirror.symnds.com/distributions/fedora/linux/updates/24/x86_64/repod…: [Errno -1] repomd.xml does not -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

4 6

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-934?page=com.atlassian.jira.p… ] Evgheni Dereveanchin reassigned OVIRT-934: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > improve ovirt.org -> www.ovirt.org redirect > ------------------------------------------- > > Key: OVIRT-934 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org > Trying to point the DNS directly at the OpenShift instance hosting the website does not work. > We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Marc Dequènes (Duck) (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-934?page=com.atlassian.jira.p… ] Marc Dequènes (Duck) commented on OVIRT-934: -------------------------------------------- Here is some documentation with RFC numbers: http://cr.yp.to/im/cname.html > improve ovirt.org -> www.ovirt.org redirect > ------------------------------------------- > > Key: OVIRT-934 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org > Trying to point the DNS directly at the OpenShift instance hosting the website does not work. > We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Marc Dequènes (Duck) (oVirt JIRA) 12 Dec '16

12 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-934?page=com.atlassian.jira.p… ] Marc Dequènes (Duck) commented on OVIRT-934: -------------------------------------------- My original comment by mail follows: I would rather let it like this because: www.ovirt.org is an alias for beta-ovirtweb.rhcloud.com. beta-ovirtweb.rhcloud.com is an alias for ex-std-node798.prod.rhcloud.com. ex-std-node798.prod.rhcloud.com is an alias for ec2-52-23-162-8.compute-1.amazonaws.com. ec2-52-23-162-8.compute-1.amazonaws.com has address 52.23.162.8 So I don't think we can count on the node to never change, and that's the magic of the cloud in fact. We cannot have a CNAME for the domain, only a A record, so a permanent _redirect_ is fine I think. > improve ovirt.org -> www.ovirt.org redirect > ------------------------------------------- > > Key: OVIRT-934 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: Low > > Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org > Trying to point the DNS directly at the OpenShift instance hosting the website does not work. > We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[ANN] oVirt 4.0.6 Fourth Release Candidate is now available
by Sandro Bonazzola 12 Dec '16

12 Dec '16

The oVirt Project is pleased to announce the availability of oVirt 4.0.6 fourth release candidate for testing, as of December 12th, 2016. This release is available now for: * Fedora 23 (tech preview) * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later This release supports Hypervisor Hosts running: * Red Hat Enterprise Linux 7.3 or later * CentOS Linux (or similar) 7.3 or later * Fedora 23 (tech preview) * oVirt Next Generation Node 4.0 This is pre-release software. Please take a look at our community page[1] to know how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This pre-release should not to be used in production. This update is the fourth release candidate of the sixth in a series of stabilization updates to the 4.0 series. 4.0.6 brings 4 enhancements and 61 bugfixes, including 25 high or urgent severity fixes, on top of oVirt 4.0 series See the release notes [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: * A new oVirt Live ISO will be available soon. [4] * A new oVirt Next Generation Node will be available soon [4] * A new oVirt Engine Appliance will be available soon for Red Hat Enterprise Linux and CentOS Linux (or similar) * Mirrors[5] might need up to one day to synchronize. Delay is due to the rolling out of CentOS 7.3 today causing several issues while building Live, Node and Appliance. They should be ready by tomorrow. Additional Resources: * Read more about the oVirt 4.0.6 release highlights: http://www.ovirt.org/release/4.0.6/ * Get more oVirt Project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.0.6/ [4] http://resources.ovirt.org/pub/ovirt-4.0-pre/iso/ [5] http://www.ovirt.org/Repository_mirrors#Current_mirrors -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

[JIRA] (OVIRT-934) improve ovirt.org -> www.ovirt.org redirect
by Evgheni Dereveanchin (oVirt JIRA) 12 Dec '16

12 Dec '16

Evgheni Dereveanchin created OVIRT-934: ------------------------------------------ Summary: improve ovirt.org -> www.ovirt.org redirect Key: OVIRT-934 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-934 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low Currently http://ovirt.org points at a server that redirects users to https://www.ovirt.org Trying to point the DNS directly at the OpenShift instance hosting the website does not work. We need to fix this in order to avoid the intermediary redirect server. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

CentOS 7.3 is coming - and o-s-t's reposync needs updates
by Yaniv Kaul 12 Dec '16

12 Dec '16

I suspect that now that CentOS 7.3 is coming, suddenly packages that we thought are only in updates are in the base channel - which we were not fetching them from. Two examples I'm seeing (and I've fixed manually) are libxml2-python and libxml2. I'll continue chasing it down. Y.

3 6

Why experimental is failing
by Eyal Edri 12 Dec '16

12 Dec '16

Looks like the issue is in the following code: # disable any other repos to avoid downloading metadata yum install --disablerepo=\* --enablerepo=alocalsync -y yum-utils yum-config-manager --disable \* yum-config-manager --enable alocalsync in ost common/deploy-scripts/add_local_repo.sh Might be happening due to new yum available now from CentoOS 7.3... Do we really need to disable all repos when installing yum-utils? ---------- Forwarded message ---------- From: <jenkins(a)jenkins.phx.ovirt.org> Date: Mon, Dec 12, 2016 at 12:39 PM Subject: [oVirt Jenkins] test-repo_ovirt_experimental_4.0 - Build #3547 - FAILURE! To: infra(a)ovirt.org Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/3547/, Build Number: 3547, Build Status: FAILURE _______________________________________________ Infra mailing list Infra(a)ovirt.org http://lists.phx.ovirt.org/mailman/listinfo/infra -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

3 3