What is the nature and description of the request?

The customer has identified that the -s scripted option related to parted
becomes interactive under certain circumstances. They would like to request the
introduction of a '--force' option to be used if desired with the -s scripted
option within the 'parted' command. 

The issue they used as an example is as follows. When running parted as part of
a Puppet script in their deployment environment, NYSE intermittently receive
the following warnnigs/errors:

---
//Node[frobdignag.bar.foo.com]/foo_ukd/ukd_utpds::setup/ukd_utpds::filesystems_qa/ukd_utpds::filesystems_qa::create_partitions/Lvm::
Create_partition[c1d3p1]/Exec[create_partition-/dev/cciss/c1d3p1]/returns: Warning: /dev/cciss/c1d3 contains GPT signatures, indicating
that it has a GPT table. However, it does not have a valid fake msdos partition table, as it should. Perhaps it was corrupted --
possibly by a program that doesn't understand GPT partition tables. Or perhaps you deleted the GPT table, and are now using an msdos
partition table. Is this a GPT partition table?
notice:
//Node[frobdignag.bar.foo.com]/foo_ukd/ukd_utpds::setup/ukd_utpds::filesystems_qa/ukd_utpds::filesystems_qa::create_partitions/Lvm::
Create_partition[c1d3p1]/Exec[create_partition-/dev/cciss/c1d3p1]/returns: Error: Unable to satisfy all constraints on the partition.
err:
//Node[frobdignag.bar.foo.com]/foo_ukd/ukd_utpds::setup/ukd_utpds::filesystems_qa/ukd_utpds::filesystems_qa::create_partitions/Lvm::
Create_partition[c1d3p1]/Exec[create_partition-/dev/cciss/c1d3p1]/returns: change from notrun to 0 failed: /sbin/parted -s
/dev/cciss/c1d3 -- mkpart primary 0 -1 returned 1 instead of 0 at /var/puppet/1.7.15/modules-base/lvm/manifests/init.pp:242
notice:
//Node[frobdignag.bar.foo.com]/foo_ukd/ukd_utpds::setup/ukd_utpds::filesystems_qa/ukd_utpds::filesystems_qa::create_partitions/Lvm::
Create_partition[c1d3p1]/Exec[lvm_pvcreate-/dev/cciss/c1d3p1]: Dependency exec[/sbin/parted -s /dev/cciss/c1d3 -- mkpart primary 0 -1]
has 1 failures
warning:
//Node[frobdignag.bar.foo.com]/foo_ukd/ukd_utpds::setup/ukd_utpds::filesystems_qa/ukd_utpds::filesystems_qa::create_partitions/Lvm::
Create_partition[c1d3p1]/Exec[lvm_pvcreate-/dev/cciss/c1d3p1]: Skipping because of failed dependencies
---

When run manually against the same LUN, the following interactivity ensues:

---
# parted /dev/cciss/c1d3
GNU Parted 1.8.1
Using /dev/cciss/c1d3
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
Warning: The existing disk label on /dev/cciss/c1d3 will be destroyed and all data on this disk will be lost. Do you want to continue?
parted: invalid token: gpt
Yes/No? no
(parted) quit
Information: Don't forget to update /etc/fstab, if necessary.
#
---

It could be the case that the volumes you are trying to set GPT on, upon which this error is manifesting itself may have been setup previously by a different tool. The tool may not have properly set up the fake msdos partition table (which keeps older tools from clobbering the GPT partitions). 

In this type of scenario, it would be useful to have a '--force' option to
include in the scripted command.

	Why does the customer need this? (List the business requirements here)

To overcome the issue described above. The problem impacts their Puppet
configuration capabilities.

	How would the customer like to achieve this? (List the functional
	requirements here)

To be able to run 'parted -s --force', etc... to overcome warnings such as the
following automatically: 

---
Warning: The existing disk label on /dev/cciss/c1d3 will be destroyed and all data on this disk will be lost. Do you want to continue?
parted: invalid token: gpt
---

	For each functional requirement listed in question 4, specify how Red
	Hat and the customer can test to confirm the requirement is
	successfully implemented.

Through the ability to run the scripted command on a LUN manifesting this type
of error/warning and be able to use --force to automatically continue.

	Is there already an existing RFE upstream or in Red Hat bugzilla?

Not that I can find.

	How quickly does this need resolved? (desired target release)

As soon as possible.

	Does this request meet the RHEL Bug and Feature Inclusion Criteria
	(please review)

Yes.

	List the affected packages

parted

	Would the customer be able to assist in testing this functionality if
	implemented?

Yes.