devel

devel@lists.centos.org

2 participants
4591 discussions

Re: [CentOS-devel] Problem with $contentdir in centos qemu-ev release repos
by Sandro Bonazzola 14 May '18

14 May '18

Adding CentOS Devel mailing list 2018-05-14 12:17 GMT+02:00 Sagi Shnaidman <sshnaidm(a)redhat.com>: > Hi, Sandro > > we have problems recently with having $contentdir in new qemu-ev repo > release[1], because it's not set anywhere. It's not an exaggeration to say > that it's blocking the whole TripleO CI in Openstack and anything else that > uses CentOS 7.5 in Openstack[2]. > > Can you please fix this problem in the package? > The problem is not in the package. On a centos instance installed with anaconda the $contendir variable is filled by /etc/yum/vars/contentdir which is supposed to be installed by centos-release rpm. The introduction of this variable has been proposed in https://lists.centos.org/pipermail/centos-devel/2018-March/016542.html and has been implemented in CentOS 7.5 GA. Looking at it, deeper I see: # LC_ALL=C rpm -qf /etc/yum/vars/contentdir file /etc/yum/vars/contentdir is not owned by any package Seems like centos-release rpm has a packaging issue. A bug has been opened on https://bugs.centos.org/view.php?id=14786 which identified the bug happening in OpenStack CI as a bug in diskimage-builder. That said, I think centos-release-qemu-ev-1.0-3 is doing the right thing there. > Thanks > > [1] http://cbs.centos.org/koji/packageinfo?packageID=1950 > [2] https://bugs.launchpad.net/tripleo/+bug/1771090 - > http://mirror.centos.org/%24contentdir/7/virt/x86_64/kvm-common/repodata/re…: > [Errno 14] HTTP Error 404 - Not Found > > -- > Best regards > Sagi Shnaidman > -- 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> <https://redhat.com/summit>

1 0

URLs in centos-release-<sig> packages: /altarch vs. /centos/
by Brian Stinson 13 May '18

13 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folks, Now that we have SIG Content in the /altarch directories for CentOS 7 on the mirrors, we need to come with some requirements and recommendations for dealing with the different locations. tl;dr The current thinking is to add the following snippet in the %post of centos-release and release to all of the arches. This will set a yum var to the correct content location when a new system gets installed: `uname -m | grep -q 'x86_64' && echo 'centos' >/etc/yum/vars/contentdir || echo 'altarch' >/etc/yum/vars/contentdir` Here's the start of a proposal from the SIG perspective ## Requirements: - - The same noarch binary RPM *must* be distributable to the Extras repo for each architecture - - The centos-release-<SIG> packages *must* require centos-release ## New Recommendations for creating a centos-release file: - - A yum variable called 'contentdir' will be populated with the toplevel directory for SIGs to use 1.) Modify baseurls in the SIG repo files to look like the following (using openstack-queens as an example): [centos-openstack-queens] name=CentOS-7 - OpenStack queens baseurl=https://mirror.centos.org/$contentdir/cloud/$basearch/openstack-que… gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-SIG-Cloud exclude=sip,PyQt4 ## Discussion I'd like to hear thoughts, additions, and subtractions here before we update the SIGGuide and rework centos-release. Cheers! - -- Brian Stinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJanjEMAAoJEIMGvNKzCweMR6oQAMbsKqvJcfKW1+5yHsbEV33d QAAMwjEcKfZ+v9ypejErbPPh5RhuNCoRFFHUDAn4hBJNo2zb0YC0vKZJF3RIPIkV 9GAOwnnrWIvFJbeZ7sY4POMa/50IJXC3N8CeiW2XonDtf58rXZPsXM9/9JN9xCv7 X39FAIufCYA7rmedta236NMAutiEolyDFKWWJN6kwDzhm4p7BT9UVSyf7sWCBDzx t+TuCo7LZei4iwQWho1YL/9jbm0YP6EEyL3jJ/YT68cE8q9Mqd8qiE0gEMy0Eoof FuGNOLMrFhsvg3jNQr5DkbToDU+VwO3B+YVR29pTrd0Gf8bodmGTH31eCEljlhjg uPlms2cDvkaXlJmjO6XHM0D2cxmlTzBfVG7YrRwlD40JSk1Z3iyPyLkWJ967oyVM 9mmkhv4spNCX4okQlNI737bULwcxILM6ks3oCdO4i4Yk8BbZp/iwrJ9jcxr7U5YT Cvq2SuV5EbcXlxnhmMd/V6+F/VkgKqi0xrltKURlVUk+JzabHTw5zGwcRjnHxUQR nz2YiQ0mdR/pPuGyXl6xOqXl+M6khPBdCk4FHHdrZYw6aijo8FHzR1DYc63m4ibf Pkad1V9Awetuz0YwewgTp3MviRlklQte8jXMV/1Nh0TTp8xIs5e4ISNBwD3EtINL oqQYqpSGC0jkrwXD5fRG =F1Fp -----END PGP SIGNATURE-----

7 14

CentOS wiki - QA related data/activities
by Phil Wyett 13 May '18

13 May '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Trying to lookup QA related team, data and general info. Issues: * Not allowed to view below page, even if logged in. https://wiki.centos.org/QaTeam * Page below mentions QA mailing list. https://wiki.centos.org/FAQ/General/RebuildReleaseProcess No QA list though on page below. https://lists.centos.org/mailman/listinfo/ * QaWiki section linked below is very out of date. Is it and the team active? https://wiki.centos.org/QaWiki Can anyone offer detail into QA related activities? Regards Phil - -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. IRC: kathenas Web: https://kathenas.org Github: https://github.com/kathenas GitLab: https://gitlab.com/kathenas Twitter: kathenasorg GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJa+HH5AAoJEDM/YNywubt3CxcQANobpP0LSeJyF8/WkYSzIqyA HuZaRIHArooc/3vs4tcLRCbrMU/eLUkABwsa4ND93kycmkwIofdc8BHUM2YeeuOB ScswCvKneoaa30T3O032TEIsaPRfAqXh8L8HP95ffa2SPuqAL7S7KaJwf+Q536h4 QUJ4yU24d47ii030IXhGFiILN2cIRxRgcjn9I23VejiJgwnxCv80BiW0mUpJNqeG RvoRya52i6JooQkNHs37U1vcG6aoCjBwM2VJBtQc27+pgt/h5R8gFD6ZEqqse4ve JujX7l5VO8/SI+A4QVV6v6NVj1XS7t4kUBzSdmskjScCq6oz8SJ0Fly2pac19GFN fidtFl0yp9kiqq6vWyJvHd4Q6exxkzsdhM5Mibbs/mnHl7tL4ou/jdlrlUmRLZ2x VfMKP+Nlj8XYLGPUflC6YGSeYPreGLDtfd4N//RtiiFjY4OcT5g7pJWmGWCg0MK/ uy93k/aypcJsC20NyuBEXIYTrMFcRujMwH+8E76JPlj/Vc6RVQUeTvrPV+qmxcFB fJ+q32sWTo6H4dWhz1cGmyjTWgvwE9lWn1T+M1uuK+6n5VHCwMvqb02zgH2S/wai zj4hABoMgIdnLadWWzdIY7l+xfrg6+Xyn1YFOG5IN+2XVE5V6WmgIz9X2qS/2prI Et4qloIslyoJGILwP4zx =OkHY -----END PGP SIGNATURE-----

1 0

Broken requirements for cockpit
by James Hogarth 12 May '18

12 May '18

