Relationship between aggregates and resources breaks if name of aggregate changes

[sedwards@bbn.com]

I'm looking at instageni rack submission.

In particular, the UI doesn't show there being any resources for these two aggregates:

instageni.gpolab.bbn.com:12369
utah.geniracks.net:12369

These formerly were reported as:

instageni.gpolab.bbn.com:80
utah.geniracks.net:80 

In particular I now notice that the old aggregate utah.geniracks.net:80 hasn't updated since December: ​https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=utah.geniracks.net%3A80

But the resources for it are listed as having reported today: ​https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=utah.geniracks.net%3A80

On the other hand the old aggregate instageni.gpolab.bbn.com:80 hasn't updated since December: ​https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=instageni.gpolab.bbn.com%3A80

But there are no resources for it listed at all: ​https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=aggregate_details;aggregate=instageni.gpolab.bbn.com%3A80

The first case (the utah.geniracks.net case) makes me think the link between the aggregate and the resources wasn't updated when the aggregate name changed. However, the second case doesn't clearly support that thinking.

I remember that we had some discussions about things like what can be updated once it's reported when Kevin built the client so this may be somewhat expected behavior. That said, I'm not sure how to proceed and get the resources linked to the new aggregate.

Can you look around and see if you can add any data for these points? Any thoughts?

[sedwards@bbn.com]

I found a resource that looks like it is an IG node on the GPO rack: ​https://gmoc-db.grnoc.iu.edu/protected-openid/index.pl?method=node_details;node=urn%3Apublicid%3AIDN%2Binstageni.gpolab.bbn.com%2Bnode%2Bpc1

But it doesn't look like it has an aggregate listed at all.

Also, we switched the reported name on the instageni.gpolab.com rack pretty quickly after reporting it at all. Whereas utah.geniracks.net had been reporting for awhile before we made the switch.

[sedwards@bbn.com]

It could also be a bug in the DB or the gmoc client data submission code. (Or perhaps even in my code that is submitting data.)

This may not even be a proper bug. It's possible we just need a procedure for how to change the name of the aggregate that's being reported.

Regardless, Mitch said he'd try to identify the problem before doing the next release (and hopefully fix it).