| 2021-09-04 13:52:24 |
Takashi Kajinami |
bug |
|
|
added bug |
| 2021-09-04 13:52:35 |
Takashi Kajinami |
description |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
qemu-img stdout: image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now the format of encrypted attribute is different ('yes'/'no' vs true/false) according to the format used. |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
qemu-img stdout: image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now the format of encrypted attribute is different ('yes'/'no' vs true/false) according to the image format used. |
|
| 2021-09-04 14:05:23 |
Takashi Kajinami |
oslo.utils: assignee |
|
Takashi Kajinami (kajinamit) |
|
| 2021-09-04 14:05:27 |
OpenStack Infra |
oslo.utils: status |
New |
In Progress |
|
| 2021-09-04 14:08:57 |
Takashi Kajinami |
description |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
qemu-img stdout: image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now the format of encrypted attribute is different ('yes'/'no' vs true/false) according to the image format used. |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
qemu-img stdout: image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now encrypted attribute can be different ('yes'/'no' vs true/false) according to the output format used. |
|
| 2021-09-04 14:10:55 |
Takashi Kajinami |
description |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
qemu-img stdout: image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now encrypted attribute can be different ('yes'/'no' vs true/false) according to the output format used. |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now encrypted attribute can be different ('yes'/'no' vs true/false) according to the output format used. |
|
| 2021-09-04 14:20:14 |
Takashi Kajinami |
description |
When format='human' is used, ecnrypted can be one of 'yes' or 'no', according to the encrypted field returned by the `qemu-img info` command.
``
image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true/false instead.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now encrypted attribute can be different ('yes'/'no' vs true/false) according to the output format used. |
When format='human' is used, the ecnrypted attribute can be 'yes' or None. This is because the `qemu-img info` command shows "encrypted: yes" for encrypted images while no line with the encrypted key for non-encrypted images.
``
image: /dev/disk/by-id/scsi-3600140564d2875a88d3462f89d7123d3
file format: luks
virtual size: 0.998 GiB (1071644672 bytes)
disk size: 0 B
encrypted: yes <====(*)
Format specific information:
ivgen alg: plain64
hash alg: sha256
cipher alg: aes-128
uuid: 001bdcd8-ec3c-4c83-9702-1d3d0267cd71
cipher mode: xts
slots:
[0]:
...
payload offset: 2097152
master key iters: 113188
```
However when json format is used, the encrypted field of "qemu-img info" shows true or false.
```
{
"virtual-size": 1071644672,
"filename": "/dev/disk/by-id/scsi-36001405ed1da8b633ed4b238518a1dfb",
"format": "luks",
"actual-size": 0,
"format-specific": {
"type": "luks",
"data": {
"ivgen-alg": "plain64",
"hash-alg": "sha256",
"cipher-alg": "aes-128",
"uuid": "ab4c427c-b0d7-4ef6-afaf-c9a55a8c079d",
"cipher-mode": "xts",
"slots": [
{
...
}
},
"encrypted": true, <===(*)
"dirty-flag": false
}
```
Because of this now encrypted attribute can be different ('yes'/None vs true/false) according to the output format used. |
|
| 2021-10-13 14:26:03 |
OpenStack Infra |
oslo.utils: status |
In Progress |
Fix Released |
|
| 2022-01-12 11:31:20 |
Stephen Finucane |
oslo.utils: importance |
Undecided |
Medium |
|
| 2022-01-12 12:55:03 |
OpenStack Infra |
tags |
|
in-stable-xena |
|
