devel

devel@lists.centos.org

4 participants
4592 discussions

Ceph/Storage SIG
by Haïkel 12 Jan '16

12 Jan '16

Hi, In order to be truly independent from EPEL, the Cloud SIG/OpenStack is looking to consume Ceph from Storage SIG repo. Seems that the only builds are from oVirt and testing build targets, so I'd like to confirm what are the plans to deliver Ceph if there are any? Regards,

3 4

Re: [CentOS-devel] [CentOS-announce] Announcing release for MySQL 5.5 and 5.6 on CentOS Linux 6 x86_64 SCL
by Leon Fauster 12 Jan '16

12 Jan '16

Hi Honza, Am 21.12.2015 um 17:20 schrieb Honza Horak <hhorak(a)redhat.com>: > > I am pleased to announce the immediate availability of versions 5.5 and 5.6 of the MySQL on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). > > QuickStart > ---------- > You can get started in three easy steps (example of MySQL 5.6): > $ sudo yum install centos-release-scl > $ sudo yum install rh-mysql56 > $ scl enable rh-mysql56 bash should centos-release-scl not have at least a "Obsoletes: centos-release-SCL" statement? http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-SCL… vs http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-scl… -- LF

4 4

CentOS Upgrade Tool
by Bruno Martins 12 Jan '16

12 Jan '16

Hi everyone, I hope this is the best place to post this question. I was wondering how can one upgrade from CentOS 6.7 to CentOS 7.x using redhat-upgrade-tool-cli in a scenario where you're upgrading an Hyper-V based VM. These are the errors I am getting: [root@apssopenvas /]# /usr/bin/redhat-upgrade-tool-cli --network 7 --instrepo=http://mirror.centos.org/centos/7/os/x86_64 setting up repos... Could not retrieve mirrorlist http://updates.atomicorp.com/channels/mirrorlist/atomic/centos-7.0-x86_64 error was 14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Could not retrieve mirrorlist http://updates.atomicorp.com/channels/mirrorlist/atomic-testing/centos-7.0-… error was 14: PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" YumRepo Error: All mirror URLs are not using ftp, http[s] or file. Eg. 7.0 is not a valid and current release or hasnt been released yet/ removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/base/mirrorlist.txt YumRepo Error: All mirror URLs are not using ftp, http[s] or file. Eg. 7.0 is not a valid and current release or hasnt been released yet/ removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/extras/mirrorlist.txt YumRepo Error: All mirror URLs are not using ftp, http[s] or file. Eg. 7.0 is not a valid and current release or hasnt been released yet/ removing mirrorlist with no valid mirrors: /var/tmp/system-upgrade/updates/mirrorlist.txt No upgrade available for the following repos: atomic atomic-testing base extras updates .treeinfo | 1.1 kB 00:00 preupgrade-assistant risk check found EXTREME risks for this upgrade. Run preupg --riskcheck --verbose to view these risks. Continuing with this upgrade is not recommended. And this is the reason for the risk: [root@apssopenvas /]# preupg --riskcheck --verbose INPLACERISK: EXTREME: This machine seems to run on a Microsoft hypervisor. Thank you! Cheers, Bruno Martins

9 15

RDO (OpenStack) doc day and test day
by Rich Bowen 07 Jan '16

07 Jan '16

With the Mitaka milestone 2 release due very soon [1], the RDO community has two events in the coming days. On January 20th/21st, we'll be focusing on improving the website and documentation, to make it easier for people to get started with OpenStack on CentOS. We'll be gathering on #rdo (on Freenode IRC) for any associated questions/discussion, and working through the open issues list. [2] On January 27th/28th, we'll be running a test day of the Mitaka milestone 2 packages. Details of that test day will be at https://www.rdoproject.org/testday/ in the coming days, along with suggested test scenarios that we'd like to run through. Once again, we'll be gathering on #rdo for this event. We look forward to expanding the audience of these test days, and thereby improve everyone's CentOS OpenStack experience. So please set aside an hour or two to help us test. Thanks. --Rich [1] http://docs.openstack.org/releases/schedules/mitaka.html [2] https://github.com/redhat-openstack/website/issues -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Updated Cloud Image for 7.2
by Neil Wilson 06 Jan '16

06 Jan '16

Hi all, Is there a new CentOS cloud image in the pipeline? The last update seems to be 18 Nov last year. Rgs Neil Wilson

2 3

named service starts before network interfaces?
by Sebastiaan Glazenborg 05 Jan '16

05 Jan '16

