Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 101621 - unrecognized ks command: part
unrecognized ks command: part
Product: Red Hat Linux Beta
Classification: Retired
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Mike McLean
Depends On:
Blocks: CambridgeBlocker
  Show dependency treegraph
Reported: 2003-08-04 15:38 EDT by Mike McLean
Modified: 2007-04-18 12:56 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-13 12:02:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike McLean 2003-08-04 15:38:17 EDT
* Cambridge-re0801.nightly (internal)
* kickstart install
* cpqarray box
* using the --onpart option

I'm getting a traceback (during kickstart validation i presume).

Traceback (most recent call last):
  File "/usr/bin/anaconda", lin 986, in ?
  File "/usr/lib/anaconda/kickstart.py", line 1239 in setInstallData
    self.ReadKickstart(id, self.file)
  File "/usr/lib/anaconda/kickstart.py", line 691 in ReadKickstart
    raise SyntaxError, "Unrecognized ks command: %s\n On the line: %s" %
(args[0], n)
Syntax error: unrecognized ks command: part 
On the line: part / --size 1024 --onpart ida/c0d0p2 --noformat

Here is the partitioning section of the kickstart:
# clearpart is disabled
part /last --size 1024 --onpart ida/c0d0p1 --noformat
part / --size 1024 --onpart ida/c0d0p2 --noformat
part swap --onpart ida/c0d0p3

Note the order: anaconda complained on the *second* part command.

Also note that tons of kickstart cases for this same build have passed without
hitting this.  Two things make this case special:
  - the onpart option
  - the cpqarray
Comment 2 Jeremy Katz 2003-08-04 15:58:03 EDT
Did you perhaps not have an ida/c0d0p3 partition?  There was some exception
handling changed in Cambridge that was being over-zealous.
Comment 3 Mike McLean 2003-08-04 19:01:59 EDT
I'm pretty sure that the partition was there.  This case does one install with
"/" and "/next" partitions.  Then it does a second install with "/" on the old
/next partition and "/last" on the old / partition.  The devices used for the
--onpart option would have been pulled from /etc/mtab.

I'll rerun the testcase just to be sure.

If this is the case, then the error message is very misleading.
Comment 4 Jeremy Katz 2003-08-04 19:17:23 EDT
Like I said, the exception catching was a bit broad there.  I've fixed that
(should show up in tomorrow's nightly I think -- I'll build an anaconda before I
leave to ensure it).  Then again, it could be some other exception entirely and
it would have been completely covered up :/

So results from tomorrow's tree would be interesting :)
Comment 5 Mike McLean 2003-08-04 20:20:00 EDT
I'm poking around on VC2 post-traceback.  The partition appears in
/proc/partitions, and I am able to mount it manually.

Nothing odd appears in anaconda.log.
Comment 6 Mike McLean 2003-08-04 20:36:55 EDT
the cpqarray has nothing to do with it. The case has failed on several different
Comment 7 Mike McLean 2003-08-05 15:29:57 EDT
The traceback looks exactly the same in Cambridge-re0805.nightly
Comment 8 Mike McLean 2003-08-05 16:06:46 EDT
A slightly simpler testcase fails also (this one has no --noformat option).
Comment 10 Jeremy Katz 2003-08-06 14:46:37 EDT
Fixed for real
Comment 11 Mike McLean 2003-08-13 12:02:55 EDT

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