On 07/22/2013 11:11 PM, Venkat_R_K(a)Dell.com wrote:
Hi Nick,
I had a problem with beaker-setup on Saturday. I tried the suggestion told by Bill.
I got the same error which I reported to Bill "user not registered with group
lab_controller" . so I commented the below line in the script.
curl -b tmpcookie -d fqdn=$(hostname -f) -d lusername=host/localhost.localdomain -d
lpassword=password -d email=root(a)localhost.localdomain -d Save=1
http://localhost/bkr/labcontrollers/save || exit 1
the problem is the curl is not atomatic the process of adding a new lab controller with
the default credentials. So I created manually as Bill guided me. Then beaker-setup was
working fine and also beaker-import was working fine too.
Ah, OK - we're slowly working through the code to make sure permission
failures are reported as proper errors rather than internal server
errors, but it's going to take some time for us to get them all :(
Specifically in the case of Beaker-in-a-box, we're currently working on
an updated set of instructions that don't require a bare metal machine,
just a system where the user doesn't mind us adjusting their libvirt
network settings and creating some Fedora VMs:
http://gerrit.beaker-project.org/#/c/2072/
The idea behind that revised approach is to focus on getting people up
and running quickly with a basic environment for development and
experimentation, and then deferring to the full install guide when they
want to set up an actual production instance.
I am doing the step of beaker-virt. I shall let you know if there is
any issue.
***********************************************************
Note:
If you would permit me, I shall provide an option for cleaning in the script if user
re-run the script.
Script name: beaker-setup
Scenario 1 :
Notify user about the existing database.
If user == delete_existing_database
Cleaning of mysql database;
Elif user == update existing database;
Update the database;
Scenario 2 :
Updating all curl issues related to adding a lab_controller etc.
Also we should update the status of curl success|failure and exit upon the return and
guide the user to do it via browser.
*****************************************
I shall try to do the complete set up one more time and let you know if there is any more
issue.
Depending on what you're attempting to set up (an experimental instance
or the seeds of a production instance), the draft
libvirt-and-Fedora-based guide on Gerrit
(
http://gerrit.beaker-project.org/#/c/2072/) may be helpful, too. I
suspect some of these issues (such as "What happens if you run the
scripts a second time?") may apply there as well.
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Testing Solutions Team Lead
Beaker Development Lead (
http://beaker-project.org/)