failure: sudo failed with stderr: "sudo: unable to resolve host autopkgtest"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Auto Package Testing |
New
|
Undecided
|
Unassigned |
Bug Description
This is biting us again?
Note that:
0. The test log says `git checkout: 699e7f9f ssh-setup/nova: explicitely set 'fqdn' in cloud-init` which is the very commit that should prevent this failure from happening. :(
1. This is an i386 test, but the failure happened very early, so maybe the fact that it's i386 is not relevant. *Unless* we're running some early command like `dpkg --add-architecture i386` and that happens to be racy with cloud-init. E.g. I don't see us doing stuff like `cloud-init status --wait` in setup-testbed.
2. This is a Xenial test. Xenial has an older cloud-init:
cloud-init | 21.1-19-
cloud-init | 24.1.3-
cloud-init | 24.1.3-
cloud-init | 24.1.3-
cloud-init | 24.1.3-0ubuntu3 | noble |
cloud-init | 24.1.3-0ubuntu3.2 | noble-proposed |
Does the fqdn setting behave differently there? Does it work at all?
Note that this is about an unsupported configuration (xenial/i386 is not ESM supported and there is no commercial offering for it). It may still be worth doing a timeboxed investigation, just trying to reproduce the issue as it happened in [1]. This is because we _may_ have a bug that could bite in other configurations.
[1] https:/ /autopkgtest. ubuntu. com/results/ autopkgtest- xenial/ xenial/ i386/u/ ubuntu- advantage- tools/20240524_ 123321_ 36163@/ log.gz