Hi guys, Trying to install cockpit-storaged and getting the following error: --> Processing Dependency: storaged-lvm2 >= 2.1.1 for package: cockpit-storaged-160-1.el7.centos.noarch Package storaged-lvm2 is obsoleted by udisks2-lvm2, but obsoleting package does not provide for requirements --> Processing Dependency: storaged-iscsi >= 2.1.1 for package: cockpit-storaged-160-1.el7.centos.noarch Package storaged-iscsi is obsoleted by udisks2-iscsi, but obsoleting package does not provide for requirements --> Processing Dependency: storaged >= 2.1.1 for package: cockpit-storaged-160-1.el7.centos.noarch Package storaged is obsoleted by udisks2, but obsoleting package does not provide for requirements ---> Package libnetfilter_conntrack.x86_64 0:1.0.6-1.el7_3 will be installed ---> Package libnfnetlink.x86_64 0:1.0.1-4.el7 will be installed ---> Package libsemanage.x86_64 0:2.5-8.el7 will be updated ---> Package libsemanage.x86_64 0:2.5-11.el7 will be an update --> Processing Conflict: initscripts-9.49.41-1.el7.x86_64 conflicts redhat-release < 7.5-0.11 --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package centos-release.x86_64 0:7-4.1708.el7.centos will be updated ---> Package centos-release.x86_64 0:7-5.1804.el7.centos will be an update ---> Package cockpit-storaged.noarch 0:160-1.el7.centos will be installed --> Processing Dependency: storaged-lvm2 >= 2.1.1 for package: cockpit-storaged-160-1.el7.centos.noarch Package storaged-lvm2 is obsoleted by udisks2-lvm2, but obsoleting package does not provide for requirements --> Processing Dependency: storaged-iscsi >= 2.1.1 for package: cockpit-storaged-160-1.el7.centos.noarch Package storaged-iscsi is obsoleted by udisks2-iscsi, but obsoleting package does not provide for requirements --> Processing Dependency: storaged >= 2.1.1 for package: cockpit-storaged-160-1.el7.centos.noarch Package storaged is obsoleted by udisks2, but obsoleting package does not provide for requirements --> Finished Dependency Resolution Error: Package: cockpit-storaged-160-1.el7.centos.noarch (extras) Requires: storaged-lvm2 >= 2.1.1 Available: storaged-lvm2-2.5.2-4.el7.x86_64 (extras) storaged-lvm2 = 2.5.2-4.el7 Error: Package: cockpit-storaged-160-1.el7.centos.noarch (extras) Requires: storaged >= 2.1.1 Available: storaged-2.5.2-4.el7.x86_64 (extras) storaged = 2.5.2-4.el7 Error: Package: cockpit-storaged-160-1.el7.centos.noarch (extras) Requires: storaged-iscsi >= 2.1.1 Available: storaged-iscsi-2.5.2-4.el7.x86_64 (extras) storaged-iscsi = 2.5.2-4.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest This is the same with or without CR Did something get a bit broken in rebuilding? On RHEL7 this installs fine. James

4 5

centos 7.5 src.rpm missing
by Farkas Levente 12 May '18

12 May '18

hi, it seems the src.rpms are missing from: http://vault.centos.org/7.5.1804/os/Source/SPackages/ on the other hand 7.5 missing from the centos git too. eg. tha last commit to the centos-release rpm is from 2017 januar: https://git.centos.org/summary/rpms!centos-release.git is there any place where we can found the source of centos? regards. -- Levente "Si vis pacem para bellum!"

3 3

Custom ISO is giving error during installation
by Veetil, Vyshnav 10 May '18

10 May '18

Hi, I created a new ISO and try to install on my box but it failed. ISO has 1744 RPMs. I saw it installed 1700+ packages and then enter this screen as attached screenshot. It seems to complain about not enough space. if you suggest me try something, please do. Regards, Vyshnav

3 2

LinchPin v1.5.3 (update) has been released
by Clint Savage 07 May '18

07 May '18

