This is (probably) my fault. I played a bit with ipv6 && libvirt, and I rebooted the machine, and it doesn't boot up now :-( sorry for the noise.
If there's some console (VPN?) access that we could use to fix such problems within our (CPT) team?
Pavel
On Monday, April 26, 2021 10:06:41 PM CEST Nagios Monitoring User wrote:
***** Nagios *****
Notification Type: PROBLEM Host: vmhost-x86-copr01.rdu-cc.fedoraproject.org State: DOWN Address: vmhost-x86-copr01.rdu-cc.fedoraproject.org Info: CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. Source: noc01.iad2.fedoraproject.org
Date/Time: Mon Apr 26 20:06:41 GMT 2021
On Mon, 26 Apr 2021 at 16:22, Pavel Raiskup praiskup@redhat.com wrote:
This is (probably) my fault. I played a bit with ipv6 && libvirt, and I rebooted the machine, and it doesn't boot up now :-( sorry for the noise.
If there's some console (VPN?) access that we could use to fix such problems within our (CPT) team?
There is currently no way to get to the consoles for these systems. That is part of the bring up of that environment.
Pavel
On Monday, April 26, 2021 10:06:41 PM CEST Nagios Monitoring User wrote:
***** Nagios *****
Notification Type: PROBLEM Host: vmhost-x86-copr01.rdu-cc.fedoraproject.org State: DOWN Address: vmhost-x86-copr01.rdu-cc.fedoraproject.org Info: CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. Source: noc01.iad2.fedoraproject.org
Date/Time: Mon Apr 26 20:06:41 GMT 2021
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Mon, 26 Apr 2021 at 16:44, Stephen John Smoogen smooge@gmail.com wrote:
On Mon, 26 Apr 2021 at 16:22, Pavel Raiskup praiskup@redhat.com wrote:
This is (probably) my fault. I played a bit with ipv6 && libvirt, and I rebooted the machine, and it doesn't boot up now :-( sorry for the noise.
If there's some console (VPN?) access that we could use to fix such problems within our (CPT) team?
There is currently no way to get to the consoles for these systems. That is part of the bring up of that environment.
I will drive into the datacenter tomorrow to put a console on and try to rescue the box. I will have to force a root login via USB key or similar.
Pavel
On Monday, April 26, 2021 10:06:41 PM CEST Nagios Monitoring User wrote:
***** Nagios *****
Notification Type: PROBLEM Host: vmhost-x86-copr01.rdu-cc.fedoraproject.org State: DOWN Address: vmhost-x86-copr01.rdu-cc.fedoraproject.org Info: CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. Source: noc01.iad2.fedoraproject.org
Date/Time: Mon Apr 26 20:06:41 GMT 2021
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-- Stephen J Smoogen.
On Monday, April 26, 2021 10:45:18 PM CEST Stephen John Smoogen wrote:
On Mon, 26 Apr 2021 at 16:44, Stephen John Smoogen smooge@gmail.com wrote:
On Mon, 26 Apr 2021 at 16:22, Pavel Raiskup praiskup@redhat.com wrote:
This is (probably) my fault. I played a bit with ipv6 && libvirt, and I rebooted the machine, and it doesn't boot up now :-( sorry for the noise.
If there's some console (VPN?) access that we could use to fix such problems within our (CPT) team?
There is currently no way to get to the consoles for these systems. That is part of the bring up of that environment.
I will drive into the datacenter tomorrow to put a console on and try to rescue the box. I will have to force a root login via USB key or similar.
Meh, sorry for complications, I'll try to be much more careful next time.
Perhaps you don't have to hurry up for the fix since we have the rest of the stack (3 more boxes) that we still have to setup via ansible.. So there's a chance that we'll break something else :-(.
I mean, because ipv4 addresses (32+ for each hypervisor) aren't available I'm trying other things. Qemu port-forwarding to libvirt guests didn't work for me (but I'll try better), ipv6 guest access did not work either (I'll retry as well), so perhaps we'll have to try iptables hacks or setup VPN(s) eventually. I'm afraid all those configuration tasks aren't really that trivial to be 100% sure that no mistake happens :-(.
Pavel
Pavel
On Monday, April 26, 2021 10:06:41 PM CEST Nagios Monitoring User wrote:
***** Nagios *****
Notification Type: PROBLEM Host: vmhost-x86-copr01.rdu-cc.fedoraproject.org State: DOWN Address: vmhost-x86-copr01.rdu-cc.fedoraproject.org Info: CHECK_NRPE STATE CRITICAL: Socket timeout after 30 seconds. Source: noc01.iad2.fedoraproject.org
Date/Time: Mon Apr 26 20:06:41 GMT 2021
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedorapro... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
-- Stephen J Smoogen.
On Tue, Apr 27, 2021 at 08:01:18AM +0200, Pavel Raiskup wrote:
Meh, sorry for complications, I'll try to be much more careful next time.
Perhaps you don't have to hurry up for the fix since we have the rest of the stack (3 more boxes) that we still have to setup via ansible.. So there's a chance that we'll break something else :-(.
I mean, because ipv4 addresses (32+ for each hypervisor) aren't available I'm trying other things. Qemu port-forwarding to libvirt guests didn't work for me (but I'll try better), ipv6 guest access did not work either (I'll retry as well), so perhaps we'll have to try iptables hacks or setup VPN(s) eventually. I'm afraid all those configuration tasks aren't really that trivial to be 100% sure that no mistake happens :-(.
I would think a bridge would work fine and just assign the guests ipv6 addresses? But I agree it will take some testing/tweaking. ;(
kevin
On Tuesday, April 27, 2021 10:08:55 PM CEST Kevin Fenzi wrote:
On Tue, Apr 27, 2021 at 08:01:18AM +0200, Pavel Raiskup wrote:
Meh, sorry for complications, I'll try to be much more careful next time.
Perhaps you don't have to hurry up for the fix since we have the rest of the stack (3 more boxes) that we still have to setup via ansible.. So there's a chance that we'll break something else :-(.
I mean, because ipv4 addresses (32+ for each hypervisor) aren't available I'm trying other things. Qemu port-forwarding to libvirt guests didn't work for me (but I'll try better), ipv6 guest access did not work either (I'll retry as well), so perhaps we'll have to try iptables hacks or setup VPN(s) eventually. I'm afraid all those configuration tasks aren't really that trivial to be 100% sure that no mistake happens :-(.
I would think a bridge would work fine and just assign the guests ipv6 addresses? But I agree it will take some testing/tweaking. ;(
Indeed, I was able to configure one VM like that now - so I obviously did something wrong before (I tested F33, now with F34, but I doubt this makes any difference). So ... I think I shouldn't break the hypervisors anymore :-).
Pavel
infrastructure@lists.fedoraproject.org