Sadly, this is already my second attempt on a "clean" build. I have made more progress. I altered my ceph repo to include the repos documented for a manual rpm build. Ceph-deploy now finds the ceph package, but then got a number of yum dependency errors (mostly python related). I sorted those out, and then tried the ceph-deploy from the admin node again. It failed trying to get the python-argparse package from the ceph repo (timed out). I then went back to the node and ran the Ceph install from there. This time it worked without timing out with the argparse package. I suppose this could be proxy related again. Baby steps.... Now to do it all again on the second node. -----Original Message----- From: Alfredo Deza [mailto:alfredo.deza@xxxxxxxxxxx] Sent: Monday, October 28, 2013 1:32 PM To: Whittle, Alistair: Investment Bank (LDN) Cc: ceph-users@xxxxxxxxxxxxxx Subject: Re: Ceph-deploy, sudo and proxies On Mon, Oct 28, 2013 at 8:37 AM, <alistair.whittle@xxxxxxxxxxxx> wrote: > Yum tells me I have the following installed on the node: > > ceph-deploy.noarch : Admin and deploy tool for Ceph > ceph-release.noarch : Ceph repository configuration > > I think this means ceph is NOT already installed. Interesting that ceph-deploy is on the node as well. I only installed it on the admin node. I assume this was done as an earlier step in the install process? I believe that ceph-deploy comes with the installation process, yes. Can you make sure that your repos have not been altered by ceph-deploy from the previous runs? At this point it looks like there has been a bunch of back and forth to attempt an install and that is causing the odd behavior. Even better would be to try this on a new/clean host and see what errors (if any) come up. > > > -----Original Message----- > From: Alfredo Deza [mailto:alfredo.deza@xxxxxxxxxxx] > Sent: Monday, October 28, 2013 12:29 PM > To: Whittle, Alistair: Investment Bank (LDN) > Cc: ceph-users@xxxxxxxxxxxxxx > Subject: Re: Ceph-deploy, sudo and proxies > > On Mon, Oct 28, 2013 at 8:26 AM, <alistair.whittle@xxxxxxxxxxxx> wrote: >> >> >> I get "Error: Nothing to do" when doing this on the node itself with sudo. > > That may mean that it is already installed. Can you check if ceph is installed and that you can move forward with the rest of the process? > > In this case, ceph-deploy would be OK to raise an error because YUM complained with a non-zero exit status. > >> >> >> -----Original Message----- >> From: Alfredo Deza [mailto:alfredo.deza@xxxxxxxxxxx] >> Sent: Monday, October 28, 2013 12:12 PM >> To: Whittle, Alistair: Investment Bank (LDN) >> Cc: ceph-users@xxxxxxxxxxxxxx >> Subject: Re: Ceph-deploy, sudo and proxies >> >> On Mon, Oct 28, 2013 at 7:33 AM, <alistair.whittle@xxxxxxxxxxxx> wrote: >>> >>> Thanks, I already had the correct ceph-deply version, but had the flag in the wrong place. >>> Solving that got me to the next problem... I get the following error: >>> >>> [ceph_deploy.cli][INFO ] Invoked (1.2.7): /usr/bin/ceph-deploy >>> install ldtdsr02se18 --no-adjust-repos [ceph_deploy.install][DEBUG ] >>> Installing stable version dumpling on cluster ceph hosts ldtdsr02se18 [ceph_deploy.install][DEBUG ] Detecting platform for host ldtdsr02se18 ... >>> [ceph_deploy.sudo_pushy][DEBUG ] will use a remote connection with >>> sudo [ceph_deploy.install][INFO ] Distro info: >>> RedHatEnterpriseServer >>> 6.4 Santiago [ldtdsr02se18][INFO ] installing ceph on ldtdsr02se18 >>> [ldtdsr02se18][INFO ] Running command: yum -y -q install ceph >>> [ldtdsr02se18][ERROR ] Traceback (most recent call last): >>> [ldtdsr02se18][ERROR ] File "/usr/lib/python2.6/site-packages/ceph_deploy/hosts/centos/install.py", line 57, in install >>> [ldtdsr02se18][ERROR ] File "/usr/lib/python2.6/site-packages/ceph_deploy/util/decorators.py", line 10, in inner >>> [ldtdsr02se18][ERROR ] File "/usr/lib/python2.6/site-packages/ceph_deploy/util/wrappers.py", line 6, in remote_call >>> [ldtdsr02se18][ERROR ] File "/usr/lib64/python2.6/subprocess.py", line 502, in check_call >>> [ldtdsr02se18][ERROR ] raise CalledProcessError(retcode, cmd) >>> [ldtdsr02se18][ERROR ] CalledProcessError: Command '['yum', '-y', >>> '-q', 'install', 'ceph']' returned non-zero exit status 1 >>> [ldtdsr02se18][ERROR ] Error: Nothing to do [ceph_deploy][ERROR ] >>> RuntimeError: Failed to execute command: yum -y -q install ceph >>> >>> My ceph repo is pointing to http://ceph.com/rpm-dumpling/rhel6/noarch as per the documentation. Is this correct, or have I missed something else? >> >> That seems correct to me. When you try `yum -y -q install ceph` on that node, all is OK? Have you tried that? >> >> >>> >>> >>> -----Original Message----- >>> From: Alfredo Deza [mailto:alfredo.deza@xxxxxxxxxxx] >>> Sent: Friday, October 25, 2013 6:53 PM >>> To: Whittle, Alistair: Investment Bank (LDN) >>> Cc: ceph-users@xxxxxxxxxxxxxx >>> Subject: Re: Ceph-deploy, sudo and proxies >>> >>> On Fri, Oct 25, 2013 at 1:25 PM, <alistair.whittle@xxxxxxxxxxxx> wrote: >>>> I have an interesting problem I was hoping someone could help with. >>>> >>>> >>>> >>>> My Red Hat servers are configured to use proxies to access the internet. I >>>> have managed to successfully add the Ceph repo install ceph-deploy on the >>>> admin node and create the cluster. All ceph nodes are no password sudo >>>> tested and I have made sure that the proxy settings are kept when >>>> trying an 'rpm' command using sudo. All other preflight checks are >>>> completed with ceph being the default login user etc. >>>> >>>> >>>> >>>> So, when I run the ceph-deploy install <ceph-node> command from the >>>> admin node, I get the following error: >>>> >>>> >>>> >>>> ceph@ldtdsr02se17 PROD $ ceph-deploy install ldtdsr02se18 >>>> >>>> [ceph_deploy.cli][INFO ] Invoked (1.2.7): /usr/bin/ceph-deploy >>>> install >>>> ldtdsr02se18 >>>> >>>> [ceph_deploy.install][DEBUG ] Installing stable version dumpling on >>>> cluster ceph hosts ldtdsr02se18 >>>> >>>> [ceph_deploy.install][DEBUG ] Detecting platform for host ldtdsr02se18 ... >>>> >>>> [ceph_deploy.sudo_pushy][DEBUG ] will use a remote connection with >>>> sudo >>>> >>>> [ceph_deploy.install][INFO ] Distro info: RedHatEnterpriseServer >>>> 6.4 Santiago >>>> >>>> [ldtdsr02se18][INFO ] installing ceph on ldtdsr02se18 >>>> >>>> [ldtdsr02se18][INFO ] Running command: su -c 'rpm --import >>>> "https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc";' >>>> >>>> [ldtdsr02se18][ERROR ] Traceback (most recent call last): >>>> >>>> [ldtdsr02se18][ERROR ] File >>>> "/usr/lib/python2.6/site-packages/ceph_deploy/hosts/centos/install.py" >>>> , line 23, in install >>>> >>>> [ldtdsr02se18][ERROR ] File >>>> "/usr/lib/python2.6/site-packages/ceph_deploy/util/decorators.py", >>>> line 10, in inner >>>> >>>> [ldtdsr02se18][ERROR ] File >>>> "/usr/lib/python2.6/site-packages/ceph_deploy/util/wrappers.py", >>>> line 6, in remote_call >>>> >>>> [ldtdsr02se18][ERROR ] File "/usr/lib64/python2.6/subprocess.py", line >>>> 502, in check_call >>>> >>>> [ldtdsr02se18][ERROR ] raise CalledProcessError(retcode, cmd) >>>> >>>> [ldtdsr02se18][ERROR ] CalledProcessError: Command '['su -c \'rpm >>>> --import "https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc"\'']' >>>> returned non-zero exit status 1 >>>> >>>> [ldtdsr02se18][ERROR ] curl: (7) couldn't connect to host >>>> >>>> [ldtdsr02se18][ERROR ] error: >>>> https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc: >>>> import read failed(2). >>>> >>>> [ceph_deploy][ERROR ] RuntimeError: Failed to execute command: su >>>> -c 'rpm --import "https://ceph.com/git/?p=ceph.git;a=blob_plain;f=keys/release.asc";' >>>> >>>> >>>> >>>> Note that it uses sudo as it should and then complains about not being able >>>> to connect. When I run the exact same command on the ceph node itself as >>>> the "ceph" user, it works without any errors. This implies that the >>>> authentication is in place between ceph and root, and the proxy settings are >>>> correct. Yet, it fails to work when initiated from the admin node via >>>> ceph-deploy. >>>> >>>> >>>> >>>> Any ideas what might be going on here? I should add that I looked at the >>>> github page about using the "-no-adjust-repos" flag but my version >>>> of ceph-deploy says it is an invalid flag... >>> >>> You should make sure you are running the latest version for ceph-deploy (1.2.7 at the moment). >>> >>> But this is a known issue, and it basically happens with proxies because environment variables get reset on sudo (common on a lot of distros for security concerns). >>> >>> What is set for a user when it is logged in via SSH will not have a >>> 1:1 behavior when done in a non-interactive shell which is what ceph-deploy does. >>> >>> My first recommendation is to use the latest ceph-deploy and the `--no-adjust-repos` flag. We do have a couple of open tickets to address the need for a proxy flag so that ceph-deploy in turn can use those values whenever a wget or curl is about to be used. >>> >>> >>>> >>>> >>>> >>>> Please help >>>> >>>> Alistair >>>> >>>> >>>> >>>> _______________________________________________ >>>> >>>> This message is for information purposes only, it is not a >>>> recommendation, advice, offer or solicitation to buy or sell a >>>> product or service nor an official confirmation of any transaction. >>>> It is directed at persons who are professionals and is not intended >>>> for retail customer use. Intended for recipient only. This message is subject to the terms at: >>>> www.barclays.com/emaildisclaimer. >>>> >>>> For important disclosures, please see: >>>> www.barclays.com/salesandtradingdisclaimer regarding market >>>> commentary from Barclays Sales and/or Trading, who are active >>>> market participants; and in respect of Barclays Research, including >>>> disclosures relating to specific issuers, please see http://publicresearch.barclays.com. >>>> >>>> _______________________________________________ >>>> >>>> >>>> _______________________________________________ >>>> ceph-users mailing list >>>> ceph-users@xxxxxxxxxxxxxx >>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >>>> >>> _______________________________________________ >>> >>> This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. >>> >>> For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. >>> >>> _______________________________________________ >>> _______________________________________________ >>> ceph-users mailing list >>> ceph-users@xxxxxxxxxxxxxx >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com >> _______________________________________________ >> >> This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. >> >> For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. >> >> _______________________________________________ > _______________________________________________ > > This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. > > For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. > > _______________________________________________ _______________________________________________ This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer. For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com. _______________________________________________ _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |