This server isn't working and we can't figure out why not. It's
a problem for openQA because we copy the host's DNS config into
'advanced networking' openQA guests, and then when we do a
FreeIPA deployment test, it picks up both DNS servers, tries to
confirm both work, and fails. So we need to take ns03 out until
it's fixed.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We don't have ipv6 routing setup yet, but are scheduled to work on that
soon. To get ready for that, lets add ipv6 addresses to the (few)
machines that will actually need them.
We do not want to add ipv6 to all hosts. The vast majority of them never
need to talk to the outside world directly and shouldn't have a ipv6
address that can do this.
These few hosts are ones with external nat mappings where it is
desireable that they be able to handle ipv6 connections.
Note that we also do NOT want to add any of these to dns until
they are known working. We also will likely have to adjust nftables
to allow the services on ipv6 that we do on ipv4 (if they make sense).
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This was done in d97f99c for coreos-ostree-importer. Here I add a
comment with more context to the the coreos-ostree-importer one and
add the same config to the fedora-ostree-pruner.
There's this annoying pattern where the NFS mount fails on boot
and then the worker services all start up and take jobs, but they
instafail because the share isn't there.
Ideally we could handle this very easily with Restart= directives
but systemd has...*opinions* about this:
https://github.com/systemd/systemd/issues/4468https://github.com/systemd/systemd/issues/1312
so we have to do some fairly awkward hacks to just express:
* Retry the NFS mount if it fails
* Don't start the workers unless the NFS mount is up
* Retry the workers after a while if they were blocked
It's ugly, but in testing this same config on one worker it seems
to work...
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This is to disambiguate 'ns02'. Right now we have ns02.fedoraproject.org
and also ns02.rdu3.fedoraproject.org. After this we will just have a
ns02 and a ns03.rdu3 server.
This will also allow us to more easily change whois/glue records.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
When looking at the mailman alert I found out that it's using
nagios-plugins-http, which is not installed by default. So let's add it
to list of installed packages.
These are various machines that are not yet deployed, or no longer exist
in rdu3 (though they did in iad2). This should clean up nagios
a fair bit and when/if we redeploy these we can add them back in.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
