Project

General

Profile

Bug #2686

RPM Should sudo to user frontend for reconfig

Added by Derek Weitzel over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Douglas Strain
Category:
Frontend
Target version:
Start date:
04/27/2012
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

The init.d process doesn't sudo to the frontend user before running reconfig. Therefore, the new directories added when a new group is added to frontend.xml all have the wrong ownership.

Don't actually know where that file is now? Is it in the glideinwms git? In the release repo?

History

#1 Updated by Douglas Strain over 8 years ago

  • Assignee set to Douglas Strain
  • Target version set to v2_7_x

It's in the osg software repo as a source file to the RPM. I'll take care of this. I think the factory has the same problem with reconfigs and new entries.

#2 Updated by Douglas Strain over 8 years ago

  • Status changed from New to Resolved

This has been fixed in the RPMs glideinwms-2.5.7-3 and glideinwms-3.0.0-4.

I have marked this ticket as resolved and will close it once I fully test these RPMs (in osg-testing and osg-contrib respectively)

#3 Updated by Douglas Strain over 8 years ago

  • Status changed from Resolved to Assigned

I noticed this has a problem when you use the "upgrade" functionality since it tries to write back the xml, sigh. More work is needed here (perhaps the frontend.xml should be owned by "frontend")

#4 Updated by Douglas Strain over 8 years ago

  • Status changed from Assigned to Resolved

I have changed the ownership of /etc/gwms-frontend/frontend.xml to frontend and /etc/gwms-factory to gfactory. This should fix the upgrade from failing when it does writeback.

#5 Updated by Parag Mhashilkar over 8 years ago

  • Target version changed from v2_7_x to v2_6

#6 Updated by Parag Mhashilkar over 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF