devel

devel@lists.centos.org

3 participants
4682 discussions

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

Reboot issue with kernel 3.10.0-862.el7.x86_64
by Lamar Owen 02 May '18

02 May '18

Ok, so I'm trying out CR for 7.5.1804, and I have upgrade three machines with it. One is my laptop, a Dell Precision M6700, which worked fine. Another is a Dell R715 server, and that worked fine. The third machine will not successfully reboot with the 3.10.0-862.el7.x86_64 kernel, throwing endless errors of the form "qla2xxx [0000:03:07.0]-5046:4: Async-gpdb failed - hdX-xxx portid=xxxxxx status=38 mb1=0 mb2=0 mb6=0 mb7" (that's as long as the line is on the screen, and it's not recorded into /var/log/messages (and C7 by default doesn't implement persistent journal storage; journalctl --list-boots only lists the current boot log)). System is a bit old, but is only used for development: Dell PowerEdge SC1425 two single-core Xeon 3.2GHz (obviously 64-bit capable, as it is running stock CentOS 7 already, with kernel 3.10.0-693.21.1.el7.x86_64 running fine. System is connected to two EMC Clariion arrays via a dual-port Fibre-Channel card: lspci tells me: 03:07.0 Fibre Channel: QLogic Corp. ISP2312-based 2Gb Fibre Channel to PCI-X HBA (rev 02) 03:07.1 Fibre Channel: QLogic Corp. ISP2312-based 2Gb Fibre Channel to PCI-X HBA (rev 02) Yeah, I know, not new, and maybe even deprecated (I actually don't see that adapter in the deprecated list for RHEL 7.5, but I do see ISP24xx ones in the deprecated list), but it worked fine with the 7.4.1708 kernel. I set the system to boot the older kernel until I can more fully troubleshoot. I have a lot invested in ISP24xx-based cards, which are on the deprecated list, and I am still running fibre-channel, so will have to find another solution before 7.x EOL. So I consider this a regression; for the moment I'll boot the older kernel, but I know that isn't sustainable.

3 5

CentOS 7.4.1708 CR new udisks2 package conflicts with extras storaged package
by Jean-Marc Liger 02 May '18

02 May '18

Hi Folks, There are some missing Provides in new udisks2 package, but as it comes from uptream, it seems that cockpit extras package shall be rebuild. Erreur : Paquet : cockpit-storaged-160-1.el7.centos.noarch (@extras) Requiert : storaged >= 2.1.1 Suppression : storaged-2.5.2-4.el7.x86_64 (@extras) storaged = 2.5.2-4.el7 Rendu obsolète par : udisks2-2.7.3-6.el7.x86_64 (cr) Non trouvé Erreur : Paquet : cockpit-storaged-160-1.el7.centos.noarch (@extras) Requiert : storaged-lvm2 >= 2.1.1 Suppression : storaged-lvm2-2.5.2-4.el7.x86_64 (@extras) storaged-lvm2 = 2.5.2-4.el7 Rendu obsolète par : udisks2-lvm2-2.7.3-6.el7.x86_64 (cr) Non trouvé Erreur : Paquet : cockpit-storaged-160-1.el7.centos.noarch (@extras) Requiert : storaged-iscsi >= 2.1.1 Suppression : storaged-iscsi-2.5.2-4.el7.x86_64 (@extras) storaged-iscsi = 2.5.2-4.el7 Rendu obsolète par : udisks2-iscsi-2.7.3-6.el7.x86_64 (cr) Non trouvé -- *Jean-Marc LIGER Ingénieur Systèmes et Réseaux de Communication * FACULTÉ DE MÉDECINE Direction Technique, Informatique, Réseaux et Multimédia 15 rue de l’École de Médecine – 75270 Paris cedex 06 Tél : +33 (0)1 76 53 00 71

3 3

[Cloud SIG] OpenStack Rocky milestone 1 test day, May 3, 4
by Rich Bowen 02 May '18

02 May '18

Please join the RDO community on May 3rd and 4th (tomorrow and Friday) as we test the first milestone in the Rocky series. We'll have a cloud environment already spun up, so that you can even come help test if you lack the hardware, time, or expertise to spin it up yourself, but still want to poke at it. The full details of the event may be found here: https://bit.ly/2w5Idkt -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

when the fix for CVE-2018-2794 & CVE-2018-2814 would be available in OpenJDK 1.7?
by Maheshwari, Shagun 02 May '18

02 May '18

Hi All, We are currently on OpenJDK 1.7.0_161 and OpenJDK 1.7.0_161 is impacted by CVE-2018-2794 & CVE-2018-2814 It seems we do NOT have an ETA for the fix. I could see RH already posted a fix for OpenJDK 1.8 here - https://clicktime.symantec.com/a/1/OXdEaLeTBZV355U3VoZGXHSsHP8TO8kMoHYzvixK… Can you please find out when the fix for OpenJDK 1.7 would be available ? If this is getting delayed, can you help to back port this fix ? Regards, Shagun

2 1

SIG meeting times
by Rich Bowen 01 May '18

01 May '18

I noticed this afternoon that the .ics file linked from https://www.centos.org/community/calendar/ was AWOL, and I've replaced it with one that agrees with all of the times on that page. I suspect, however, that that page is incomplete and/or out of date. If you are responsible for a SIG's meeting schedule, please have a look at that page, and let me know if any updates. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen

1 0

CentOS 7.4.1708 CR Available in CBS
by Brian Stinson 27 Apr '18

27 Apr '18

Hi Folks, The CR (https://wiki.centos.org/AdditionalResources/Repositories/CR) repository was released earlier today. We have regenerated all the CentOS 7 buildroots in CBS so you can build against the content that will make it into the next point-release of CentOS Linux. Machines in ci.centos.org are available with CR as well so you may continue your testing. As we discussed earlier (https://lists.centos.org/pipermail/centos-devel/2018-April/016627.html) we are currently in Point-release Freeze which means anything tagged for release will *NOT* get pushed out to mirror.centos.org and we will be holding new push requests until we have a GA point-release. If there are any questions please find us here or in #centos-devel on Freenode. Cheers! -- Brian Stinson

3 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel