Infrastructure/fedora-infrastructure
5
0
Fork 0
Code Issues 68 Pull requests Projects Releases Packages Wiki Activity Actions

[greenwave] Greenwave not sending messages on fedmsg or fedora-messaging #7735

New issue
Closed
opened 2019-04-23 21:09:03 +00:00 by tdawson · 14 comments
tdawson commented 2019-04-23 21:09:03 +00:00
Copy link

Greenwave hasn't sent a message via fedmsg or fedora-messaging for two weeks.
https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.greenwave.decision.update

I've locally logged all fedora-messaging messages, to double check, incase they weren't being duplicated on both fedora-messaging and fedmsg. Also without success.
As far as I can see, greenwave isn't sending out messages.

Greenwave hasn't sent a message via fedmsg or fedora-messaging for two weeks. https://apps.fedoraproject.org/datagrepper/raw?topic=org.fedoraproject.prod.greenwave.decision.update I've locally logged all fedora-messaging messages, to double check, incase they weren't being duplicated on both fedora-messaging and fedmsg. Also without success. As far as I can see, greenwave isn't sending out messages.
smooge commented 2019-04-23 21:18:58 +00:00
Copy link

@gnaponie @ralph I think this is somewhere on your teams workflow?

@gnaponie @ralph I think this is somewhere on your teams workflow?
smooge commented 2019-04-23 21:18:58 +00:00
Copy link

Metadata Update from @smooge:

  • Issue priority set to: Waiting on Assignee (was: Needs Review)
  • Issue tagged with: greenwave
**Metadata Update from @smooge**: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: greenwave
ralph commented 2019-04-24 01:43:53 +00:00
Copy link

Linking #7111 from the last time something like this came up.

Linking #7111 from the last time something like this came up.
ralph commented 2019-04-24 01:46:32 +00:00
Copy link

Looks like the last deployment was 12 days ago. The pods starts up and connects to the public gateway at tcp://hub.fedoraproject.org:9940 and then just sits there. It probably got connected to a gateway with broken vpn and doesn't know that it needs to reconnect. Will try to roll it out afresh with oc rollout latest dc/greenwave-fedmsg-consumers.

Looks like the last deployment was 12 days ago. The pods starts up and connects to the public gateway at `tcp://hub.fedoraproject.org:9940` and then just sits there. It probably got connected to a gateway with broken vpn and doesn't know that it needs to reconnect. Will try to roll it out afresh with `oc rollout latest dc/greenwave-fedmsg-consumers`.
ralph commented 2019-04-24 01:51:18 +00:00
Copy link

Wait - I should've checked this first. Greenwave sends messages in response to resultsdb messages.... but @tdawson, it looks like resultsdb isn't sending any. At least, I don't see any in this datagrepper query. Any idea what's up there?

edit: it looks like the most recent one is from ~14 days ago: 2019-04-09 17:17:39 UTC.

Wait - I should've checked this first. Greenwave sends messages in response to resultsdb messages.... but @tdawson, it looks like resultsdb isn't sending any. At least, I don't see any in [this datagrepper query](https://apps.fedoraproject.org/datagrepper/raw?category=resultsdb&rows_per_page=1&delta=127800). Any idea what's up there? **edit**: it looks like the most recent one is from ~14 days ago: 2019-04-09 17:17:39 UTC.
ralph commented 2019-04-24 01:58:47 +00:00
Copy link

/var/log/httpd/error_log on resultsdb01.qa.fedoraproject.org is full of pika connection refused errors.

Looks like the code was introduced in https://pagure.io/taskotron/resultsdb/pull-request/130

Maybe just missing config to go with it? @cverna, can you have a look?

`/var/log/httpd/error_log` on `resultsdb01.qa.fedoraproject.org` is full of [pika](https://pika.readthedocs.io/en/stable/) connection refused errors. Looks like the code was introduced in https://pagure.io/taskotron/resultsdb/pull-request/130 Maybe just missing config to go with it? @cverna, can you have a look?
ralph commented 2019-04-24 01:59:14 +00:00
Copy link

Metadata Update from @ralph:

  • Issue assigned to cverna
**Metadata Update from @ralph**: - Issue assigned to cverna
cverna commented 2019-04-24 06:49:40 +00:00
Copy link

The fedora-messaging config was setup to be applied in stg only.

I have opened an FBR to fix that --> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/JPQCZ3MT7AJZJLSLJDC36V3CVVZ3YUPT/

The fedora-messaging config was setup to be applied in stg only. I have opened an FBR to fix that --> https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/JPQCZ3MT7AJZJLSLJDC36V3CVVZ3YUPT/
cverna commented 2019-04-24 07:56:00 +00:00
Copy link

I have also sent an FBR to add monitoring for resultsdb messages.

https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/U4P4SAE6JG7ISJOYQNUE6L6QXCMAG6WX/

I have also sent an FBR to add monitoring for resultsdb messages. https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/U4P4SAE6JG7ISJOYQNUE6L6QXCMAG6WX/
smooge commented 2019-04-24 10:51:35 +00:00
Copy link

This has been deployed can someone test?

This has been deployed can someone test?
cverna commented 2019-04-24 11:01:57 +00:00
Copy link

The greenwave fedmsg consumer is now getting messages from resultsdb. But I have not seen yet a greenwave message sent, let's give it enough time to receive a results that would trigger a message.

The greenwave fedmsg consumer is now getting messages from resultsdb. But I have not seen yet a greenwave message sent, let's give it enough time to receive a results that would trigger a message.
kevin commented 2019-04-24 23:05:01 +00:00
Copy link

Fixed! Thanks @ralph and @cverna

📐

Fixed! Thanks @ralph and @cverna :triangular_ruler:
kevin commented 2019-04-24 23:05:01 +00:00
Copy link

Metadata Update from @kevin:

  • Issue close_status updated to: Fixed
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @kevin**: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
ralph commented 2019-04-25 03:21:04 +00:00
Copy link

\ó/

\ó/
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
announcement

   
authentication

Authentication related issues

  
automate

   
aws

Issues related to Amazon Web Services

  
backlog

Tasks that will take longer then ~4 hours to do

  
blocked

Issue is blocked

  
bodhi

Issues with Bodhi

  
ci

Continuous Integration

  
Closed As
Duplicate
Closed with the reason of Duplicate

  
Closed As
Fixed
Closed with the reason of Fixed

  
Closed As
Fixed with Explanation
Closed with the reason of Fixed with Explanation

  
Closed As
Initiative Worthy
Closed with the reason of Initiative Worthy

  
Closed As
Insufficient data
Closed with the reason of Insufficient data

  
Closed As
Invalid
Closed with the reason of Invalid

  
Closed As
Spam
Closed with the reason of Spam

  
Closed As
Upstream
Closed with the reason of Upstream

  
Closed As
Will Not or Can Not fix
Closed with the reason of Will Not/Can Not fix

  
cloud

Items in FedoraInfraCloud or COmmunishift

  
communishift

issues/questions about os.edorainfracloud.org ( Community OpenShift)

  
copr

COPR system (run by other team)

  
database

Issues related to databases

  
deprecated

Tools which Infrastructure may not be able to fix

  
dev

Tasks requiring some dev work

  
discourse

outsourced tool

  
dns

Changes or problems with DNS

  
downloads

rsync,dl.fp.o,AWS,torrents

  
easyfix

   
epel

Issues relating to epel

  
factory2

Generic issues for the factory2 team

  
firmitas

   
gitlab

   
greenwave

Issues with greenwave

  
hardware

Problem is with Fedora Infrastructure Owned/Leased Hardware

  
help wanted

   
high-gain

task that gets us a lot / is important / makes many people happy

  
high-trouble

task that is complex/long/difficult

  
iad2

Something to do with the iad2 datacenter

  
koji

Issues with the build system

  
koschei

Items needing Koschei team

  
lists

issues with lists

  
low-gain

tasks that gets us little / isn't very important / makes only 1 person or few happy

  
low-trouble

task that is easy/short

  
mbs

Issues with mbs.fedoraproject.org

  
medium-gain

task that gets us some / is somewhat important / makes some people happy

  
medium-trouble

task that is medium complex / difficult

  
mini-initiative

Something that is bigger than one person but not a full initiative

  
mirrorlists

Way to tell systems where downloads are

  
monitoring

   
Needs investigation

   
notifier

   
odcs

On Demand Compose Service issues

  
OpenShift

Issues with OpenShift

  
ops

ops problem now...

  
OSBS

OpenShift Build System issues in Fedora

  
outage

   
packager_workflow_blocker

Blocks the packager workflow

  
pagure

Issues with pagure.io

  
permissions

Items which need permissions set in outside tools

  
Priority
Needs Review
Priority of Needs Review

  
Priority
Next Meeting
Priority of Next Meeting

  
Priority
🔥 URGENT 🔥
Priority of 🔥 URGENT 🔥

  
Priority
Waiting on Assignee
Priority of Waiting on Assignee

  
Priority
Waiting on External
Priority of Waiting on External

  
Priority
Waiting on Reporter
Priority of Waiting on Reporter

  
rabbitmq

issues with the message broker

  
rdu-cc

Items doing with RDU Community Cage

  
release-monitoring

release-monitoring.org (Anitya)

  
releng

For problems which should be in the releng ticket system

  
repoSpanner

Issues with repoSpanner

  
request-for-resources

   
s390x

The secondary architecture hardware and problems related with it

  
security

   
SMTP

Email issues outside of lists (DMARC, SPF, aliases)

  
src.fp.o

Issues related to src.fedoraproject.org

  
staging

Issues in staging

  
taiga

outsourced tool

  
unfreeze

Patches to be applied after freeze is lifted

  
waiverdb

Issues with waiverdb

  
websites-general

General items with a website focus

  
wiki

Issues with the Wiki

No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As
Will Not or Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Infrastructure/fedora-infrastructure#7735
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?