| 2023-02-24 06:58:48 |
Nobuto Murata |
bug |
|
|
added bug |
| 2023-02-24 06:59:40 |
Nobuto Murata |
attachment added |
|
Screenshot from 2023-02-24 15-59-15.png https://bugs.launchpad.net/maas/+bug/2008454/+attachment/5649726/+files/Screenshot%20from%202023-02-24%2015-59-15.png |
|
| 2023-02-24 07:00:58 |
Nobuto Murata |
attachment added |
|
next-llama.log https://bugs.launchpad.net/maas/+bug/2008454/+attachment/5649735/+files/next-llama.log |
|
| 2023-02-24 07:01:56 |
Nobuto Murata |
attachment added |
|
quick-gopher.log https://bugs.launchpad.net/maas/+bug/2008454/+attachment/5649736/+files/quick-gopher.log |
|
| 2023-03-01 03:07:31 |
Nobuto Murata |
summary |
Commissioning intermittently fails with No such file or directory: '/var/run/lldpd.socket' |
Commissioning fails when a node is rebooted in the middle - No such file or directory: '/var/run/lldpd.socket' |
|
| 2023-03-01 03:09:54 |
Nobuto Murata |
description |
maas: 1:3.3.0-13159-g.1c22f7beb-0ubuntu1~22.04.1
For example in my test bed, 2 out of 7 machines fail at commissioning with the same error.
[maas-capture-lldpd]
Traceback (most recent call last):
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 53, in <module>
lldpd_capture("/var/run/lldpd.socket", 60)
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 41, in lldpd_capture
time_ref = getmtime(reference_file)
File "/usr/lib/python3.8/genericpath.py", line 55, in getmtime
return os.stat(filename).st_mtime
FileNotFoundError: [Errno 2] No such file or directory: '/var/run/lldpd.socket'
Interestingly enough, I only see the "Installing apt packages for 20-maas-01-install-lldpd" message from the 5 succeeded machines in rsyslog although all 7 machines should have an identical commissioning configuration.
$ sudo grep -i 'Installing apt packages for 20-maas-01-install-lldpd' -l /var/log/maas/rsyslog/*/*/messages
/var/log/maas/rsyslog/crack-chow/2023-02-22/messages
/var/log/maas/rsyslog/enough-camel/2023-02-22/messages
/var/log/maas/rsyslog/open-bee/2023-02-22/messages
/var/log/maas/rsyslog/quick-gopher/2023-02-22/messages
/var/log/maas/rsyslog/wanted-louse/2023-02-22/messages |
maas: 1:3.3.0-13159-g.1c22f7beb-0ubuntu1~22.04.1
When a node is rebooted in the middle of commissioning with any reasons (a corner case indeed), it seems that already completed commissioning scripts are skipped thus the process fails since lldpd installation is not going to happen in the next boot.
I'm not 100% sure but it looks like the behavior is changed between 3.2 and 3.3.
[maas-capture-lldpd]
Traceback (most recent call last):
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 53, in <module>
lldpd_capture("/var/run/lldpd.socket", 60)
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 41, in lldpd_capture
time_ref = getmtime(reference_file)
File "/usr/lib/python3.8/genericpath.py", line 55, in getmtime
return os.stat(filename).st_mtime
FileNotFoundError: [Errno 2] No such file or directory: '/var/run/lldpd.socket'
Interestingly enough, I only see the "Installing apt packages for 20-maas-01-install-lldpd" message from the 5 succeeded machines in rsyslog although all 7 machines should have an identical commissioning configuration.
$ sudo grep -i 'Installing apt packages for 20-maas-01-install-lldpd' -l /var/log/maas/rsyslog/*/*/messages
/var/log/maas/rsyslog/crack-chow/2023-02-22/messages
/var/log/maas/rsyslog/enough-camel/2023-02-22/messages
/var/log/maas/rsyslog/open-bee/2023-02-22/messages
/var/log/maas/rsyslog/quick-gopher/2023-02-22/messages
/var/log/maas/rsyslog/wanted-louse/2023-02-22/messages |
|
| 2023-03-01 03:13:36 |
Nobuto Murata |
attachment added |
|
commissioning-events.log https://bugs.launchpad.net/maas/+bug/2008454/+attachment/5650593/+files/commissioning-events.log |
|
| 2023-03-01 05:36:50 |
Nobuto Murata |
description |
maas: 1:3.3.0-13159-g.1c22f7beb-0ubuntu1~22.04.1
When a node is rebooted in the middle of commissioning with any reasons (a corner case indeed), it seems that already completed commissioning scripts are skipped thus the process fails since lldpd installation is not going to happen in the next boot.
I'm not 100% sure but it looks like the behavior is changed between 3.2 and 3.3.
[maas-capture-lldpd]
Traceback (most recent call last):
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 53, in <module>
lldpd_capture("/var/run/lldpd.socket", 60)
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 41, in lldpd_capture
time_ref = getmtime(reference_file)
File "/usr/lib/python3.8/genericpath.py", line 55, in getmtime
return os.stat(filename).st_mtime
FileNotFoundError: [Errno 2] No such file or directory: '/var/run/lldpd.socket'
Interestingly enough, I only see the "Installing apt packages for 20-maas-01-install-lldpd" message from the 5 succeeded machines in rsyslog although all 7 machines should have an identical commissioning configuration.
$ sudo grep -i 'Installing apt packages for 20-maas-01-install-lldpd' -l /var/log/maas/rsyslog/*/*/messages
/var/log/maas/rsyslog/crack-chow/2023-02-22/messages
/var/log/maas/rsyslog/enough-camel/2023-02-22/messages
/var/log/maas/rsyslog/open-bee/2023-02-22/messages
/var/log/maas/rsyslog/quick-gopher/2023-02-22/messages
/var/log/maas/rsyslog/wanted-louse/2023-02-22/messages |
maas: 1:3.3.0-13159-g.1c22f7beb-0ubuntu1~22.04.1
When a node is rebooted in the middle of commissioning with any reasons (a corner case indeed), it seems that already completed commissioning scripts are skipped thus the process fails since lldpd installation is not going to happen in the next boot.
[maas-capture-lldpd]
Traceback (most recent call last):
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 53, in <module>
lldpd_capture("/var/run/lldpd.socket", 60)
File "/tmp/user_data.sh.4Jn6tY/scripts/commissioning/maas-capture-lldpd", line 41, in lldpd_capture
time_ref = getmtime(reference_file)
File "/usr/lib/python3.8/genericpath.py", line 55, in getmtime
return os.stat(filename).st_mtime
FileNotFoundError: [Errno 2] No such file or directory: '/var/run/lldpd.socket'
Interestingly enough, I only see the "Installing apt packages for 20-maas-01-install-lldpd" message from the 5 succeeded machines in rsyslog although all 7 machines should have an identical commissioning configuration.
$ sudo grep -i 'Installing apt packages for 20-maas-01-install-lldpd' -l /var/log/maas/rsyslog/*/*/messages
/var/log/maas/rsyslog/crack-chow/2023-02-22/messages
/var/log/maas/rsyslog/enough-camel/2023-02-22/messages
/var/log/maas/rsyslog/open-bee/2023-02-22/messages
/var/log/maas/rsyslog/quick-gopher/2023-02-22/messages
/var/log/maas/rsyslog/wanted-louse/2023-02-22/messages |
|
| 2023-03-06 15:08:35 |
Björn Tillenius |
maas: status |
New |
Triaged |
|
| 2023-03-06 15:08:40 |
Björn Tillenius |
maas: importance |
Undecided |
Medium |
|
| 2023-03-06 15:08:44 |
Björn Tillenius |
maas: milestone |
|
3.4.0 |
|
| 2023-06-29 08:36:15 |
Alberto Donato |
maas: milestone |
3.4.0 |
3.4.x |
|