Should this be a bug report or is this misconfiguration. At this moment I do not have access to RHEL 7.2 system(s) so are unable to verify if this is true for RHEL systems as well. Named seems to start before network interfaces are up/started and so named does not listen on any configured, in this case, IPv4 addresses. >From /var/log/messages: Jan 5 02:00:29 server1 named[633]: all zones loaded Jan 5 02:00:29 server1 named[633]: running Jan 5 02:00:29 server1 systemd: Started Berkeley Internet Name Domain (DNS). Jan 5 02:00:29 server1 systemd: Reached target Host and Network Name Lookups. Jan 5 02:00:29 server1 systemd: Starting Host and Network Name Lookups. Jan 5 02:00:29 server1 network: Bringing up loopback interface: [ OK ] Jan 5 02:00:31 server1 network: Bringing up interface eth0: [ OK ] netstat -tulpen | grep named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 25 13661 633/named tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25 13667 633/named tcp6 0 0 ::1:53 :::* LISTEN 25 13663 633/named tcp6 0 0 ::1:953 :::* LISTEN 25 13668 633/named udp 0 0 127.0.0.1:53 0.0.0.0:* 25 13660 633/named udp6 0 0 ::1:53 :::* 25 13662 633/named sudo systemctl restart named.service sudo netstat -tulpen | grep named tcp 0 0 192.168.150.2:53 0.0.0.0:* LISTEN 25 15368 955/named tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 25 15366 955/named tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 25 15373 955/named tcp6 0 0 ::1:53 :::* LISTEN 25 15370 955/named tcp6 0 0 ::1:953 :::* LISTEN 25 15374 955/named udp 0 0 192.168.150.2:53 0.0.0.0:* 25 15367 955/named udp 0 0 127.0.0.1:53 0.0.0.0:* 25 15365 955/named udp6 0 0 ::1:53 :::* 25 15369 955/named

1 0

Is which requried for rpm-build?
by Andrew Neff 04 Jan '16

04 Jan '16

I've been using centos dockers for a while to build images. With the latest Centos update 7.2.1511 to the docker images, I am no longer able to build rpm packages without manually installing which. I get an error similar to this rpmbuild -ba /home/dev/rpmbuild/SPECS/re2c.spec sh: which: command not found sh: which: command not found Executing(%prep): -e /var/tmp/rpm-tmp.9WC5EP error: Exec of /var/tmp/rpm-tmp.9WC5EP failed (%prep): No such file or directory error: Bad exit status from /var/tmp/rpm-tmp.9WC5EP (%prep) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.9WC5EP (%prep) No matter how simple my spec is... I can run "sh /var/tmp/rpm-tmp.9WC5EP" without issue. So I'm still not 100% sure where the problem REALLY lies. The only packages I've installed is yum groupinstall "Development Tools" My question is where is the error, and where can I file/view a bug report? Should rpm-build from https://git.centos.org/summary/?r=rpms/rpm have "Requires: which" for the build package? Or is which supposed to be in "Development tools", or am I just doing this all wrong? Thanks

3 2

Make Atomic Host Downloads more Visible
by Brian (bex) Exelbierd 04 Jan '16

04 Jan '16

I believe we should list the Atomic Host downloads more clearly on these pages: https://wiki.centos.org/Download https://www.centos.org/download/ I can make the edits if given permission or I am happy to just see them done. regards, bex

5 5

Greater Visibility for Events
by Brian (bex) Exelbierd 29 Dec '15

29 Dec '15

I believe we should add a link in the Community NavBar on centos.org for https://wiki.centos.org/Events I also believe we should either add confirmed events to the meeting calendar or produce a separate calendar of events CentOS will be represented at. I can do the updates or am happy to let someone else make the changes. regards, bex

1 0

CentOS for ppc64le bare-metal install failed on S822L
by Yan Hui Tan 23 Dec '15

23 Dec '15

Hello, We ran into below error when install CentOS on bare-metal S822L(OPAL firmware), does it now support bare-metal installation? With the same iso we successfully installed it in a PowerKVM guest. 5) Asia Please select the timezone. Use numbers or type names directly [b to region list, q to quit]: 5 ** (anaconda:5706): WARNING **: Could not open X display An unknown error has occured, look at the /tmp/anaconda-tb* file(s) for more details =============================================================================== An unknown error has occurred =============================================================================== anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/formats/fs.py", line 703, in unmount raise FSError("umount failed") File "/usr/lib64/python2.7/site-packages/pyanaconda/image.py", line 215, in opticalInstallMedia dev.format.unmount() File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 980, in _setupInstallDevice self.install_device = opticalInstallMedia(storage.devicetree) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 541, in updateBaseRepo url, mirrorlist, sslverify = self._setupInstallDevice(self.storage, checkmount) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/yumpayload.py", line 145, in inner_method ret = method(yum_payload, *args, **kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/packaging/__init__.py", line 1253, in _runThread payload.updateBaseRepo(fallback=fallback, checkmount=checkmount) File "/usr/lib64/python2.7/threading.py", line 764, in run self.__target(*self.__args, **self.__kwargs) File "/usr/lib64/python2.7/site-packages/pyanaconda/threads.py", line 227, in run threading.Thread.run(self, *args, **kwargs) FSError: umount failed What do you want to do now? 1) Report Bug 2) Debug 3) Quit Best Regards, ========================================== Tan, Yanhui (谭艳辉) Technical Sales Specialist IBM China, Technology Partnership Mobile: 186 0137 8245 E-Mail: yanhuit(a)cn.ibm.com Add: 20/F, Pangu Plaza, No. 27, Central North Fourth Ring Road, Chaoyang District, Beijing,100101,China.

3 8

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