CentOS 6 deployment fails to deploy with Bionic
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.4 |
Won't Fix
|
Medium
|
Unassigned | |||
3.5 |
Won't Fix
|
Medium
|
Unassigned | |||
3.6 |
Triaged
|
Medium
|
Unassigned |
Bug Description
* Operating system: Ubuntu 18.04
* MAAS version: 2.4.0 (6981-g011e51b7
root@maas1:~# ls -lah /var/log/maas/
total 16M
drwxr-xr-x 4 maas maas 4.0K May 23 06:25 .
drwxrwxr-x 18 root syslog 4.0K Jun 6 06:25 ..
-rw-r--r-- 1 syslog syslog 932K Jun 6 15:41 maas.log
drwxr-x--- 2 proxy proxy 4.0K Jun 6 06:25 proxy
-rw-r--r-- 1 maas maas 5.0M Jun 6 15:42 rackd.log
-rw-r--r-- 1 maas maas 9.3M Jun 6 15:49 regiond.log
-rw-r--r-- 1 maas maas 391K May 23 06:24 regiond.log.1.gz
drwxr-xr-x 6 syslog syslog 4.0K May 31 13:56 rsyslog
# dpkg -l '*maas*'|cat
Desired=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 2.4.0-6981-
ii maas-cli 2.4.0-6981-
un maas-cluster-
ii maas-common 2.4.0-6981-
ii maas-dhcp 2.4.0-6981-
un maas-dns <none> <none> (no description available)
ii maas-proxy 2.4.0-6981-
ii maas-rack-
ii maas-region-api 2.4.0-6981-
ii maas-region-
un maas-region-
un python-django-maas <none> <none> (no description available)
un python-maas-client <none> <none> (no description available)
un python-
ii python3-django-maas 2.4.0-6981-
ii python3-maas-client 2.4.0-6981-
ii python3-
I'm running into an issue related to CentOS 6 deployments failing with multiple MAAS installations using different network configurations (one simple and one complex) for the machines being deployed. I thought it might have been related to the complex network config however I've confirmed the same problem exists with what I would consider a simple network config. Below is the error output found in the installation log once the CentOS 6 deployment fails:
-------
Traceback (most recent call last):
File "/tmp/tmpzkdjc8
main()
File "/tmp/tmpzkdjc8
grub_root = get_grub_
File "/tmp/tmpzkdjc8
return regex.groups()[0]
AttributeError: 'NoneType' object has no attribute 'groups'
Unexpected error while running command.
Command: ['/tmp/
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
curtin: Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'curthooks']
Exit code: 3
Reason: -
Stdout: Traceback (most recent call last):
File "/tmp/tmpzkdjc8
main()
File "/tmp/tmpzkdjc8
File "/tmp/tmpzkdjc8
return regex.groups()[0]
Unexpected error while running command.
Command: ['/tmp/
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
Stderr: ''
-------
Here are the steps to recreate the problem:
1.) Enlist the server into MAAS and rename it to the appropriate server name
2.) Mark the machine as broken and configure the network interfaces as follows:
- eth0 - private subnet used for MAAS deployments
- eth1 - public /29 subnet dedicated to specific server (gateway to internet here)
3.) Mark the machine as fixed and then commission the machine ensuring to select the commissioning option to retain the current network config
4.) Once the server has been successfully commissioned, acquire the server (admin user) and deploy with CentOS 6.
5.) The server indicates the installation has begun and CentOS 6 cloud installer image is downloaded for install/extraction however the error listed above is produced immediately after the image download then the status changes to 'Failed Deployment'
I have no problems successfully installing via MAAS operating systems Ubuntu 14.04, Ubuntu 16.04, Ubuntu 18.04 and CentOS 7 using the same exact steps listed above.
If you need any additional information or have any questions please let me know and I'll be happy to oblige.
Thanks!
Related branches
- Dan Watkins (community): Approve
- Server Team CI bot: Approve (continuous-integration)
-
Diff: 252 lines (+160/-3)4 files modifiedexamples/tests/centos6_basic.yaml (+101/-0)
tests/vmtests/releases.py (+14/-0)
tests/vmtests/test_basic.py (+29/-1)
tests/vmtests/test_simple.py (+16/-2)
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
Hi there,
I've deployed centos6 and i cannot reproduce your issue https:/ /pastebin. ubuntu. com/p/t7H9hbQMK Z/
Could you confirm a few things:
1. Which image have you used?
2. Is there any customization done, or just straight forward deployment?