Project

General

Profile

Support #6545

Test v3.2.5.1 rpms from the osg-development repo

Added by Parag Mhashilkar over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Parag Mhashilkar
Category:
test category
Target version:
Start date:
06/23/2014
Due date:
% Done:

0%

Estimated time:
Stakeholders:
Duration:

Related issues

Related to GlideinWMS - Bug #6421: new RPM installation failing Closed06/06/2014

Related to GlideinWMS - Bug #6546: trust_doman attribute inconsistent between default factory and frontend xmlClosed06/24/2014

History

#1 Updated by John Weigand over 5 years ago

Bug #6421 tested with glideinwms-factory-3.2.5.1-1.osg32.el6.noarch
and appears resolved.
John Weigand

#2 Updated by John Weigand over 5 years ago

Bug #6546 was the only issue I detected in this set of testing.
Once manually resolved in the configurations, everything worked fine.
Jobs could be submitted and run at the entry point.
Whether it is a line stopper or not is questionable.
Documentation for configuration and troubleshooting definitely should
be done as soon as possible.
It does not affect upgrades as I tested those on #

John Weigand

#3 Updated by John Weigand over 5 years ago

Bug #6546 was the only issue I detected in this set of testing.
Once manually resolved in the configurations, everything worked fine.
Jobs could be submitted and run at the entry point.
Whether it is a line stopper or not is questionable.
Documentation for configuration and troubleshooting definitely should
be done as soon as possible.
It does not affect upgrades as I tested those on Support#5932 and since
the old configuration files were used, upgrade was not affected.

John Weigand

#4 Updated by John Weigand over 5 years ago

  • Status changed from New to Feedback
  • Assignee changed from John Weigand to Parag Mhashilkar

#5 Updated by John Weigand over 5 years ago

Tested v3.2.5.1-2 from osg-development for standard 4.

Only changes are in the frontend, the addition of a 2nd factory

<collectors>
  <collector DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=gfactory-1.t2.ucsd.edu" 
    comment="Define factory collector globally for simplicity" 
    factory_identity="gfactory@gfactory-1.t2.ucsd.edu" 
    my_identity="<username>@gfactory-1.t2.ucsd.edu" 
    node="gfactory-1.t2.ucsd.edu"/>
  <collector DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=glidein.grid.iu.edu" 
    comment="Define factory collector globally for simplicity" 
    factory_identity="gfactory@glidein.grid.iu.edu" 
    my_identity="<username>@glidein.grid.iu.edu" 
    node="glidein.grid.iu.edu"/>
</collectors>

Everything else tested good.

On upgrade, the only difference was that in the frontend.xml.rpmnew file, the keywords
normally expanded on an fresh install, are not expanded. This was expected.

frontend.xml.rpmnew
--------------------
<schedd DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=FRONTEND_HOSTNAME" 
    fullname="FRONTEND_HOSTNAME"/>

frontend.xml (fresh install)
-----------------------------
<schedd DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=fermicloud004.fnal.gov" 
    fullname="fermicloud004.fnal.gov"/>

There was no ticket to reference for this change to the template.

John Weigand

#6 Updated by John Weigand over 5 years ago

Parag,

This is related to the inclusion of the osg factory in the frontend.xml template
which we don't have a specific ticket for.

I just noticed this.

The OSG collector was included in the same factory element as the UCSD collector.

      <factory query_expr='((stringListMember("<vo>", GLIDEIN_Supported_VOs)))'>
         <match_attrs>
         </match_attrs>
         <collectors>
            <collector DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=gfactory-1.t2.ucsd.edu" ... />
            <collector DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=glidein.grid.iu.edu"  .../>
         </collectors>
      </factory>

Shouldn't it have have been in a unique factory element instead? .. as in ...

<factory query_expr='((stringListMember("<vo>", GLIDEIN_Supported_VOs)))'>
  <match_attrs>
  </match_attrs>
  <collectors>
    <collector DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=gfactory-1.t2.ucsd.edu"... />
  </collectors>
</factory>

<factory query_expr='((stringListMember("<vo>", GLIDEIN_Supported_VOs)))'>
  <match_attrs>
  </match_attrs>
  <collectors>
    <collector DN="/DC=com/DC=DigiCert-Grid/O=Open Science Grid/OU=Services/CN=glidein.grid.iu.edu".../>
  </collectors>
</factory>

Or is it sufficient to leave it to the FE admin to manually adjust?

Just curious.
John Weigand

#7 Updated by Parag Mhashilkar over 5 years ago

  • Status changed from Feedback to Closed


Also available in: Atom PDF