Modify

Ticket #1072 (closed defect: wontfix)

Opened 12 years ago

Last modified 11 years ago

uuid-based configs don't work on bcfg server itself

Reported by: https://www.google.com/accounts/o8/id?id=AItOawlI1O8VyrSK3MFDS2zghV1X2pul0TDfg1o Owned by: desai
Priority: minor Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-server Version: 1.0
Keywords: Cc:

Description

Using 1.2.0rc2, I created two clients: one that is my bcfg server, and another with a uuid specified:

  <Client name="rrz-master.ccstar.lanl.gov" profile="rrz1-master"/>
  <Client name="computeimage" profile="rrz-compute" uuid="computeimage"/>

and ran the client on two different machines both with and without the '-u' option:

  bcfg2 -q -v -n
  bcfg2 -q -v -n -u computeimage

When run on the machine that is also running the bcfg server, both cases result in the real machine's config (as if I hadn't run with '-u' either time). But when run on an independent client, adding the '-u' works as I would expect - the client gets the config associated with the 'computeimage' config.

Attachments

Change History

comment:1 Changed 11 years ago by solj

  • Status changed from new to closed
  • Resolution set to wontfix

The only way to do this is to use a separate bcfg2.conf which doesn't contain the key and certificate entries and point to it with the -C option. Using SSL authentication overrides everything when determining client identity.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.