** Description changed: Given this command line: BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily iscsi_target_ip=2001:67c:1562:8010::2:1 iscsi_target_port=3260 iscsi_initiator=kearns ip=::::kearns:BOOTIF ro root=/dev/disk/by-path/ip-2001:67c:1562:8010::2:1:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://maas-boot-vm-xenial.dt-maas:5240/MAAS/metadata/latest/by-id/8w4gkk/?op=get_preseed log_host=maas-boot-vm-xenial.dt-maas log_port=514 --- console=ttyS1 BOOTIF=01-38:63:bb:43:b8:bc Where: root@ubuntu:~# host maas-boot-vm-xenial.dt-maas maas-boot-vm-xenial.dt-maas is an alias for maas-boot-vm-xenial.maas. maas-boot-vm-xenial.maas has address 10.246.0.5 maas-boot-vm-xenial.maas has IPv6 address 2001:67c:1562:8010::2:1 cloud-init takes "forever" to run, because there is a 25 second pause every time it tries to report status to the maas server. This is because hostname resolution assumes a working dbus, and takes 25 seconds to timeout on connecting to dbus to get the answer. + + Related bugs: + * bug 1629868: Reformatting of ephemeral drive fails on resize of Azure VM
** Description changed: Given this command line: BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily iscsi_target_ip=2001:67c:1562:8010::2:1 iscsi_target_port=3260 iscsi_initiator=kearns ip=::::kearns:BOOTIF ro root=/dev/disk/by-path/ip-2001:67c:1562:8010::2:1:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://maas-boot-vm-xenial.dt-maas:5240/MAAS/metadata/latest/by-id/8w4gkk/?op=get_preseed log_host=maas-boot-vm-xenial.dt-maas log_port=514 --- console=ttyS1 BOOTIF=01-38:63:bb:43:b8:bc Where: root@ubuntu:~# host maas-boot-vm-xenial.dt-maas maas-boot-vm-xenial.dt-maas is an alias for maas-boot-vm-xenial.maas. maas-boot-vm-xenial.maas has address 10.246.0.5 maas-boot-vm-xenial.maas has IPv6 address 2001:67c:1562:8010::2:1 cloud-init takes "forever" to run, because there is a 25 second pause every time it tries to report status to the maas server. This is because hostname resolution assumes a working dbus, and takes 25 seconds to timeout on connecting to dbus to get the answer. Related bugs: - * bug 1629868: Reformatting of ephemeral drive fails on resize of Azure VM + * bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM ** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1629868 Title: times out because of no dbus Status in cloud-init: New Status in MAAS: New Status in cloud-init package in Ubuntu: New Bug description: Given this command line: BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily iscsi_target_ip=2001:67c:1562:8010::2:1 iscsi_target_port=3260 iscsi_initiator=kearns ip=::::kearns:BOOTIF ro root=/dev/disk/by-path/ip-2001:67c:1562:8010::2:1:3260-iscsi-iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily-lun-1 overlayroot=tmpfs cloud-config-url=http://maas-boot-vm-xenial.dt-maas:5240/MAAS/metadata/latest/by-id/8w4gkk/?op=get_preseed log_host=maas-boot-vm-xenial.dt-maas log_port=514 --- console=ttyS1 BOOTIF=01-38:63:bb:43:b8:bc Where: root@ubuntu:~# host maas-boot-vm-xenial.dt-maas maas-boot-vm-xenial.dt-maas is an alias for maas-boot-vm-xenial.maas. maas-boot-vm-xenial.maas has address 10.246.0.5 maas-boot-vm-xenial.maas has IPv6 address 2001:67c:1562:8010::2:1 cloud-init takes "forever" to run, because there is a 25 second pause every time it tries to report status to the maas server. This is because hostname resolution assumes a working dbus, and takes 25 seconds to timeout on connecting to dbus to get the answer. Related bugs: * bug 1611074: Reformatting of ephemeral drive fails on resize of Azure VM To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1629868/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
