Created attachment 1941773 [details]
anaconda.log

Reproduced in a VM with 2 disks. Compose RHEL-8.8.0-20230201.0 with anaconda-33.16.8.6-1.el8, python-blivet-3.6.0-3.el8.

Created attachment 1941774 [details]
storage.log

Created attachment 1941775 [details]
syslog

Hi Vendy, could you please take a look if you can spot what is the root cause?

From anaconda.log:

07:44:52,685 DBG ui.gui.spokes.lib.accordion: Select device: vda1
07:45:05,046 DBG ui.gui.spokes.custom_storage: Saving the right side for device: vda1
07:45:05,047 DBG ui.gui.spokes.custom_storage: Device request: {
container-encrypted = False
container-name = ''
container-raid-level = ''
container-size-policy = 0
container-spec = ''
device-encrypted = False
device-name = 'vda1' -> 'boot'
device-raid-level = '' -> 'raid1'
device-size = 1073741824
device-spec = 'vda1'
device-type = 2 -> 1
disks = ['vda', 'vdb']
format-type = 'xfs'
label = ''
luks-version = ''
mount-point = '/boot'
reformat = True
}

From storage.log:

DEBUG:anaconda.modules.storage.partitioning.interactive.utils:Generated factory arguments: {
device_type = 1,
device = None,
disks = [DiskDevice instance (0x7f231421f908) --
  name = vda  status = True  id = 4
  children = ['non-existent 2.52 GiB partition vda2 (142) with non-existent swap']
  parents = []
  uuid = None  size = 20 GiB
  format = non-existent msdos disklabel
  major = 252  minor = 0  exists = True  protected = False
  sysfs path = /sys/devices/pci0000:00/0000:00:02.4/0000:05:00.0/virtio4/block/vda
  target size = 20 GiB  path = /dev/vda
  format args = []  original_format = None  removable = False  wwn = None, DiskDevice instance (0x7f231421ffd0) --
  name = vdb  status = True  id = 9
  children = ['non-existent 20 GiB partition vdb1 (135) with non-existent xfs filesystem '
 'mounted at /']
  parents = []
  uuid = None  size = 20 GiB
  format = non-existent msdos disklabel
  major = 252  minor = 16  exists = True  protected = False
  sysfs path = /sys/devices/pci0000:00/0000:00:02.5/0000:06:00.0/virtio5/block/vdb
  target size = 20 GiB  path = /dev/vdb
  format args = []  original_format = None  removable = False  wwn = None],
mountpoint = '/boot',
fstype = 'xfs',
label = None,
luks_version = None,
device_name = 'boot',
size = Size (1024 MiB),
raid_level = <blivet.devicelibs.raid.RAID1 object at 0x7f2318a7bac8>,
encrypted = False,
container_name = None,
container_size = 0,
container_raid_level = None,
container_encrypted = False
}

The device request and the arguments generated for the Blivet's factory look good to me. It seems to be an issue in the Blivet library.

Reassigning to blivet based on comment 5.

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.