Date: January 13th 2014, 07h22 by mail

Attendees:

• Patrick Guterl (CNRS I3S)
• Jerome Pansanel (CNRS IPHC)
• Doan Trung Tung (IFI)

Next conference: January 20th 2014, 10h00.

Remind about best practices:

• Start by following up on open tickets and verifying solved tickets, before submitting new ones.
• Before submitting a ticket verify that:
  • Another ticket does not already exist for the same problem
  • The resource is not in downtime and is in production status ⇒ you can use the brand new VAPOR portal to do so
  • The alarm can be reproduced manually
• For CEs: ignore the alarms in the cases described here.

The following tickets have been verified:

• https://ggus.eu/ws/ticket_info.php?ticket=98862
• https://ggus.eu/ws/ticket_info.php?ticket=100012
• https://ggus.eu/ws/ticket_info.php?ticket=100104

Using VAPOR, I submit some ticket related to CEs publish invalid data:

• https://ggus.eu/ws/ticket_info.php?ticket=100103 - status is assigning but it seems ok now
• https://ggus.eu/ws/ticket_info.php?ticket=100214 - invalid data but also has problem with copying file to SE but I don't have time to check, so to be checked
• https://ggus.eu/ws/ticket_info.php?ticket=100215 - invalid data
• https://ggus.eu/ws/ticket_info.php?ticket=100216 - invalid data and also a problem with submitting job but the host status is draining (is this the reason?).
• https://ggus.eu/ws/ticket_info.php?ticket=100217 - invalid data
• https://ggus.eu/ws/ticket_info.php?ticket=100218 - invalid data
• https://ggus.eu/ws/ticket_info.php?ticket=100219 - invalid data

Nothing to report

• https://ggus.eu/ws/ticket_info.php?ticket=100148 - job canceled

All the tickets submitted by Franck the previous week still need to be monitored (nothing has been solved).

Nothing to report