Bug 1172172

Summary: Appropriate size for pre-existing logical volume can not be determined during kickstart
Product: [Fedora] Fedora Reporter: mulhern <amulhern>
Component: anacondaAssignee: mulhern <amulhern>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: amulhern, anaconda-maint-list, g.kaviyarasu, jonathan, mbanas, mikolaj, pkotvan, release-test-team-automation, vanmeeuwen+fedora, wnefal+redhatbugzilla
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-22.15-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1101322 Environment:
Last Closed: 2015-06-23 16:06:46 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda-tb.log
none
anaconda.log
none
program.log
none
storage.log none

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.