New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS issues on Azure #356
Comments
That's odd. What does Hmm, but clearly this has to be working on RHCOS. One difference I can think of is that RHCOS does check-in from the initrd, though I don't think checking in would be related to DNS. |
I've included
|
Ahhh hmm yeah, that's a big delta. I don't quite remember now why we don't do this in FCOS too. Maybe we expected it to be unnecessary with the switch to NM in the initrd? |
Thats a showstopper because we have to reboot each machine a few times manually before it has an internet connection. Is it a big task to resolve this in the official fcos image? |
@jlebon I think coreos/ignition-dracut#119 is related. |
Hi folks. Do you have any updates for this one? |
cross referencing this with #394 |
Hitting this issue as well. Any updates? |
yes, once coreos/ignition-dracut#159 and coreos/fedora-coreos-config#310 are merged and into a release we think this should be taken care of. |
Hi, FYI, I used this in the ignition to work around the issue. Seems to be working: systemd:
units:
- name: azure-restart-network.service
enabled: true
contents: |
[Service]
Type=oneshot
ExecStart=/bin/bash -c '\
/usr/bin/cp /run/initramfs/state/etc/resolv.conf /etc/resolv.conf; \
/usr/bin/systemctl restart NetworkManager'
[Install]
WantedBy=multi-user.target |
@jomeier @simongottschlag - care to test https://builds.coreos.fedoraproject.org/prod/streams/testing-devel/builds/31.20200323.20.0/x86_64/fedora-coreos-31.20200323.20.0-azure.x86_64.vhd.xz to see if that fixes the problem? |
I'm having issues deploying our production VMs right now (capacity in West Europe), meaning I need to prioritise that before tests. Sorry! |
Strike! I will try that out today. Give me a few hours, please. |
@dustymabe @vrutkovs @LorbusChris Ok guys ... it looks good. I installed OKD 4.4 successfully without manual interaction from my side. Everything is green in the web ui -> ok. For your information: I had to resize, convert and upload the FCOS test image to Azure but I'm sure thats expected behaviour for this test. I used a helper VM which I patched in the OKD installer which did the work. Good job ! |
We are now using NetworkManager in the initramfs and also propagating network information from the initramfs (kargs) when appropriate, which we think fixes this issue. See #394 (comment) and the preceding discussion for more details. |
Issue Report
Bug
Fedora CoreOS Version
31.20200113.3.1
Expected Behavior
Working DNS
Actual Behavior
When spawning FCOS machines on Azure there is no DNS. The machines do seem to have working networking otherwise.
Reproduction Steps
Other Information
I haven't managed to get a machine booted on Azure via manual spawning in the CLI or kola that have working DNS.
The text was updated successfully, but these errors were encountered: