yahoo-eng-team team mailing list archive

[Christian Grabowski <2104179@xxxxxxxxxxxxxxxxxx>]

Adding cloud-init as this seems to be an issue coming from its execution
itself.

** 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/2104179

Title:
  Node deployment fails due to segfault

Status in cloud-init:
  New
Status in MAAS:
  New

Bug description:
  Describe the bug: 
  On virtual maas in solutionsqa labs, a maas run failed because one of the nodes did not deploy. In the syslogs I see

  
  log/syslog:Mar 22 14:35:45 infra3 maas-machine[26057]: [node3] cloud-init[1626]: finish: cmd-install/stage-curthooks/builtin/cmd-curthooks/configuring-bootloader: SUCCESS: configuring target system bootloader
  log/syslog:Mar 22 14:35:45 infra3 maas-machine[26057]: [node3] cloud-init[1626]: finish: cmd-install/stage-curthooks/builtin/cmd-curthooks: SUCCESS: curtin command curthooks
  log/syslog:Mar 22 14:35:45 infra3 maas-machine[26057]: [node3] kernel: [  390.844192] show_signal_msg: 6 callbacks suppressed 
  log/syslog:Mar 22 14:35:45 infra3 maas-machine[26057]: [node3] kernel: [  390.844199] python3[1628]: segfault at 0 ip 0000561d7cc4a445 sp 00007ffeb251deb0 error 6 in python3.10[561d7cb42000+2b5000]
  log/syslog:Mar 22 14:35:45 infra3 maas-machine[26057]: [node3] kernel: [  390.844220] Code: e3 f3 0f 1e fa 4c 8b 5c 24 08 4d 63 c4 4b 8b 3c c3 48 85 ff 0f 84 24 9d f0 ff 45 0f b7 65 00 48 83 07 01 4d 8d 4e 08 4c 89 e8 <49> 89 3e 44 8b 94 24 50 01 00 00 49 8d 75 02 4c 8d 35 91 49 43 00
  log/syslog:Mar 22 14:35:46 infra3 maas-machine[26057]: [node3] cloud-init[1626]: 2025-03-22 14:35:46,032 - cc_scripts_user.py[WARNING]: Failed to run module scripts_user (scripts in /var/lib/cloud/instance/scripts)
  log/syslog:Mar 22 14:35:46 infra3 maas-machine[26057]: [node3] cloud-init[1626]: 2025-03-22 14:35:46,032 - log_util.py[WARNING]: Running module scripts_user (<module 'cloudinit.config.cc_scripts_user' from '/usr/lib/python3/dist-packages/cloudinit/config/cc_scripts_user.py'>) failed

  
  Steps to reproduce: 
  We have only hit this once so I do not have a reliable way to reproduce.

  Expected behavior (what should have happened?):
  Node should have deployed

  Actual behavior (what actually happened?): 
  Node failed to deployed

  MAAS version and installation type (deb, snap): 
  snap 3.6.0~rc5-17537-g.0b0ee2c2e

  
  MAAS setup (HA, single node, multiple regions/racks):
  HA

  
  Host OS distro and version:
  Jammy

  
  Additional context:
  testrun: https://solutions.qa.canonical.com/testruns/42931efd-03c5-4103-be2b-d87294ad36cb

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2104179/+subscriptions