Re: [foreman-dev] Koji Outage

I can confirm that rsync port was not in the SG, added and Ewoud tested this. Thanks. What happened is in a summary in a separate thread. Let's carry on discussion there. But the good thing about this failure is we have been able to recover quite fast. Next time this happens I think we are able

Re: [foreman-dev] Koji Outage

Turns out it was started in a new security group which didn't allow rsync. lzap fixed that now. On Sat, Oct 28, 2017 at 08:09:39PM +0200, Ewoud Kohl van Wijngaarden wrote: It looks like the rsync service isn't started causing our promotion pipeline to fail. Could you have a look? On Thu, Oct

Re: [foreman-dev] Koji Outage

Here is an update. Restart did not help, we stopped the instance and I am following this guide to create new AMI and start it: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami-ebs.html Image which is now pending completion is called ami-2ecd6b54 and it has both root EBS volume

Re: [foreman-dev] Koji Outage

Likely a hardware failure according to notification, our instance is not responding. We are trying restart first. *** EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance associated with this event in the us-east-1 region. Due to this degradation, your

[foreman-dev] Koji Outage

Our Koji is currently down from a web perspective and ssh access. Please don't merge anything further to -packaging until we've resolved this. All actions requiring Koji repositories for testing or actions in Koji cannot be performed. If Bryan or Lukas (since I am not sure who has AWS access to

Re: [foreman-dev] Koji outage on Sunday

The kojibuilder was snapshotted live, so it is doing 20-minutes fsck of root volume on first boot. LZ On Thu, Jun 8, 2017 at 1:59 PM, Bryan Kearney wrote: > Thanks. Any idea why I could not ssh into the instance when it was launched > in the old security group? > > -- bk >

Re: [foreman-dev] Koji outage on Sunday

Bryan, I terminated builder2 it was running in incorrect security group. You can delete it. The one we need to use is called "launch-wizard-1" - this is where both koji and builder3 which I spawned today are. I set the rules to accept all TCP/UDP connections in this group (ssh/https from outside

[foreman-dev] Koji outage on Sunday

Hey, I had to brought Koji services offline, I expect them to come back in an hour, we are trying to move the data to different EC2 instance. This is just a test and if the new instance will work fine, we will do the switchover during the week. Sorry for inconvenience, please resubmit your jobs