NVMe test failures in integration tests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
curtin |
Triaged
|
Medium
|
Unassigned |
Bug Description
In https:/
[ 316.702663] cloud-init[895]: Traceback (most recent call last):
[ 316.706636] cloud-init[895]: File "/curtin/
[ 316.707961] cloud-init[895]: ret = args.func(args)
[ 316.708918] cloud-init[895]: File "/curtin/
[ 316.710387] cloud-init[895]: print(json.
[ 316.716316] cloud-init[895]: File "/curtin/
[ 316.720192] cloud-init[895]: return storage_
[ 316.724117] cloud-init[895]: File "/curtin/
[ 316.726642] cloud-init[895]: found_cfgs, found_errs = parser.parse()
[ 316.729288] cloud-init[895]: File "/curtin/
[ 316.735945] cloud-init[895]: entry = self.asdict(data)
[ 316.739419] cloud-init[895]: File "/curtin/
[ 316.742409] cloud-init[895]: "Couldn't find partition entry in table")
I know what's going on here:
The probert level in bionic/cosmic is not enough to provide the correct output format for curtin block-discover.
I'll sort out a fix in vmtest.