Bug 1314805

Summary: Need to add partition table for atomic
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: OtherAssignee: Daniel Lobato Garcia <dlobatog>
Status: CLOSED ERRATA QA Contact: Sachin Ghai <sghai>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, ehelms, paji
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:04:24 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:
Bug Depends On:    
Bug Blocks: 1321771    

Description Sachin Ghai 2016-03-04 15:03:06 UTC
Description of problem:
Currently I don't see partition table for atomic, its required at the time of provisioning atomic host.


Version-Release number of selected component (if applicable):
sat 6.2 snap2

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
Missing  partition table for atomic

Expected results:


Additional info:

Comment 4 Daniel Lobato Garcia 2016-03-17 11:02:52 UTC
Atomic doesn't need any special partition table - the "Kickstart default" partition table works just fine using autopart.

Comment 5 Partha Aji 2016-03-21 18:27:40 UTC
It works with "Kickstart default". Moving it to ON_QA  for qe to verify

Comment 6 Sachin Ghai 2016-03-29 09:17:39 UTC
I just provisioned a atomic-host and associated 'Kickstart default' template while provisioning. and partitioning works fine. Moving this to verified.

Comment 9 errata-xmlrpc 2016-07-27 09:04:24 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1500