Closed Bug 1331211 Opened 8 years ago Closed 8 years ago

Discussion Forum: mozilla.dev.ui-alerts

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

All
Other
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: MattN, Assigned: vinh)

References

()

Details

(Whiteboard: pending giganews)

List Name: mozilla.dev.ui-alerts List Admin: MattN@mozilla.com Short Description: Automated messages about UI changes (moderated) Long Description: Automated messages regarding UI changes detected in automation on desktop Firefox builds. Documentation: https://developer.mozilla.org/en-US/docs/Mozilla/QA/Browser_screenshots Justification / Special Instructions: This is similar to mozilla.dev.tree-alerts and mozilla.dev.telemetry-alerts in that it will used for automated messages about UI changes. To start it will be the result of mozscreenshots running on mozilla-central Nightly for desktop builds.
Over to MOC for implementation. Gerv
Assignee: gerv → nobody
Component: Discussion Forums → MOC: Service Requests
Product: mozilla.org → Infrastructure & Operations
QA Contact: justdave → lypulong
Assignee: nobody → vhua
newsgroup created on mailman2. Pending giganews/google groups. **Reminder for self** - need to set to advertise once newsgroup is active.
Whiteboard: pending giganews
admin password emailed to MattN@mozilla.com
Status: NEW → ASSIGNED
Wes Jan 19, 14:39 CST Hello, Thank you for your patience. I am happy to report that our Giganews Administrators have added the following moderated newsgroup: mozilla.dev-ui-alerts Please let us know if you have any further questions! Regards, Wes Customer Support Level II
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Hi Vinh, No messages seem to be showing up over NNTP though the group does now exist. I just sent an email in the last hour and it doesn't appear but I did receive it via email. Google Groups seems to gets the messages fine: https://groups.google.com/forum/#!forum/mozilla.dev.ui-alerts
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Flags: needinfo?(vhua)
:MattN - yea I'm not seeing any messages either. I've emailed giganews to have them take a look.
Flags: needinfo?(vhua)
Hi Gerv, Would you mind updating the raw-ng-list.txt file when you get a chance so I can link to the forums anchor in my announcement when the newsgroup starts working? Thanks
Flags: needinfo?(gerv)
raw-ng-list.txt updated. Gerv
Flags: needinfo?(gerv)
Thanks Gerv though it seems like you committed the wrong file as an unrelated .pl script was updated but the txt file was not: https://github.com/mozilla/community-data/commit/5a2ba4e2daeb8a58ed178b23fc8ef33c0b31fbda
Flags: needinfo?(gerv)
(In reply to Matthew N. [:MattN] (PM me if requests are blocking you) from comment #5) > Hi Vinh, > > No messages seem to be showing up over NNTP though the group does now exist. > I just sent an email in the last hour and it doesn't appear but I did > receive it via email. > > Google Groups seems to gets the messages fine: > https://groups.google.com/forum/#!forum/mozilla.dev.ui-alerts Can you tell me where you are sending the email to? Are you sending it to dev-ui-alerts@lists.mozilla.org or are you sending it directly to NNTP or are you sending it to the google group?
(In reply to Ed Lim [:limed] from comment #10) > (In reply to Matthew N. [:MattN] (PM me if requests are blocking you) from > comment #5) > > Hi Vinh, > > > > No messages seem to be showing up over NNTP though the group does now exist. > > I just sent an email in the last hour and it doesn't appear but I did > > receive it via email. > > > > Google Groups seems to gets the messages fine: > > https://groups.google.com/forum/#!forum/mozilla.dev.ui-alerts > > Can you tell me where you are sending the email to? Are you sending it to > dev-ui-alerts@lists.mozilla.org or are you sending it directly to NNTP or > are you sending it to the google group? Emails sent to dev-ui-alerts@lists.mozilla.org are getting delivered to mailman subscribers and Google Groups but not via NNTP. Messages submitted directly to NNTP via Thunderbird seem to go into a black hole and don't appear via NNTP and don't get sent to mailman or Google Groups.
Oops, sorry about that, no idea how that happened. Now fixed. Gerv
Flags: needinfo?(gerv)
Any updates? I would like to announce this list on Tuesday 8am Pacific but would need time on Monday to populate the list with backdated automated alerts. Thanks
Flags: needinfo?(vhua)
Flags: needinfo?(limed)
:limed - Any ideas?
Flags: needinfo?(vhua)
(In reply to Matthew N. [:MattN] (PM me if requests are blocking you) from comment #11) > (In reply to Ed Lim [:limed] from comment #10) > > (In reply to Matthew N. [:MattN] (PM me if requests are blocking you) from > > comment #5) > > > Hi Vinh, > > > > > > No messages seem to be showing up over NNTP though the group does now exist. > > > I just sent an email in the last hour and it doesn't appear but I did > > > receive it via email. > > > > > > Google Groups seems to gets the messages fine: > > > https://groups.google.com/forum/#!forum/mozilla.dev.ui-alerts > > > > Can you tell me where you are sending the email to? Are you sending it to > > dev-ui-alerts@lists.mozilla.org or are you sending it directly to NNTP or > > are you sending it to the google group? > > Emails sent to dev-ui-alerts@lists.mozilla.org are getting delivered to > mailman subscribers and Google Groups but not via NNTP. > Messages submitted directly to NNTP via Thunderbird seem to go into a black > hole and don't appear via NNTP and don't get sent to mailman or Google > Groups. Hmm that makes no sense, ultimately when a post ends up in google groups it will come from NNTP so this appears to be an NNTP issue of some sort on the giganews side of things
Flags: needinfo?(limed)
I've emailed giganews again to have them double check.
Here's the response from giganews: Hello, Thank you for your reply. From the logs provided below, we are sending the messages correctly. Can you clarify if the moderator email address is setup correctly? (Please confirm the moderator email address in your reply) [root@cruncher1 serv]# zfgrep ui-alerts archive/posting-20170122-* archive/posting-20170122-0100.gz:Jan 21 21:26:29 serv2.dca1 postd[19907]: 216.166.100.84 post queued <mailman.1650.1485055588.19729.dev-ui-alerts@lists.mozilla.org> archive/posting-20170122-0100.gz:Jan 21 21:26:29 serv2.dca1 queuefilter[991]: Message-ID: <mailman.1650.1485055588.19729.dev-ui-alerts@lists.mozilla.org>#015#012 archive/posting-20170122-0100.gz:Jan 21 21:26:29 serv2.dca1 queuefilter[991]: Article ACCEPTED: <mailman.1650.1485055588.19729.dev-ui-alerts@lists.mozilla.org> 63.245.214.181 mozilla.org NoAuthUser nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail 60 Nightly Screenshot Changes: c91249f41e37 to 57ac9f63fc69 archive/posting-20170122-0100.gz:Jan 21 21:26:29 serv2.dca1 queuefilter[991]: TAKETHIS: 439 <mailman.1650.1485055588.19729.dev-ui-alerts@lists.mozilla.org>#012 archive/posting-20170122-0100.gz:Jan 21 21:26:29 serv2.dca1 queuefilter[991]: Article FAILED: bad response: 439 <mailman.1650.1485055588.19729.dev-ui-alerts@lists.mozilla.org>#012 archive/posting-20170122-0100.gz:Jan 21 21:55:39 serv2.dca1 postd[19898]: 216.166.100.194 post queued <mailman.1722.1485057338.19728.dev-ui-alerts@lists.mozilla.org> archive/posting-20170122-0100.gz:Jan 21 21:55:39 serv2.dca1 queuefilter[999]: Message-ID: <mailman.1722.1485057338.19728.dev-ui-alerts@lists.mozilla.org>#015#012 archive/posting-20170122-0100.gz:Jan 21 21:55:39 serv2.dca1 queuefilter[999]: Article ACCEPTED: <mailman.1722.1485057338.19728.dev-ui-alerts@lists.mozilla.org> 63.245.214.181 mozilla.org NoAuthUser nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail 60 Nightly Screenshot Changes: c91249f41e37 to 57ac9f63fc69 archive/posting-20170122-0100.gz:Jan 21 21:55:39 serv2.dca1 queuefilter[999]: TAKETHIS: 239 <mailman.1722.1485057338.19728.dev-ui-alerts@lists.mozilla.org>#012 archive/posting-20170122-1010.gz:Jan 22 09:53:26 serv1.dca1 postd[15927]: 216.166.100.34 post queued <mailman.1732.1485100406.19728.dev-ui-alerts@lists.mozilla.org> archive/posting-20170122-1010.gz:Jan 22 09:53:26 serv1.dca1 queuefilter[21015]: Message-ID: <mailman.1732.1485100406.19728.dev-ui-alerts@lists.mozilla.org>#015#012 archive/posting-20170122-1010.gz:Jan 22 09:53:26 serv1.dca1 queuefilter[21015]: Article ACCEPTED: <mailman.1732.1485100406.19728.dev-ui-alerts@lists.mozilla.org> 63.245.214.181 mozilla.org NoAuthUser nntp.mozilla.org!news.mozilla.org.POSTED!not-for-mail 1 test archive/posting-20170122-1010.gz:Jan 22 09:53:26 serv1.dca1 queuefilter[21015]: TAKETHIS: 239 <mailman.1732.1485100406.19728.dev-ui-alerts@lists.mozilla.org>#012 Thank you in advance for this information. We look forward to hearing from you! Regards, Wes Customer Support Level II
(In reply to Vinh Hua [:vinh] from comment #17) > Thank you for your reply. From the logs provided below, we are sending the > messages correctly. > > Can you clarify if the moderator email address is setup correctly? (Please > confirm the moderator email address in your reply) And what was your reply? I assume this is something you had to set up? You can set the moderator email to dev-ui-alerts-owner@lists.mozilla.org Thanks
Flags: needinfo?(vhua)
Wes Feb 3, 17:54 CST Hello, Thank you for your patience. After review, it appears there is a discrepancy with the moderator email. The moderator email you have setup is "dev-ui-alerts-owner@lists.mozilla.org" However, it needs to be "mozilla-dev-ui-alerts@lists.mozilla.org" Once you have changed the moderator email address, you should be able to view the postings within the group. :limed - any idea where to make the adjustment? I don't recall going through the moderator email set up in the runbook.
Flags: needinfo?(vhua) → needinfo?(limed)
(In reply to Vinh Hua [:vinh] from comment #19) > Wes > Feb 3, 17:54 CST > > Hello, > > Thank you for your patience. After review, it appears there is a discrepancy > with the moderator email. > > The moderator email you have setup is "dev-ui-alerts-owner@lists.mozilla.org" > > However, it needs to be "mozilla-dev-ui-alerts@lists.mozilla.org" > > Once you have changed the moderator email address, you should be able to > view the postings within the group. > > > :limed - any idea where to make the adjustment? I don't recall going > through the moderator email set up in the runbook. I have responded and do not agree with their solution
Flags: needinfo?(limed)
FWIW I had tested that dev-ui-alerts-owner@lists.mozilla.org gets delivered to me before giving that address in comment 18.
(In reply to Matthew N. [:MattN] (Meetings In Taipei) from comment #21) > FWIW I had tested that dev-ui-alerts-owner@lists.mozilla.org gets delivered > to me before giving that address in comment 18. I'm still awaiting giganews' response fyi
Thanks for the update. I'm not sure what could possibly take them so long… I saw a test message from one of their employees at https://groups.google.com/forum/#!topic/mozilla.dev.ui-alerts/htfkGAGW4xk but it also doesn't show up via NNTP.
(In reply to Matthew N. [:MattN] (Meetings In Taipei) from comment #23) > Thanks for the update. I'm not sure what could possibly take them so long… I > saw a test message from one of their employees at > https://groups.google.com/forum/#!topic/mozilla.dev.ui-alerts/htfkGAGW4xk > but it also doesn't show up via NNTP. I don't know myself but I have gotten a response from them today <snip> Hello, At this time our engineers have discovered a possible resolution to this matter, which we are waiting for them to test. As soon as we have an update applicable to you as the end user we will reach out and let you know. We appreciate your patience throughout this process. Regards, Katherine Level 2 | Team Lead </snip>
This appears to be fixed now <snip> Hello, Thank you for your patience. The group is now repaired and all articles are on usenet except for the first one. There is nothing we can do about the first article as it was never numbered, most likely due to an issue causing us to never see the accepted message. We have tested posting using both thunderbird to news.mozilla.org and from the google groups page. <snip>
Thanks. It's working now!
Status: REOPENED → RESOLVED
Closed: 8 years ago8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.