search

canonical / cloud-init

Official upstream for the cloud-init: cloud instance initialization
https://cloud-init.io/
Other
2.87k stars 856 forks source link

maas wily deployment to HP Proliant m400 arm64 server cartridge fails #2586

Closed ubuntu-server-builder closed 1 year ago

ubuntu-server-builder commented 1 year ago

This bug was originally filed in Launchpad as LP: #1499869

Launchpad details 
affected_projects = ['curtin', 'cloud-init (Ubuntu)', 'linux (Ubuntu)', 'linux (Ubuntu Vivid)', 'cloud-init (Ubuntu Wily)', 'linux (Ubuntu Wily)']
assignee = smoser
assignee_name = Scott Moser
date_closed = 2017-04-10T23:16:10.838068+00:00
date_created = 2015-09-25T20:05:36.135713+00:00
date_fix_committed = 2017-04-10T23:16:10.838068+00:00
date_fix_released = 2017-04-10T23:16:10.838068+00:00
id = 1499869
importance = high
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1499869
milestone = None
owner = blake-rouse
owner_name = Blake Rouse
private = False
status = fix_released
submitter = craig.magina
submitter_name = Craig Magina
tags = ['patch', 'verification-done-vivid']
duplicates = []

Launchpad user Craig Magina(craig.magina) wrote on 2015-09-25T20:05:36.135713+00:00

This is the error seen on the console:

[ 64.149080] cloud-init[834]: 2015-08-27 15:03:29,289 - util.py[WARNING]: Failed fetching metadata from url http://10.229.32.21/MAAS/metadata/curtin [ 124.513212] cloud-init[834]: 2015-09-24 17:23:10,006 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2427570/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x7f7faa4b70>, 'Connection to 169.254.169.254 timed out. (connect timeout=50.0)'))] [ 124.515570] cloud-init[834]: 2015-09-24 17:23:10,007 - DataSourceEc2.py[CRITICAL]: Giving up on md from ['http://169.254.169.25/2009-04-04/meta-data/instance-id'] after 2427570 seconds [ 124.531624] cloud-init[834]: 2015-09-24 17:23:10,024 - url_helper.py[WARNING]: Calling 'http:///latest/meta-data/instance-id' failed [0/120s]: bad status code [404]

This times out eventually and the node is left at the login prompt. I can install wily via netboot without issue and some time back, wily was deployable to this node from MAAS.

ubuntu-server-builder commented 1 year ago

Launchpad user Craig Magina(craig.magina) wrote on 2015-09-25T20:08:01.933887+00:00

The version of MAAS is 1.8.2.

ubuntu-server-builder commented 1 year ago

Launchpad user Blake Rouse(blake-rouse) wrote on 2015-09-25T20:19:01.646336+00:00

This is either because curtin is not installing the cloud configuration for MAAS, cloud-init is not reading the correct config, or cloud-init cannot talk to MAAS.

I believe cloud-init changed to python-oauthlib instead of python-oauth so that might be the issue. Going to target to both curtin and cloud-init as well just to make sure the appropriate eyes see this.

ubuntu-server-builder commented 1 year ago

Launchpad user Craig Magina(craig.magina) wrote on 2015-09-29T17:00:21.080520+00:00

I can deploy wily to a virtual machine and an x86 based node without issue using the same MAAS that fails when deploying to the m400 node with the error above.

ubuntu-server-builder commented 1 year ago

Launchpad user Craig Magina(craig.magina) wrote on 2015-09-29T18:56:25.961913+00:00

Launchpad attachments: Failing boot log

ubuntu-server-builder commented 1 year ago

Launchpad user Craig Magina(craig.magina) wrote on 2015-09-29T20:48:46.052323+00:00

Cloud-init is getting the wrong time because of this error:

[ 14.726283] hctosys: unable to open rtc device (rtc0)

What that means is the RTC_DRV_XGENE kernel config option was changed to 'm', this needs to be built-in in order for the device to be available for hctosys.

ubuntu-server-builder commented 1 year ago

Launchpad user Brad Figg(brad-figg) wrote on 2015-09-29T21:00:06.494507+00:00

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1499869

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

ubuntu-server-builder commented 1 year ago

Launchpad user Scott Moser(smoser) wrote on 2015-09-29T21:10:20.756694+00:00

cloud-init changes caused issues when "fixing" timestamp for oauth on systems with bad clock. change here is to fix that. I'll upload later. Launchpad attachments: cloud-init fix diff

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2015-09-30T03:34:56.981625+00:00

This bug was fixed in the package cloud-init - 0.7.7~bzr1147-0ubuntu1

cloud-init (0.7.7~bzr1147-0ubuntu1) wily; urgency=medium

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2015-10-04T08:58:36.585794+00:00

This bug was fixed in the package linux - 4.2.0-14.16

linux (4.2.0-14.16) wily; urgency=low

[ Tim Gardner ]

ubuntu-server-builder commented 1 year ago

Launchpad user Luis Henriques(henrix) wrote on 2015-10-08T14:48:34.779609+00:00

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

ubuntu-server-builder commented 1 year ago

Launchpad user Craig Magina(craig.magina) wrote on 2015-10-16T20:57:52.342751+00:00

Vivid deployment succeeded with no issues.

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2015-10-20T16:29:17.909142+00:00

This bug was fixed in the package linux - 3.19.0-31.36

linux (3.19.0-31.36) vivid; urgency=low

[ Luis Henriques ]

linux (3.19.0-31.35) vivid; urgency=low

[ Brad Figg ]