Le mardi 12 mars 2019 à 16:44 +0530, Deepshikha Khandelwal a écrit : > It is now fixed.
This was likely caused by the bugzilla upgrade, who logged the bot out. To prevent that from happening, we have now a script to log with cron (every hour), and I am also moving the bugzilla script node inside the lan, which mean I am doing a few tests (the old one is untouched). -- Michael Scherer Sysadmin, Community Infrastructure and Platform, OSAS
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Gluster-infra mailing list [email protected] https://lists.gluster.org/mailman/listinfo/gluster-infra
