Daniel,
We've poured over your log output, and while there some errors
related to list DB connections, all of those are eventually cleaned
up. Towards the end everything seems to be operating as expected. I'd
like to understand what doesn't work when you say "It failed again."
Would you be able to give us more detail one what makes you say this
please?
Simon
*From:*Daniel San Pedro [mailto:dsanpe...@mcna.net]
*Sent:* Tuesday, October 01, 2013 4:17 PM
*To:* Jakesch, Simon
*Cc:* Jacob, Jacob; crowbar
*Subject:* Re: [Crowbar] mesa-1.6 - cinder barclamp fails when
applying proposal
It failed again. Perhaps I am missing a step or I'm doing them out of
order. This is what I did:
on Controller Node:
1. bluepill chef-client stop
2. mysql -u root -p
3. drop database cinder;
4. drop user cinder@'%';
5. rm /etc/cinder/cinder.conf
Then, on Crowbar admin node:
1. /opt/dell/bin/barclamp_install.rb cinder (it succeeds)
Back on the Controller Node:
1. bluepill chef-client start
On the crowbar web gui:
1. I deactivated the cinder proposal then deleted it
2. created a new proposal
3. and then applied it.
Syslog for the Controller node attached. Let me know if you need
another log file.
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net <mailto:dsanpe...@mcna.net>
Office: (800) 494-6262 Ext. 203
------------------------
CONFIDENTIALITY NOTICE: This electronic mail may contain
information that is privileged, confidential, and/or
otherwise protected from disclosure to anyone other than
its intended recipient(s). Any dissemination or use of
this electronic mail or its contents by persons other
than the intended recipient(s) is strictly prohibited. If
you have received this communication in error, please
notify the sender immediately by reply e-mail so that we
may correct our internal records. Please then delete the
original message. Thank you.
On 10/1/13 4:45 PM, simon_jake...@dell.com
<mailto:simon_jake...@dell.com> wrote:
My mistake it's actually barclamp_install.rb.
*From:*Daniel San Pedro [mailto:dsanpe...@mcna.net]
*Sent:* Tuesday, October 01, 2013 3:40 PM
*To:* Jakesch, Simon
*Cc:* Jacob, Jacob; crowbar
*Subject:* Re: [Crowbar] mesa-1.6 - cinder barclamp fails when
applying proposal
I can not locate /opt/dell/bin/install_barclamp.rb on the crowbar
admin node nor on allocated node..
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net <mailto:dsanpe...@mcna.net>
Office: (800) 494-6262 Ext. 203
------------------------
CONFIDENTIALITY NOTICE: This electronic mail may
contain information that is privileged, confidential,
and/or otherwise protected from disclosure to anyone
other than its intended recipient(s). Any
dissemination or use of this electronic mail or its
contents by persons other than the intended
recipient(s) is strictly prohibited. If you have
received this communication in error, please notify
the sender immediately by reply e-mail so that we may
correct our internal records. Please then delete the
original message. Thank you.
On 10/1/13 4:37 PM, Daniel San Pedro wrote:
Thanks. I did not modify anything when deploying the cinder
barclamp. It fails on the first try. Path:
Install crowbar OS.
Install Crowbar.
PXE boot two nodes: Controller and Compute
Rename and allocate nodes, wait for green light
Create proposals for each OpenStack barclamp except Swift and
Tempest
Apply each proposal in order starting with the database
barclamp to Controller node
Apply the cinder barclamp to controller node - failure
My test environment is as follows:
KVM Host
Crowbar admin node running as KVM guest
Two KVM guests PXE booting off the Crowbar admin node
One private virtual network that all guests can talk to each
other on
One public network that the crowbar node has where I can
access the GUI from
I received instructions from another Dell CloudEdge team
member on making this work by editing the
bc-template-network.json file before installing crowbar, and
it works well.
I am currently running through the steps you outlined below
and will report back my findings. Thanks once again.
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net <mailto:dsanpe...@mcna.net>
Office: (800) 494-6262 Ext. 203
------------------------
CONFIDENTIALITY NOTICE: This electronic mail may
contain information that is privileged,
confidential, and/or otherwise protected from
disclosure to anyone other than its intended
recipient(s). Any dissemination or use of this
electronic mail or its contents by persons other
than the intended recipient(s) is strictly
prohibited. If you have received this
communication in error, please notify the sender
immediately by reply e-mail so that we may
correct our internal records. Please then delete
the original message. Thank you.
On 10/1/13 2:36 PM, simon_jake...@dell.com
<mailto:simon_jake...@dell.com> wrote:
Daniel,
we've taken a look at your issue, and we're having a hard
time coming up with a path on how you got to where you
are now. Specifically your second statement about being
able to login with the cinder.conf password. None the
less here are the things you can do to either fix this
issues or provide more information to use:
We can try to recreate the cinder DB and reinitialize the
password. In order to do so we recommend you stop
chef-client from running on whichever node you have the
DB located (which is typically the node that runs all the
other MySQL DBs). Then you should drop the DB via the
usual mysqladmin command. After we upload the whole
Barclamp, this will reset all the associated Databags on
the chef server, which is exactly what you want. You do
this via: /opt/dell/bin/install_barclamp.rb cinder. For
good measure delete the cinder.conf and restart
chef-client. The DB and cinder.conf should be recreated
with a new password at this time.
If the above method doesn't result in a success, please
send us the logfile contents (including +-100 lines)
before and after the relevant section. We'll be happy to
take a closer look at things.
Hope this helps,
Simon
*From:*crowbar-bounces *On Behalf Of *Jacob, Jacob
*Sent:* Monday, September 30, 2013 4:36 PM
*To:* dsanpe...@mcna.net <mailto:dsanpe...@mcna.net>
*Cc:* crowbar
*Subject:* Re: [Crowbar] mesa-1.6 - cinder barclamp fails
when applying proposal
*Dell - Internal Use - Confidential *
Hi Daniel,
Looks like after you changed cinder.conf , the changes
get reverted back to the wrong one when you re-applied
the proposal.
Let me try to reproduce this here. Will keep you posted.
Thanks
Jacob M. Jacob
Software Dev Principal Engineer
*Dell*| Enterprise Cloud Solutions
*From:*crowbar-bounces *On Behalf Of *Daniel San Pedro
*Sent:* Monday, September 30, 2013 3:17 PM
*To:* crowbar
*Subject:* [Crowbar] mesa-1.6 - cinder barclamp fails
when applying proposal
Hello,
I am running mesa-1.6_openstack-os-build.3459.dev. I am
currently testing crowbar to use on our production
environment. I am able to successfully apply the
database, keystone, rabbitmq, and glance barclamps, but
get hung up when applying cinder. I get the following
error message in the logs and the proposal fails:
/CRITICAL [cinder] (OperationalError) (1045, "Access
denied for user 'cinder'@'192.168.124.81' (using
password: YES)")/
Upon further research, I found that the MySQL password
that the barclamp reports differs from what is cinder.conf
I have tried all of the below with no success:
* Synchronize passwords. I tried changing cinder.conf
to the password found in the barclamp and reapplied,
and vice versa
* I am able to login locally to MySQL using the cinder
user and the password found in cinder.conf
* Edit
/opt/dell/barclamps/cinder/chef/data_bags/crowbar/bc-template-cinder.json
and manually add the password in the "db" section
Thanks!
--
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net <mailto:dsanpe...@mcna.net>
Office: (800) 494-6262 Ext. 203
------------------------
CONFIDENTIALITY NOTICE: This electronic mail
may contain information that is privileged,
confidential, and/or otherwise protected from
disclosure to anyone other than its intended
recipient(s). Any dissemination or use of
this electronic mail or its contents by
persons other than the intended recipient(s)
is strictly prohibited. If you have received
this communication in error, please notify
the sender immediately by reply e-mail so
that we may correct our internal records.
Please then delete the original message.
Thank you.
