Hi autoinstall list,
I've got a problem creating autoyast xml files on a HP-BL20pg3 server
(SuSE 9.3).
The result of the creation of the xml file doesn't seem to be valid at
all.
Here are the steps I did
1. started yast/yast2: chose misc -> autoinstallation I got an empty set
of basic settings.
2. create the reference file: Tools ->Create Reference Profile.
3. chose system services (runlevel) only - for simplicity
4. create... looks good up to then
5. let's check the result: Tools-> check validity..
Without DTD: OK
With DTD:
/tmp/YaST2-15489-tNCLVw/valid.xml:12: element device_map: validity error :
No declaration for attribute type of element device_map
^
/tmp/YaST2-15489-tNCLVw/valid.xml:14: element firmware: validity error :
No declaration for element firmware
<firmware>(hd0)</firmware>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:15: element linux: validity error : No
declaration for element linux
<linux>/dev/cciss/c0d0</linux>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:16: element device_map_entry: validity
error : No declaration for element device_map_entry
^
/tmp/YaST2-15489-tNCLVw/valid.xml:17: element device_map: validity error :
No declaration for element device_map
^
/tmp/YaST2-15489-tNCLVw/valid.xml:83: element bootloader: validity error :
Element bootloader content does not follow the DTD, expecting (activate? ,
global? , initrd_modules? , loader_device? , loader_type? , location? ,
repl_mbr? , sections?), got (activate device_map global initrd_modules
loader_device loader_type location repl_mbr sections )
</bootloader>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:103: element keep_partition_fsys:
validity error : No declaration for attribute type of element
keep_partition_fsys
^
/tmp/YaST2-15489-tNCLVw/valid.xml:104: element keep_partition_id: validity
error : No declaration for attribute type of element keep_partition_id
^
/tmp/YaST2-15489-tNCLVw/valid.xml:105: element keep_partition_num:
validity error : No declaration for attribute type of element
keep_partition_num
^
/tmp/YaST2-15489-tNCLVw/valid.xml:105: element keep_partition_num:
validity error : No declaration for element keep_partition_num
^
/tmp/YaST2-15489-tNCLVw/valid.xml:109: element filesystem_id: validity
error : No declaration for attribute type of element filesystem_id
131
^
/tmp/YaST2-15489-tNCLVw/valid.xml:109: element filesystem_id: validity
error : No declaration for element filesystem_id
131
^
/tmp/YaST2-15489-tNCLVw/valid.xml:118: element size: validity error : No
declaration for attribute type of element size
<size config:type="integer">100270081</size>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:119: element partition: validity error :
Element partition content does not follow the DTD, expecting (create |
crypt | crypt_fs | crypt_key | filesystem | format | fs_options | fstopt |
grow | label | loop_fs | lv_name | lvm_group | maxsize | mount | mountby |
noauto | partition_id | partition_nr | partition_type | raid_name |
raid_options | raid_type | region | size | usepart)*, got (filesystem
filesystem_id format mount partition_id partition_nr region size )
</partition>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:121: element filesystem_id: validity
error : No declaration for attribute type of element filesystem_id
142
^
/tmp/YaST2-15489-tNCLVw/valid.xml:121: element filesystem_id: validity
error : No declaration for element filesystem_id
142
^
/tmp/YaST2-15489-tNCLVw/valid.xml:129: element size: validity error : No
declaration for attribute type of element size
<size config:type="integer">72716697601</size>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:130: element partition: validity error :
Element partition content does not follow the DTD, expecting (create |
crypt | crypt_fs | crypt_key | filesystem | format | fs_options | fstopt |
grow | label | loop_fs | lv_name | lvm_group | maxsize | mount | mountby |
noauto | partition_id | partition_nr | partition_type | raid_name |
raid_options | raid_type | region | size | usepart)*, got (filesystem_id
lvm_group partition_id partition_nr region size )
</partition>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:133: element drive: validity error :
Element drive content does not follow the DTD, expecting (device? ,
initialize? , is_lvm_vg? , partitions? , pesize? , use?), got (device
keep_partition_fsys keep_partition_id keep_partition_num partitions use )
</drive>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:137: element keep_partition_fsys:
validity error : No declaration for attribute type of element
keep_partition_fsys
^
/tmp/YaST2-15489-tNCLVw/valid.xml:138: element keep_partition_id: validity
error : No declaration for attribute type of element keep_partition_id
^
/tmp/YaST2-15489-tNCLVw/valid.xml:139: element keep_partition_num:
validity error : No declaration for attribute type of element
keep_partition_num
^
/tmp/YaST2-15489-tNCLVw/valid.xml:139: element keep_partition_num:
validity error : No declaration for element keep_partition_num
^
/tmp/YaST2-15489-tNCLVw/valid.xml:140: element lvm2: validity error : No
declaration for element lvm2
<lvm2 config:type="boolean">true</lvm2>
^
/tmp/YaST2-15489-tNCLVw/valid.xml:217: element drive: validity error :
Element drive content does not follow the DTD, expecting (device? ,
initialize? , is_lvm_vg? , partitions? , pesize? , use?), got (device
is_lvm_vg keep_partition_fsys keep_partition_id keep_partition_num lvm2
partitions pesize use )
</drive>
^
What was wrong?
This is the first thing i do with this system after the fresh
installation.
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg00-lv_root
5.0G 162M 4.6G 4% /
tmpfs 2.0G 0 2.0G 0% /dev/shm
/dev/cciss/c0d0p1 99M 8.2M 86M 9% /boot
/dev/mapper/vg00-lv_home
1008M 33M 925M 4% /home
/dev/mapper/vg00-lv_tmp
1008M 33M 925M 4% /tmp
/dev/mapper/vg00-lv_usr
2.0G 613M 1.3G 32% /usr
/dev/mapper/vg00-lv_var
2.0G 71M 1.8G 4% /var
We have been using autoyast for about one year now. But it has never
given us the impression of being in productive state.
The dialogs to create a control file manually seem to be kinda unready,
too.
- The dialog inserts mount points for LVM, swap or md partitions by
default and accepts them.
- File -> new shows no impact
- created a dummy partition maually without the crypt option being
checked:
<partition>
<crypt>twofish256</crypt> ... I don't know the internals,
perhaps I'm wrong, but.. maybe you can tell me
- Configuring my partition setup after generating a reference file isn't
possible. The left bar tells me sth
about a table to the right. Unfortunately there is no table to the right -
there is no problem, when start with an empty setup.
Did you experience problems like this, too?
I clouldn't find any patches up to now.
Is there a way to tell yast to create a xml file on installation time,
like kickstart?
Thanks for your hints
Matthias
