 |
 |
Using the local SE seems a good suggestion to me. From: Testbed Support for GridPP member institutes [mailto:[log in to unmask]] On Behalf Of Daniela Bauer Sent: 20 November 2012 10:22 To: [log in to unmask] Subject: Re: Tickets for the 20th of November Just to get back to the original list. I've got one more ticket where I would appreciate some input: https://ggus.eu/ws/ticket_info.php?ticket=88489 Am I being dense (feel free to answer with yes), but what actually is the guy's problem ? Cheers, Daniela On 19 November 2012 23:40, Christopher J. Walker <[log in to unmask]<mailto:[log in to unmask]>> wrote: On 19/11/12 17:14, Alessandra Forti wrote: /Discussion point (mainly for atlas): In https://ggus.eu/ws/ticket_info.php?ticket=86334 Wahid and Brian had an exchange about the usefulness of tickets to track very long standing issues- the main grumble for Wahid seemed to be the constant presence of ECDF on the daily resume because of this ticket. I agree with Brian that tickets are the tool to track issues, but the constant noise created by this ticket (which isn't going anywhere fast) is a nuisance. Maybe the resume needs to start ignoring certain classes of tickets (low priority, on hold ones for example). / In the abstract, I find it annoying when a ticket is solved with "I've transferred it to another ticketing system", or "There's a new release that will solve this problem - I'm planning to install it in 6 months". In both cases, IMHO, it should be put on hold. There's a slightly different category of "on hold" - "I can't solve this problem until this other problem is solved by someone else". Again this problem should be on hold, but I don't know how to mark the tickets depending on each other. It's also not conducive to sensible debugging if the issue is known to affect several sites, but that's not reported in the ticket. Don't think it is a good policy to make tickets disappear from the resume. They should however be in a "on hold" section - and sites shouldn't get daily nags about them (once a week would be fine). We can ignore them when we discuss tickets. We have been wilfully ignoring Durham for a while and their ticket has been opened for much longer than the networking ones. Said that I find them irritating too because nobody is really working on them and then one has to wonder if it is really useful to keep open a ticket for a problem nobody is working on. Chris cheers alessandra On 19/11/2012 16:53, Alessandra Forti wrote: I solved Brunel and EFDA-JET upgrade tickets. I believe the COD or whoever should be closing them isn't payng attention. cheers alessandra On 19/11/2012 15:50, Matt Doidge wrote: Hello all, I've taken a break from whining about python to send you the ticket update you all look forward to. Cheers, Matt 29 Open UK tickets this week. Thanks for all your hard work making my job easier :-) Unsupported Glite Software. MANCHESTER: https://ggus.eu/ws/ticket_info.php?ticket=87467 (17/10) On Hold (5/11) Just the DPM left to go now I think, which is scheduled for next week. ECDF: https://ggus.eu/ws/ticket_info.php?ticket=87171 (10/10) In progress (7/11) Opened support tickets to help deal with their issues: https://ggus.eu/tech/ticket_show.php?ticket=88284 (cream canceling jobs-in progress) https://ggus.eu/ws/ticket_info.php?ticket=88285 (cream sge information pub-solved) https://ggus.eu/tech/ticket_show.php?ticket=88286 (argus problems- on hold) EFDA-JET: https://ggus.eu/ws/ticket_info.php?ticket=87169 (10/10) In Progress (9/11) I think jet are all upgraded, but having nagios issues. Might need a hand from someone. Not sure why this ticket hasn't closed though. BRISTOL: https://ggus.eu/ws/ticket_info.php?ticket=87472 (17/10) In Progress (19/11) Have an emi2 test CE up and running, so things are looking good. BRUNEL: https://ggus.eu/ws/ticket_info.php?ticket=87469 (17/10) In Progress (5/11) Site is on EMI2, so I don't understand why this ticket didn't auto-close. Worth manually solving it (unless you guys have some hidden glite about the place). UCL: https://ggus.eu/ws/ticket_info.php?ticket=87468 (17/10) On hold (1/11) Ben hoped to have an EMI cream by the 9th, not sure that that target was reached. SHEFFIELD: Elena has closed their ticket after upgrading everything. NGI/VOMS https://ggus.eu/ws/ticket_info.php?ticket=88546 (16/11) Setting up a new "epic" VO (that's actually what they're calling themselves). Debate in the finer points of naming - original suggestion was "epic.gridpp.ac.uk<http://epic.gridpp.ac.uk>" but need to decide on some precedent for future VO naming. Andy McNab suggest the VO registers it's own domain name and uses that. In progress (16/11) https://ggus.eu/ws/ticket_info.php?ticket=88395 (9/11) David Meredith asks the NGI (i.e. us) if there are any objections to deleting the "UKI-Local-MAN-HEP" site-that-never-was from the gocdb. Waiting for reply (13/11) RHUL https://ggus.eu/ws/ticket_info.php?ticket=88417 (11/11) Alastair would like to know what you have in your squid ACLs/customize.sh to debug the squid problems at RHUL. In progress (12/12) GLASGOW https://ggus.eu/ws/ticket_info.php?ticket=88376 (8/11) Biomed ticketed Glasgow with a problem on one of their CEs, but have neglected to reply to Sam's question on the 9th. Still Waiting for Reply (9/11) DURHAM https://ggus.eu/ws/ticket_info.php?ticket=86242 (20/9) Another example of biomed's silence when asked a question. Waiting for reply (5/11) BIRMINGHAM https://ggus.eu/ws/ticket_info.php?ticket=88262 (6/11) How are Birmingham's power problems coming along? On hold (9/11) RALPP https://ggus.eu/ws/ticket_info.php?ticket=88099 (3/11) Transfer errors continued, although they've changed in nature. The last update was from Wahid on Thursday, any word from the site? They've been quiet on this one, which suggests that they're not getting alerts. In progress (16/11) OXFORD https://ggus.eu/ws/ticket_info.php?ticket=86106 (14/9) Low atlas sonar rates to BNL. Brian asked if you guys could see if the bad rates also applied to direct globus-url-copies. Have you had a chance to have a bash at this? In Progress (6/11) Discussion point (mainly for atlas): In https://ggus.eu/ws/ticket_info.php?ticket=86334 Wahid and Brian had an exchange about the usefulness of tickets to track very long standing issues- the main grumble for Wahid seemed to be the constant presence of ECDF on the daily resume because of this ticket. I agree with Brian that tickets are the tool to track issues, but the constant noise created by this ticket (which isn't going anywhere fast) is a nuisance. Maybe the resume needs to start ignoring certain classes of tickets (low priority, on hold ones for example). Tickets from the UK: https://ggus.eu/tech/ticket_show.php?ticket=87891 Chris's ticket concerning the hard-to-kill lhcb jobs. https://ggus.eu/ws/ticket_info.php?ticket=87264 Daniela's ticket concerning the enormous number of entries showing up in /var/glite/log, with some interesting input from Daniela. QMUL & Lancaster also see this problem, if you do too please add your voice (to coax a swifter fix). If you have any tickets you'd like the spot light on, please let me know. -- Facts aren't facts if they come from the wrong people. (Paul Krugman) -- Sent from the pit of despair ----------------------------------------------------------- [log in to unmask]<mailto:[log in to unmask]> HEP Group/Physics Dep Imperial College Tel: +44-(0)20-75947810 http://www.hep.ph.ic.ac.uk/~dbauer/ -- Scanned by iCritical.