[Bug 1129663] New: setting up encrypted partition with YaST errors: stub do_reallot_text called for LvmPv
http://bugzilla.suse.com/show_bug.cgi?id=1129663 Bug ID: 1129663 Summary: setting up encrypted partition with YaST errors: stub do_reallot_text called for LvmPv Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: aspiers@suse.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 800476 --> http://bugzilla.suse.com/attachment.cgi?id=800476&action=edit y2log.bz2 I bought a new hard disk and want to encrypt it exactly like the existing one. I tried with the yast partitioner and got: error: stub do_reallot_text called for LvmPv Unexpected situation found in the system. Click below to see more details (English only). Continue despite the error? Clicking Details... just gives the same error with no extra details. y2log attached, but here is the first occurrence: 2019-03-18 23:55:16 <1> ionian.linksys.moosehall(15522) [Ruby] y2storage/dump_manager.rb:264 Dumping Devicegraph to 04-committed 2019-03-18 23:55:16 <1> ionian.linksys.moosehall(15522) [libstorage] ActiongraphImpl.cc:621 commit begin 2019-03-18 23:55:16 <1> ionian.linksys.moosehall(15522) [libstorage] ActiongraphImpl.cc:631 Commit Action "error: stub do_reallot_text called for LvmPv" [sid:49] 2019-03-18 23:55:16 <3> ionian.linksys.moosehall(15522) [libstorage] DeviceImpl.cc:409 THROW: stub do_reallot called 2019-03-18 23:55:16 <3> ionian.linksys.moosehall(15522) [libstorage] CallbacksImpl.cc:45 CAUGHT: stub do_reallot called 2019-03-18 23:55:16 <1> ionian.linksys.moosehall(15522) [Ruby] callbacks/libstorage_callback.rb:75 libstorage-ng reported an error, asking the user whether to continue 2019-03-18 23:55:16 <1> ionian.linksys.moosehall(15522) [Ruby] callbacks/libstorage_callback.rb:76 Error details. Message: error: stub do_reallot_text called for LvmPv. What: stub do_reallot called. 2019-03-18 23:55:16 <1> ionian.linksys.moosehall(15522) [Ruby] callbacks/libstorage_callback.rb:86 error: stub do_reallot_text called for LvmPv For some reason the next attempt gave much more info: 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] CallbacksImpl.cc:55 user decides to continue after error 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] ActiongraphImpl.cc:631 Commit Action "Creating encryption layer device on /dev/sdc2" [sid:110, first] 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:69 constructor SystemCmd("/sbin/udevadm settle --timeout=20") 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:188 SystemCmd Executing:"/sbin/udevadm settle --timeout=20" 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:189 timestamp [429511.827502], 2019-03-18 23:58:02 GMT, 2019-03-18 23:58:02 GMT 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:419 stopwatch 0.041077s for "/sbin/udevadm settle --timeout=20" 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:439 system() Returns:0 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] BlkDeviceImpl.cc:805 name:/dev/sdc2 exists:true 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:69 constructor SystemCmd("/sbin/cryptsetup --batch-mode luksFormat '/dev/sdc2' --tries 1 --key-file -") 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:188 SystemCmd Executing:"/sbin/cryptsetup --batch-mode luksFormat '/dev/sdc2' --tries 1 --key-file -" 2019-03-18 23:58:02 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:189 timestamp [429511.869396], 2019-03-18 23:58:02 GMT, 2019-03-18 23:58:02 GMT 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:419 stopwatch 5.210480s for "/sbin/cryptsetup --batch-mode luksFormat '/dev/sdc2' --tries 1 --key-file -" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:439 system() Returns:0 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:69 constructor SystemCmd("/sbin/blkid -c '/dev/null' '/dev/sdc2'") 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:188 SystemCmd Executing:"/sbin/blkid -c '/dev/null' '/dev/sdc2'" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:189 timestamp [429517.080456], 2019-03-18 23:58:07 GMT, 2019-03-18 23:58:07 GMT 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:663 Adding Line 1 "/dev/sdc2: UUID="3eb892ba-42ca-4cf7-9e50-eaff3f76d01b" TYPE="crypto_LUKS" PARTUUID="c296f447-4944-4927-97f6-d0b5914ceb68"" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:629 pid:16510 added lines:1 stderr:false 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:419 stopwatch 0.011767s for "/sbin/blkid -c '/dev/null' '/dev/sdc2'" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:439 system() Returns:0 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] CmdBlkid.cc:149 data[/dev/sdc2] -> is-luks:true luks-uuid:3eb892ba-42ca-4cf7-9e50-eaff3f76d01b 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] ActiongraphImpl.cc:631 Commit Action "Activating encryption layer device on /dev/sdc2" [sid:110, last] 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:69 constructor SystemCmd("/sbin/udevadm settle --timeout=20") 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:188 SystemCmd Executing:"/sbin/udevadm settle --timeout=20" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:189 timestamp [429517.093042], 2019-03-18 23:58:07 GMT, 2019-03-18 23:58:07 GMT 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:419 stopwatch 0.032027s for "/sbin/udevadm settle --timeout=20" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:439 system() Returns:0 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] BlkDeviceImpl.cc:805 name:/dev/sdc2 exists:true 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:69 constructor SystemCmd("/sbin/cryptsetup --batch-mode luksOpen '/dev/sdc2' 'cr_ata-ST2000DM006-2DM164_Z560YD1F-part2' --tries 1 --key-file -") 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:188 SystemCmd Executing:"/sbin/cryptsetup --batch-mode luksOpen '/dev/sdc2' 'cr_ata-ST2000DM006-2DM164_Z560YD1F-part2' --tries 1 --key-file -" 2019-03-18 23:58:07 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:189 timestamp [429517.125845], 2019-03-18 23:58:07 GMT, 2019-03-18 23:58:07 GMT 2019-03-18 23:58:09 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:419 stopwatch 2.146724s for "/sbin/cryptsetup --batch-mode luksOpen '/dev/sdc2' 'cr_ata-ST2000DM006-2DM164_Z560YD1F-part2' --tries 1 --key-file -" 2019-03-18 23:58:09 <1> ionian.linksys.moosehall(15522) [libstorage] SystemCmd.cc:439 system() Returns:0 2019-03-18 23:58:09 <1> ionian.linksys.moosehall(15522) [libstorage] ActiongraphImpl.cc:631 Commit Action "error: stub do_reallot_text called for LvmPv" [sid:49] 2019-03-18 23:58:09 <3> ionian.linksys.moosehall(15522) [libstorage] DeviceImpl.cc:409 THROW: stub do_reallot called 2019-03-18 23:58:09 <3> ionian.linksys.moosehall(15522) [libstorage] CallbacksImpl.cc:45 CAUGHT: stub do_reallot called 2019-03-18 23:58:09 <1> ionian.linksys.moosehall(15522) [Ruby] callbacks/libstorage_callback.rb:75 libstorage-ng reported an error, asking the user whether to continue 2019-03-18 23:58:09 <1> ionian.linksys.moosehall(15522) [Ruby] callbacks/libstorage_callback.rb:76 Error details. Message: error: stub do_reallot_text called for LvmPv. What: stub do_reallot called. 2019-03-18 23:58:09 <1> ionian.linksys.moosehall(15522) [Ruby] callbacks/libstorage_callback.rb:86 error: stub do_reallot_text called for LvmPv -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c1
Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c2
Ancor Gonzalez Sosa
From what I can see in the logs, /dev/sdc2 contained an LvmPv object not associated to any volume group (likely, just a leftover from the previous system to which that hard disk was plugged).
Then the user encrypts that partition which results in the LvmPv object being deleted from the devicegraph and a new Encryption object being added on its place. And then the library become nuts while trying to create the actiongraph needed to perform that transformation. Creating a unit test to showcase the problem should be doable -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c3
Ancor Gonzalez Sosa
Creating a unit test to showcase the problem should be doable
Arvin, would it be possible to create a unit test for the commands executed during the commit phase with this probed devicegraph[1] and this staging[2] one? [1] http://paste.opensuse.org/view//52937714 [2] http://paste.opensuse.org/view//77631130 I suspect that would trigger the bug. Before the commit phase, the actiongraph looks fine, it contains the entries: - Delete physical volume on /dev/sdc2 - Encrypt partition /dev/sdc2 But I suspect that translating that into commands ends up in the reported exception. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c4
Arvin Schnell
Arvin, would it be possible to create a unit test for the commands executed during the commit phase with this probed devicegraph[1] and this staging[2] one?
Yes, that is easy. Or just run "libstorage-ng/utils/display --actiongraph probed.xml staging.xml". But I do not get an exception with those from comment #3. The complete YaST logs will contain the devicegraphs and then debugging should be easier. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c5
Adam Spiers
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c6
--- Comment #6 from Ancor Gonzalez Sosa
The complete YaST logs will contain the devicegraphs and then debugging should be easier.
The initially attached YaST logs did contain the devicegraphs (inline the y2log file instead of separate files, but that's just a matter of copy&pasting the interesting lines). That's what I used to get my conclusions. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c7
Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c8
--- Comment #8 from Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c9
--- Comment #9 from Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c10
Arvin Schnell
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c11
--- Comment #11 from Ancor Gonzalez Sosa
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c12
David Diaz
http://bugzilla.suse.com/show_bug.cgi?id=1129663
http://bugzilla.suse.com/show_bug.cgi?id=1129663#c13
--- Comment #13 from Adam Spiers
participants (1)
-
bugzilla_noreply＠novell.com