Bug 37662 - fails to setup a password for the LUKS partition properly
Summary: fails to setup a password for the LUKS partition properly
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: alterator-luks (show other bugs)
Version: unstable
Hardware: x86_64 Linux
: P3 critical
Assignee: Олег Соловьев
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks: 37660
  Show dependency tree
 
Reported: 2019-12-23 03:38 MSK by Dmitry V. Levin
Modified: 2020-01-22 17:46 MSK (History)
4 users (show)

See Also:


Attachments
luks error (12.68 KB, image/png)
2020-01-15 15:00 MSK, Олег Соловьев
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitry V. Levin 2019-12-23 03:38:27 MSK
When installing into a LUKS partition on a UEFI hardware,
the corresponding install step stops with the following diagnostics:
"Критическая ошибка
Failed setup the password: No key available with this passphrase."
Comment 1 Олег Соловьев 2019-12-23 11:39:55 MSK
A duplicate?

Image alt-kworkstation-8.94-beta20191220-install-x86_64.iso is good, installer successfully set up given password to cryptocontainers.

Had to manually edit /etc/default/grub to proceed because of bug #37661

*** This bug has been marked as a duplicate of bug 31895 ***
Comment 2 Dmitry V. Levin 2019-12-23 13:48:55 MSK
(In reply to comment #1)
> A duplicate?

It looks similar but I don't think it's a duplicate because alterator-luks-0.3.0-alt2 from slinux-8.910-20191212-x86_64.iso was used.

Apparently, the passphrase was set successfully, but alterator-luks complained nevertheless and didn't allow to proceed.

For the reference, it was a single LUKS partition created by installer, containing rootfs and all the rest.
Comment 3 Олег Соловьев 2019-12-23 14:38:02 MSK
(В ответ на комментарий №2)
> (In reply to comment #1)
> > A duplicate?
> 
> It looks similar but I don't think it's a duplicate because
> alterator-luks-0.3.0-alt2 from slinux-8.910-20191212-x86_64.iso was used.
Where did you get that iso?
Comment 4 Dmitry V. Levin 2019-12-23 14:46:42 MSK
(In reply to comment #3)
> (В ответ на комментарий №2)
> > (In reply to comment #1)
> > > A duplicate?
> > 
> > It looks similar but I don't think it's a duplicate because
> > alterator-luks-0.3.0-alt2 from slinux-8.910-20191212-x86_64.iso was used.
> Where did you get that iso?

It used to be the latest build of Simply, now slinux-8.910-20191220-x86_64.iso seems to be the latest.
Comment 5 Олег Соловьев 2019-12-23 15:01:10 MSK
(В ответ на комментарий №3)
> Where did you get that iso?
Still no answer to the question above.

If it built from scratch, provide it with exact partitioning steps to reproduce the issue and find out what I am doing wrong if it works to me.
Comment 6 Dmitry V. Levin 2019-12-23 15:16:14 MSK
(In reply to comment #5)
> (В ответ на комментарий №3)
> > Where did you get that iso?
> Still no answer to the question above.

I got mine from basalt:/space/office/sem/iso/ if it helps.

> If it built from scratch, provide it with exact partitioning steps to reproduce
> the issue and find out what I am doing wrong if it works to me.

There was nothing special: the first partition was FAT32, the second was LUKS.

Wait, there was another LUKS partition on that disk that was not involved at all, but in theory it could confuse alterator-luks.
Comment 7 Олег Соловьев 2019-12-23 15:28:34 MSK
(В ответ на комментарий №6)
> Wait, there was another LUKS partition on that disk that was not involved at
> all, but in theory it could confuse alterator-luks.

I suggest either remove that partition manually and retry.

Perhaps alterator-luks should be modified in such way:
Set password for partitions with mountpoints assigned
Comment 8 Олег Соловьев 2019-12-24 11:29:20 MSK
(В ответ на комментарий №7)
> Set password for partitions with mountpoints assigned

Implemented fix a slightly different way: cryptsetup can tell whether given crypto device is active or not.
If it's not, password will not be set because it was set manually or device remains from previous installation.
Comment 9 Repository Robot 2019-12-24 15:49:41 MSK
alterator-luks-0.3.1-alt1 -> sisyphus:

Tue Dec 24 2019 Oleg Solovyov <mcpain@altlinux> 0.3.1-alt1
- Don't change password on inactive containers (Closes: #37662)
Comment 10 Олег Соловьев 2020-01-13 15:33:08 MSK
(В ответ на комментарий №9)
> alterator-luks-0.3.1-alt1 -> sisyphus:
> 
> Tue Dec 24 2019 Oleg Solovyov <mcpain@altlinux> 0.3.1-alt1
> - Don't change password on inactive containers (Closes: #37662)

Causes regression
https://redmine.basealt.space/issues/10726
Comment 11 AEN 2020-01-13 15:42:43 MSK
(В ответ на комментарий №10)
> (В ответ на комментарий №9)
> > alterator-luks-0.3.1-alt1 -> sisyphus:
> > 
> > Tue Dec 24 2019 Oleg Solovyov <mcpain@altlinux> 0.3.1-alt1
> > - Don't change password on inactive containers (Closes: #37662)
> 
> Causes regression
> https://redmine.basealt.space/issues/10726

Прошу избегать ссылок в публичных багах на закрытые источники, в тч. redmine. 
 Спасибо.
Comment 12 Олег Соловьев 2020-01-15 15:00:11 MSK
Created attachment 8515 [details]
luks error

После обновления до alterator-luks при входе в систему не принимает пароль на шифрованный раздел. Регрессия, до обновления работает.
Comment 13 AEN 2020-01-15 15:07:30 MSK
(В ответ на комментарий №12)
> Created an attachment (id=8515) [details]
> luks error
> 
> После обновления до alterator-luks при входе в систему не принимает пароль на
> шифрованный раздел. Регрессия, до обновления работает.

Понятно, спасибо!
Comment 14 Олег Соловьев 2020-01-22 17:46:17 MSK
Помечаю FIXED, но в p9 отправка затруднена из-за 37695, т.к. установленную систему загрузить все еще невозможно.