| 2016-08-11 11:28:05 |
Andres Rodriguez |
bug |
|
|
added bug |
| 2016-08-11 11:28:16 |
Andres Rodriguez |
maas: importance |
Undecided |
Critical |
|
| 2016-08-11 11:28:18 |
Andres Rodriguez |
maas: status |
New |
Confirmed |
|
| 2016-08-11 11:28:35 |
Andres Rodriguez |
description |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there. |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Note, this has only been confirmed with Lee's bootloader branch. |
|
| 2016-08-11 11:28:49 |
Andres Rodriguez |
summary |
MAchine unable to pxe with no-such-image while non-related images rae being imported |
[Trunk] MAchine unable to pxe with no-such-image while non-related images rae being imported |
|
| 2016-08-11 11:28:54 |
Andres Rodriguez |
maas: milestone |
|
2.1.0 |
|
| 2016-08-11 11:29:00 |
Andres Rodriguez |
nominated for series |
|
maas/2.0 |
|
| 2016-08-11 11:29:00 |
Andres Rodriguez |
bug task added |
|
maas/2.0 |
|
| 2016-08-11 11:29:00 |
Andres Rodriguez |
nominated for series |
|
maas/trunk |
|
| 2016-08-11 11:29:00 |
Andres Rodriguez |
bug task added |
|
maas/trunk |
|
| 2016-08-11 11:29:06 |
Andres Rodriguez |
maas/2.0: milestone |
|
2.0.0 |
|
| 2016-08-11 11:29:10 |
Andres Rodriguez |
maas/2.0: status |
New |
Incomplete |
|
| 2016-08-11 11:29:13 |
Andres Rodriguez |
maas/2.0: importance |
Undecided |
Critical |
|
| 2016-08-11 12:01:11 |
Andres Rodriguez |
summary |
[Trunk] MAchine unable to pxe with no-such-image while non-related images rae being imported |
[Trunk] MAchine unable to pxe with no-such-image while non-related images are being imported |
|
| 2016-08-11 12:19:16 |
Andres Rodriguez |
description |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Note, this has only been confirmed with Lee's bootloader branch. |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Note, this has only been confirmed with Lee's bootloader branch.
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
|
| 2016-08-11 12:19:19 |
Andres Rodriguez |
maas/2.0: status |
Incomplete |
Confirmed |
|
| 2016-08-11 12:20:03 |
Andres Rodriguez |
description |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Note, this has only been confirmed with Lee's bootloader branch.
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Confirmed in 2.0, trunk, bootloader branch.
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
|
| 2016-08-11 12:22:12 |
Andres Rodriguez |
description |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Confirmed in 2.0, trunk, bootloader branch.
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Confirmed in 2.0, trunk, bootloader branch.
Example:
#MAAS Imported images in Region:
maas-integration.TestMAASIntegration.test_imported_boot_resources_region ... ok
#MAAS Imported images in Rack:
maas-integration.TestMAASIntegration.test_imported_boot_resources_rack ... ok
#MAAS Told macines to PXE boot
maas-integration.TestMAASIntegration.test_boot_nodes_enlist ... ok
#At this point, I try to import arm64/i386 manually, and this is what I see in the logs:
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
|
| 2016-08-11 12:39:08 |
Andres Rodriguez |
description |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there.
Confirmed in 2.0, trunk, bootloader branch.
Example:
#MAAS Imported images in Region:
maas-integration.TestMAASIntegration.test_imported_boot_resources_region ... ok
#MAAS Imported images in Rack:
maas-integration.TestMAASIntegration.test_imported_boot_resources_rack ... ok
#MAAS Told macines to PXE boot
maas-integration.TestMAASIntegration.test_boot_nodes_enlist ... ok
#At this point, I try to import arm64/i386 manually, and this is what I see in the logs:
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there. (while the region is trying to import new images).
Confirmed in 2.0, trunk, bootloader branch.
Example:
#MAAS Imported images in Region:
maas-integration.TestMAASIntegration.test_imported_boot_resources_region ... ok
#MAAS Imported images in Rack:
maas-integration.TestMAASIntegration.test_imported_boot_resources_rack ... ok
#MAAS Told macines to PXE boot
maas-integration.TestMAASIntegration.test_boot_nodes_enlist ... ok
#At this point, I try to import arm64/i386 manually, and this is what I see in the logs:
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
|
| 2016-08-11 13:03:40 |
Andres Rodriguez |
description |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there. (while the region is trying to import new images).
Confirmed in 2.0, trunk, bootloader branch.
Example:
#MAAS Imported images in Region:
maas-integration.TestMAASIntegration.test_imported_boot_resources_region ... ok
#MAAS Imported images in Rack:
maas-integration.TestMAASIntegration.test_imported_boot_resources_rack ... ok
#MAAS Told macines to PXE boot
maas-integration.TestMAASIntegration.test_boot_nodes_enlist ... ok
#At this point, I try to import arm64/i386 manually, and this is what I see in the logs:
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
In the CI, I came across a bug that surfaces an issue that prevents machines from PXE booting while other images are being imported. What does the CI do:
1. CI imports Xenial
2. CI tells machines to PXE (power's them on for enlistment).
3. Machine enlists and CI containers.
However, I did this:
1. CI imports Xenial
2. CI tells machines to PXE
3. After 2, I immediately try to import images for other architecture (such as arm64, i386).
4. Machines fail to PXE boot with no-such-image even though amd64 images are there. (while the region is trying to import new images).
Confirmed in 2.0, trunk, bootloader branch.
Example:
#MAAS Imported images in Region:
maas-integration.TestMAASIntegration.test_imported_boot_resources_region ... ok
#MAAS Imported images in Rack:
maas-integration.TestMAASIntegration.test_imported_boot_resources_rack ... ok
#MAAS Told macines to PXE boot
maas-integration.TestMAASIntegration.test_boot_nodes_enlist ... ok
#At this point, I try to import arm64/i386 manually, and this is what I see in the logs while Region is trying to sync new images and machines are attempting to PXE boot:
2016-08-11 08:19:41 [TFTP (UDP)] Datagram received from ('10.245.136.19', 49173): <RRQDatagram(filename=b'ubuntu/amd64/generic/xenial/no-such-image/boot-kernel', mode=b'octet', options=OrderedDict([(b'tsize', b'0'), (b'blksize', b'1408')]))> |
|
| 2016-08-11 13:17:09 |
Andres Rodriguez |
summary |
[Trunk] MAchine unable to pxe with no-such-image while non-related images are being imported |
MAchine unable to pxe with no-such-image while non-related images are being imported |
|
| 2016-08-11 14:05:38 |
Christian Reis |
summary |
MAchine unable to pxe with no-such-image while non-related images are being imported |
Machine unable to pxe with no-such-image while non-related images are being imported |
|
| 2016-08-22 19:16:45 |
Andres Rodriguez |
maas/2.0: milestone |
2.0.0 |
2.1.0 |
|
| 2016-08-22 19:16:47 |
Andres Rodriguez |
maas/trunk: milestone |
2.0.1 |
2.1.0 |
|
| 2016-08-22 19:17:22 |
Andres Rodriguez |
maas/2.0: milestone |
2.1.0 |
2.0.1 |
|
| 2016-09-26 13:55:08 |
Gavin Panella |
maas: status |
Confirmed |
Triaged |
|
| 2016-09-26 13:55:56 |
Gavin Panella |
maas/2.0: status |
Confirmed |
Triaged |
|
| 2016-10-04 16:07:56 |
Launchpad Janitor |
branch linked |
|
lp:~blake-rouse/maas/fix-1612203-1611949 |
|
| 2016-10-04 16:11:51 |
Blake Rouse |
maas/trunk: status |
Triaged |
In Progress |
|
| 2016-10-04 16:11:54 |
Blake Rouse |
maas/trunk: assignee |
|
Blake Rouse (blake-rouse) |
|
| 2016-10-05 15:47:39 |
MAAS Lander |
maas/trunk: status |
In Progress |
Fix Committed |
|
| 2016-10-06 01:59:19 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
| 2017-11-02 18:16:20 |
Andres Rodriguez |
maas/2.0: status |
Triaged |
Won't Fix |
|
| 2017-11-02 18:16:22 |
Andres Rodriguez |
maas/2.0: milestone |
2.0.1 |
|
|
