Bug 1172172 - Appropriate size for pre-existing logical volume can not be determined during kickstart
Summary: Appropriate size for pre-existing logical volume can not be determined during...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 22
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: mulhern
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-09 14:09 UTC by mulhern
Modified: 2015-06-23 16:06 UTC (History)
10 users (show)

Fixed In Version: anaconda-22.15-1
Clone Of: 1101322
Environment:
Last Closed: 2015-06-23 16:06:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
anaconda-tb.log (544.42 KB, text/plain)
2014-12-27 20:51 UTC, Mikolaj Kucharski
no flags Details
anaconda.log (3.03 KB, text/plain)
2014-12-27 22:02 UTC, Mikolaj Kucharski
no flags Details
program.log (89.83 KB, text/plain)
2014-12-27 22:03 UTC, Mikolaj Kucharski
no flags Details
storage.log (379.41 KB, text/plain)
2014-12-27 22:04 UTC, Mikolaj Kucharski
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1101322 0 unspecified CLOSED RHEL7rc kickstart fails to use existing volgroup 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1169783 0 unspecified CLOSED `logvol --useexisting` requires `--size` (using whole disk as PV instead of a partition) 2021-02-22 00:41:40 UTC

Internal Links: 1101322 1169783

Comment 1 mulhern 2014-12-09 14:12:44 UTC
Please attach logs to this bug.

Comment 2 Mikolaj Kucharski 2014-12-27 20:51:26 UTC
Created attachment 973597 [details]
anaconda-tb.log

Comment 3 Mikolaj Kucharski 2014-12-27 22:00:09 UTC
Ah, anaconda-tb.log contains details about different issues, I think. I've bumped memory of the VM to 2GB, will attach new logs.

Comment 4 Mikolaj Kucharski 2014-12-27 22:02:32 UTC
Created attachment 973612 [details]
anaconda.log

Comment 5 Mikolaj Kucharski 2014-12-27 22:03:49 UTC
Created attachment 973613 [details]
program.log

Comment 6 Mikolaj Kucharski 2014-12-27 22:04:31 UTC
Created attachment 973614 [details]
storage.log

Comment 7 Mikolaj Kucharski 2014-12-27 22:54:00 UTC
Let me know, do you need anything else.

Comment 8 mulhern 2015-01-02 16:35:26 UTC
It looks like the logical volume is being discovered and it has a known size which is not 0, so the problem is in how the kickstart data is being extended and used.

Comment 9 mulhern 2015-01-02 16:52:08 UTC
I've posted an updates image at http://mulhern.fedorapeople.org/1172172.img.

Please try f21 install again with this image and let me know how it turns out.
It is a very simple change, it looks like the code that signals the error has too broad a definition of what constitutes a missing size.

Comment 10 Mikolaj Kucharski 2015-01-02 22:44:51 UTC
added to the anaconda boot options:

updates=https://mulhern.fedorapeople.org/1172172.img


and it works, machine imaged successfully to Fedora 21.

Comment 11 mulhern 2015-01-12 20:33:29 UTC
(In reply to Mikolaj Kucharski from comment #10)
> added to the anaconda boot options:
> 
> updates=https://mulhern.fedorapeople.org/1172172.img
> 
> 
> and it works, machine imaged successfully to Fedora 21.

Thanks!

Acked and pushed to master + RHEL7. Waiting for f22 devel cycle to push to fedora.

Comment 12 mulhern 2015-06-19 15:54:40 UTC
Actual fix went in in 2015 January. Somehow failed to update the bz.


Note You need to log in before you can comment on or make changes to this bug.