We are happy to announce that LinchPin v1.5.3 has been released. This release has the following updates: This release marks some useful enhancements and features: - Add support for passing instance_tags for aws driver. (#541 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/541>) - Add name in topology for bkr_server, os_server, aws_ec2 resources, include in distilled data (#550 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/550>) - Add auto_ip option to os_server resources (#552 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/552>) - Add security_group as a list to aws_ec2 resources (#557 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/557>) Additional bugs were also fixed along the way: - linchpin up AWS target fails when using CREDS_PATH (#497 <https://github.com/CentOS-PaaS-SIG/linchpin/issues/497>) - use match instead of equalto for rhel7/centos7 (#537 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/537>) - Fix TypeError when missing template-data (#539 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/539>) - Fixup reporting issues, other minor fixes (#565 <https://github.com/CentOS-PaaS-SIG/linchpin/pull/565>) - removed errant if/else which was providing incorrect return code output to the user - Add no_log in a few places which would display sensitive data - Moved the code for distilling data into a distill_data method Documentation was updated as well: - Updated credentials format for all providers (514) - Documented the Context Distiller (#523 <https://github.com/CentOS-PaaS-SIG/linchpin/issues/523>) - Documented what is required for each provider topology (#487 <https://github.com/CentOS-PaaS-SIG/linchpin/issues/487>) The official release notes are available at https://github.com/CentOS-PaaS -SIG/linchpin/releases/tag/v1.5.3 This update is available via PyPI: https://pypi.org/project/linchpin/ If you discover any errors or regressions, please open a Github issue ( https://github.com/CentOS-PaaS-SIG/linchpin/issues). Cheers, Clint Savage LinchPin Maintainer Senior Software Engineer, Red Hat twitter: @herlo, github: herlo, IRC: herlo, #linchpin (freenode)

1 0

CentOS DevCloud environment down
by Fabian Arrotin 05 May '18

05 May '18

We have a major service disruption with our DevCloud RDO environment (https://wiki.centos.org/DevCloud) right now so it's currently unusable. The underlying storage node (over infiniband) used by the openstack compute nodes is actually powered off, and in unusable state. At first sight, after a small discussion with DC people, it seems that it needs vendor support, so unfortunately that will take time (probably some days) to get resolved. We'll notify this list (for people using it for testing purposes) and also we'll reflect that status on https://status.centos.org when service will be fully restored Thanks for your comprehending. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 1

Re: [CentOS-devel] [Cloud SIG] RDO Rocky Test Days Milestone ONE
by Rain Leander 04 May '18

04 May '18

Can't wait to see everyone on #rdo TOMORROW! Thanks, in advance, for your help!! ! On Tue, Apr 24, 2018 at 11:21 AM, Rain Leander <rleander(a)redhat.com> wrote: > Hello everyone! > > Bust out your spoons because we're about to test the first batch of Rocky > [road] ice cream! > > Or, y'know, the first Rocky OpenStack milestone. > > On 03 and 04 May, next week Thursday and Friday, we'll have our first > milestone test days for Rocky OpenStack. We would love to get as wide > participation in the RDO Test Days from our global team as possible! > > We're looking for developers, users, operators, quality engineers, > writers, and, yes, YOU. If you're reading this, we want your help! > > Let's set new records on the amount of participants! The amount of > tickets! The amount of feedback and questions and NOTES! > > Oh, my. > > But, seriously. > > I know that everyone has Important Stuff To Do but taking a few hours or a > day to give things a run through at various points in the RDO cycle will > benefit everyone. Not only will this help identify issues early in the > development process, but you can be the one of the first to cut your teeth > on the latest versions of your favorite deployment methods like TripleO, > PackStack, and Kolla. > > So, please consider taking a break from your normal duties and spending at > least a few hours with us in #rdo on Freenode. > > See you NEXT WEEK! > -- > K Rain Leander > OpenStack Community Liaison > Open Source and Standards Team > https://www.rdoproject.org/ > http://community.redhat.com > -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

1 2

[Artwork] Is the Artwork SIG alive?
by Rich Bowen 03 May '18

03 May '18

I've been working through the various SIGs, trying to determine which ones are active. I'm curious about the state of the Artwork SIG. https://wiki.centos.org/SpecialInterestGroup/Artwork Is this still an ongoing effort, or is it "done"? -- Rich Bowen - rbowen(a)redhat.com @RDOcommunity // @CentOSProject // @rbowen

4 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel