@thinktwo nothing missing, the fix is entirely in systemd. Please open
a new bug and put in your steps so we can track down what's going wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815254
>From what understand the fix in systemd was release with 18.04.3, but i
still seem to hit this with cloud-init 19.2-36-g059d049c-
0ubuntu2~18.04.1 on 18.04.3. Are something still missing in cloud-init
to resolve this?
--
You received this bug notification because you are a member of Ubuntu
The systemd SRU has landed in Bionic and later.
This bug can be closed as fix released once cloud-init v.19.2.10 or
later.
** Changed in: cloud-init (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Chad Smith (chad.smith)
--
This will require no work from cloud-init as it is a systemd related
fix. Cloud-init just needs to be aware of when the existing systemd SRUs
land in Bionic, Disco and Eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have verified that Bionic and Disco work with the aforementioned SRU
(and have attached logs to
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835581). Eoan
SRU is not yet queued for SRU verification with a fix because an
existing SRU is already in the pipeline there and needs to land
A systemd SRU [1] has started with the branch referenced in comment 6
included in it. It would be good to verify this actually fixes this
issue and reply on the SRU bug.
[1] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1835581
--
You received this bug notification because you are a
This issue is resolved by the following WIP branch:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/370152
Expectation is that this branch will be included in a systemd SRU: bug:
#1835581.
--
You received this bug notification because you are a member of Ubuntu
This issue is resolved by the following WIP branch:
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/370152
Expectation is that this branch will be included in a systemd SRU:
LP:#1835581.
--
You received this bug notification because you are a member of Ubuntu
filed a related bug against netplan for discussion about how best to
express this type of configuration
https://bugs.launchpad.net/netplan/+bug/1834956
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, this is easily reproduced by adding a single static IP in the same
subnet as the IP that comes from dhcp'ing on the interface.
For example, if you launch an instance with a 10.0.0./24 subnet, the
dhcp IP is something like 10.0.0.4
You can login and
curl -H Metadata:true
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815254
Title:
ip addr show output:
https://paste.ubuntu.com/p/3gHdFzkrrQ/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815254
Title:
Azure multiple ips prevent access to metadata service
To manage
12 matches
Mail list logo
