action #27883
closedaction #12092: [tools][dashboard][Feature] - make openQA show when a bug is marked as "RESOLVED FIXED" but still in the product
[tools] Deploy bug fetcher on proper VM
100%
Description
This runs on dheidler's work station, but is crucial for QA reviews meanwhile. So this needs proper care. Either QA has hardware for this or a VM needs to be setup (possibly on skynet)
Updated by coolo over 6 years ago
skycastle is the name of the cloud - sorry, I'll be back!
Updated by okurz over 6 years ago
:D I already got interested where SUSE runs it's own skynet. You know, meant to be just a small, uninteresting, self-aware thing ;)
I recommend a VM on qamaster.qa, adding nicksinger as watcher to ticket.
Updated by okurz over 6 years ago
- Related to action #28711: "hermes" died for osd added
Updated by okurz over 6 years ago
the "deploy" part should then include "hermes", the IRC bot forwarding AMQP events to #openqa-events and #openqa-test using suse_msg
Updated by coolo over 6 years ago
- Subject changed from Deploy bug fetcher on proper VM to [tools] Deploy bug fetcher on proper VM
- Assignee set to dheidler
- Target version changed from Ready to Current Sprint
I talked to Bernhard and he said cloud.suse.de is better suited for such non-critical stuff atm. The data on it might get lost, but so is the data on the current machine :)
And cloud.suse.de is full self service - so I talked to dheidler, who agreed to take over the task next time he's in the office.
Updated by okurz over 6 years ago
I hope you didn't talk to Bernhard and Dominik today before your comment ;)
Updated by dheidler over 6 years ago
- Status changed from New to In Progress
- Assignee changed from dheidler to okurz
- % Done changed from 0 to 50
I moved the hermes irc bot and the openqa_bugfetcher (for osd and o3) to new.cloud.suse.de.
The instance is called openqa-service and has the IP 10.162.187.162.
Things left to be done:
Currently I only use an unpriviged bugzilla-account for osc and o3 bug fetching.
This is ok for o3, but for osd we need an account with access to internal bugzilla bugs.
@okurz: I think, you have access to such an account, don't you?
Updated by okurz over 6 years ago
Yes, I have such an account. I can eventually do the changes myself or if someone wants to go forward I can provide the credentials on request personally.
Updated by okurz over 6 years ago
how to access the machine? root seems to not allow password authentication? You could add my ssh public key for the root user or enable the password authentication.
Updated by okurz over 6 years ago
- Assignee changed from okurz to dheidler
sent you the credentials for the bugzilla account as well
Updated by dheidler over 6 years ago
enabled password-based login for the machine
Updated by szarate over 6 years ago
Dominik, what's needed to set this one to resolved?
Updated by dheidler over 6 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
I think, we're done here.
Updated by okurz about 6 years ago
- Status changed from Resolved to In Progress
I did not find a documentation about that instance elsewhere. Also I can not resolve it by any name, just IP. I guess a reverse DNS entry is missing (at least). Shouldn't we also at least mention it on https://wiki.microfocus.net/index.php/OpenQA#Additional_Servers ?
Updated by dheidler about 6 years ago
- Status changed from In Progress to Resolved
Now I'm using a VM provided by the INFRA team.
It has dns (and reverse dns) name openqa-service.suse.de.