Everything we have is in both 20.04.3 release and impish dailies.
** Changed in: subiquity (Ubuntu Impish)
Status: Incomplete => Fix Released
** Changed in: subiquity (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification because you are a member of
Can you please try the latest Impish images and see if the work to
update the installer resolves this? (I'm not sure that work is complete
and merged, to be honest, so please keep that in mind)
** Changed in: subiquity (Ubuntu Impish)
Status: Confirmed => Incomplete
--
You received this
** Also affects: subiquity (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
** Also affects: subiquity (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Should be resolved with work in progress for Subiquity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage
I can confirm this same bug on a Supermicro 6019U-TN4RT with SATA disks
on the VROC controller. Downgrading to the D-I based installer allowed
me to use the MD device. Notably, launching a shell from the Subiquity
installer and viewing the output of /proc/mdstat indicated the device is
available
Can we please target this for 21.10? This is being requested by several
hardware partners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid
Quanxian, Pavel, Can these servers with VROC enabled/configured be
installed using MAAS (https://maas.io)?
For server, while we do have an ISO installer in Subiquity, any time we
do a deployment for customers the preferred method of managing and
deploying DC hardware is MAAS. MAAS deployments
** Tags added: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this
Unfortunately not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this bug go to:
Are there any updates here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this
Hi,
What is the result of this issue?
On my VROC platform I observe that VROC RAID does not appear as install target
at all (using live-installer). Mdadm assembles the RAID, but it does not appear
on the list of available devices.
With d-i it is working fine.
Is the result the same in this
Another workaround is to use the legacy server install image for 20.04:
http://cdimage.ubuntu.com/ubuntu-legacy-server/releases/20.04.1/release/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
** Tags added: vroc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
[Focal] Installation Fails with "Invalid dep_id" when using Intel VROC
To manage notifications about this bug go
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: subiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885191
Title:
I can confirm the bug on our servers and also that the workaround
actually works.
Also I attach the logs.
Maybe this is the most interesting part:
Traceback (most recent call last):
File
"/snap/subiquity/1966/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
line 154, in
15 matches
Mail list logo
