This pod does not match the specified networks.

Bug #1892758 reported by Marian Gasparovic
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
Undecided
Unassigned

Bug Description

MAAS: 2.8.1-8567-g.c4825ca06-0ubuntu1~18.04.

2020-08-22-09:21:07 root DEBUG [localhost]: maas root pod compose 1 hostname=vault-1 cores=2 memory=4096 storage=20.0 zone=2 'interfaces=eth0:space=oam-space,mode=auto;eth1:space=internal-space,type=bridge,mode=auto'
2020-08-22-09:21:08 root ERROR [localhost] Command failed: maas root pod compose 1 hostname=vault-1 cores=2 memory=4096 storage=20.0 zone=2 'interfaces=eth0:space=oam-space,mode=auto;eth1:space=internal-space,type=bridge,mode=auto'
2020-08-22-09:21:08 root ERROR [localhost] STDOUT follows:
This pod does not match the specified networks.

We had other runs with the same config which passed this part without any issue

configs and crashdumps are here -

https://oil-jenkins.canonical.com/artifacts/dc196208-076f-41f0-9edc-21835bb440de/index.html

Tags: cdo-qa
Revision history for this message
Alberto Donato (ack) wrote :

Has this been seen recently with 2.9 or 3.0?

Changed in maas:
status: New → Incomplete
Revision history for this message
Marian Gasparovic (marosg) wrote :

No, we encountered this bug only once.

Revision history for this message
Alberto Donato (ack) wrote :

Are networks on the pod host configured before the pod is added to maas or after?

I wonder if this could be a race condition where the pod is added when it doesn't yet see all the expected networks.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.