| 2014-04-05 12:47:22 |
Mark Shuttleworth |
bug |
|
|
added bug |
| 2014-04-05 13:52:02 |
Mark Shuttleworth |
summary |
Tested system appears to look for MAAS in the wrong place |
maas-test should try to ensure the machine PXE boots |
|
| 2014-04-05 13:58:52 |
Mark Shuttleworth |
description |
The host from which I am running maas-test is at 192.168.1.25 on my home network. That host has another network, accessed through interface em1 on which the cloud cluster lives.
Running maas-test proceeds relatively well. I see the machine being tested PXE boot, and it is allocated an IP address on 192.168.2.0/24. I see the VM that maas-test creates is being told its network interface is 192.168.2.1/24 so this all appears correct.
However, watching the tested machine serial port output, I notice that it is being told to look for MAAS at 192.168.1.25.
2014-04-05 12:21:45,993 - url_helper.py[DEBUG]: [0/1] open 'http://192.168.1.25/MAAS/metadata//2012-03-01/meta-data/instance-id' with {'url': 'http://192.168.1.25/MAAS/metadata//2012-03-01/meta-data/instance-id', 'headers': {'Authorization': 'OAuth realm="", oauth_nonce="80128939", oauth_timestamp="1396700505", oauth_consumer_key="Q5zfbF9gmCgaN44DXc", oauth_signature_method="PLAINTEXT", oauth_version="1.0", oauth_token="M3njT2qxuaBpfpESzN", oauth_signature="%26jq6Q4gnjy3Km2b7GPXHhzNd46xMf7GAt"'}, 'allow_redirects': True, 'method': 'GET', 'timeout': 6.0} configuration
2014-04-05 12:21:45,995 - url_helper.py[DEBUG]: Calling 'http://192.168.1.25/MAAS/metadata//2012-03-01/meta-data/instance-id' failed [113/120s]: request error [HTTPConnectionPool(host='192.168.1.25', port=80): Max retries exceeded with url: /MAAS/metadata//2012-03-01/meta-data/instance-id (Caused by <class 'socket.error'>: [Errno 111] Connection refused)]
2014-04-05 12:21:45,995 - url_helper.py[DEBUG]: Please wait 7 seconds while we wait to try again
It appears that the machine is being told to check in to a MAAS on the maas-test physical host, instead of on the maas-test VM. Needless to say, the test does not proceed far from that point :) |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
## Possible values: Yes/No (Yes = All Future Boots; No = Next Boot Only)
Boot_Flags_Persistent No
## Possible values: NO-OVERRIDE/PXE/HARD-DRIVE/HARD-DRIVE-SAFE-MODE/
## DIAGNOSTIC_PARTITION/CD-DVD/BIOS-SETUP/REMOTE-FLOPPY
## PRIMARY-REMOTE-MEDIA/REMOTE-CD-DVD/REMOTE-HARD-DRIVE/FLOPPY
Boot_Device PXE
## Possible values: BIOS-SETTING/SUPPRESS/ENABLE
Console_Redirection BIOS-SETTING
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c -n chassis.cfg |
|
| 2014-04-05 13:59:31 |
Mark Shuttleworth |
description |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
## Possible values: Yes/No (Yes = All Future Boots; No = Next Boot Only)
Boot_Flags_Persistent No
## Possible values: NO-OVERRIDE/PXE/HARD-DRIVE/HARD-DRIVE-SAFE-MODE/
## DIAGNOSTIC_PARTITION/CD-DVD/BIOS-SETUP/REMOTE-FLOPPY
## PRIMARY-REMOTE-MEDIA/REMOTE-CD-DVD/REMOTE-HARD-DRIVE/FLOPPY
Boot_Device PXE
## Possible values: BIOS-SETTING/SUPPRESS/ENABLE
Console_Redirection BIOS-SETTING
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c -n chassis.cfg |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
Boot_Flags_Persistent No
Boot_Device PXE
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c -n chassis.cfg |
|
| 2014-04-05 14:03:14 |
Mark Shuttleworth |
description |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
Boot_Flags_Persistent No
Boot_Device PXE
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c -n chassis.cfg |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
Boot_Flags_Persistent No
Boot_Device PXE
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c -n chassis.cfg
The exit code of ipmi-chassis-config is 0 if all went well, and 1 if there was a problem.
maas-test should perhaps also test that the BMC responds appropriately to this configuration update. |
|
| 2014-04-05 18:26:03 |
Mark Shuttleworth |
description |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
Boot_Flags_Persistent No
Boot_Device PXE
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c -n chassis.cfg
The exit code of ipmi-chassis-config is 0 if all went well, and 1 if there was a problem.
maas-test should perhaps also test that the BMC responds appropriately to this configuration update. |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
Boot_Flags_Persistent No
Boot_Device PXE
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c \
-e chassis_Boot_Flags:Boot_Flags_Persistent=No -e Chassis_Boot_Flags:Boot_Device=PXE
The exit code of ipmi-chassis-config is 0 if all went well, and 1 if there was a problem.
maas-test should perhaps also test that the BMC responds appropriately to this configuration update. |
|
| 2014-04-05 18:26:26 |
Mark Shuttleworth |
description |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration fragment which looks like:
Section Chassis_Boot_Flags
Boot_Flags_Persistent No
Boot_Device PXE
EndSection
With that in a file called chassis.cfg, it's possible to set it with:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c \
-e chassis_Boot_Flags:Boot_Flags_Persistent=No -e Chassis_Boot_Flags:Boot_Device=PXE
The exit code of ipmi-chassis-config is 0 if all went well, and 1 if there was a problem.
maas-test should perhaps also test that the BMC responds appropriately to this configuration update. |
When maas-test boots a machine it should attempt to ensure that the machine PXE boots. In the case of IPMI, that means sending a chassis configuration:
ipmi-chassis-config -u XXX -p XXX -h AA.BB.CC.DD -c \
-e chassis_Boot_Flags:Boot_Flags_Persistent=No -e Chassis_Boot_Flags:Boot_Device=PXE
The exit code of ipmi-chassis-config is 0 if all went well, and 1 if there was a problem.
maas-test should perhaps also test that the BMC responds appropriately to this configuration update. |
|
| 2014-04-22 09:38:55 |
Raphaël Badin |
bug task added |
|
maas |
|
| 2014-04-22 09:39:02 |
Raphaël Badin |
maas: status |
New |
Invalid |
|
| 2014-04-23 06:16:49 |
Julian Edwards |
maas: status |
Invalid |
Triaged |
|
| 2014-04-23 06:16:53 |
Julian Edwards |
maas-test: status |
New |
Invalid |
|
| 2014-04-23 06:17:53 |
Julian Edwards |
maas: importance |
Undecided |
High |
|
| 2014-04-23 06:17:56 |
Julian Edwards |
maas: milestone |
|
14.10 |
|
| 2014-06-05 15:15:57 |
Raphaël Badin |
tags |
|
robustness |
|
| 2014-07-07 02:13:34 |
Julian Edwards |
maas: milestone |
1.6.0 |
|
|
| 2016-08-23 11:28:49 |
Andres Rodriguez |
maas: status |
Triaged |
Won't Fix |
|
