Problem creating valid autoyast.xml file (SuSE 9.3) [Virus checked]
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
On Thursday 19 May 2005 19:54, Matthias.Eble@kaufland.de wrote:
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.
Is that machine a 9.3 too? I would suggest to start with an empty profile and then configure all you need (partitioning, software, network, root password) from scratch. Then you have a better overview on what you have configured in the profile.
With DTD:
/tmp/YaST2-15489-tNCLVw/valid.xml:12: element device_map: validity error : No declaration for attribute type of element device_map
^ What was wrong?
I don't know. It might help to see the profile.xml. Can you post it?
- File -> new shows no impact
thank you, that's a bug. I fixed that and you can download new RPMs from here: ftp://ftp.suse.com/pub/people/ug/RPMs/9.3/autoyast/
- 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
I'm not sure if I undrestand your question right but the <crpyt> tag does not meant that the partition is encrypted. So it can always be there and does not hurt. It's just an information IF the partition is encrypted.
- 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.
that's another bug (but that one I already knew) and it's fixed too in the RPMs above.
Is there a way to tell yast to create a xml file on installation time, like kickstart?
I don't know kickstart but wouldn't that be the "reference profile" from the autoyast UI? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Is that machine a 9.3 too? I would suggest to start with an empty
then configure all you need (partitioning, software, network, root
Uwe Gansert
from scratch. Then you have a better overview on what you have configured in the profile.
My aim is to clone this 9.3 machine. Starting with an empty profile looks kinda hard to me since I need to use LVM. Yast tells me: "For LVM and RAID setup, consult the documentation and add the configuration to an existing control file." Is the documentation mentioned the one located in /usr/share/doc/packages?
With DTD:
/tmp/YaST2-15489-tNCLVw/valid.xml:12: element device_map: validity
error :
No declaration for attribute type of element device_map
^ What was wrong? I don't know. It might help to see the profile.xml. Can you post it?
Where should it be located?
thank you, that's a bug. I fixed that and you can download new RPMs from here: ftp://ftp.suse.com/pub/people/ug/RPMs/9.3/autoyast/
- 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
I'm not sure if I undrestand your question right but the <crpyt> tagdoes not meant that the partition is encrypted. So it can always be there anddoes not hurt. It's just an information IF the partition is encrypted. Ok, you got me. It looked diffusing to me ;)
- Configuring my partition setup after generating a reference file
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.
that's another bug (but that one I already knew) and it's fixed too in
isn't the
RPMs above. Thank you.
Is there a way to tell yast to create a xml file on installation time, like kickstart?
I don't know kickstart but wouldn't that be the "reference profile" from
the
autoyast UI? That's right. Older RedHat installations (I think fedora still do) generated a kickstart file after installation. The machine can then be cloned using this file easily.
thank you. I'm going to try now..
On Friday 20 May 2005 16:09, Matthias.Eble@kaufland.de wrote:
My aim is to clone this 9.3 machine. Starting with an empty profile looks kinda hard to me since I need to use LVM. Yast tells me:
"For LVM and RAID setup, consult the documentation and add the configuration to an existing control file."
Is the documentation mentioned the one located in /usr/share/doc/packages?
/usr/share/doc/packages/autoyast2/html/ or http://yast.suse.com/autoinstall/ref.html LVM is documented there too. Unfortunatly I don't have any experiences with that topic but maybe someone else here.
error :
No declaration for attribute type of element device_map
^ What was wrong? I don't know. It might help to see the profile.xml. Can you post it?
Where should it be located?
that's your xml file for the configuration. That's the profile. Some people call it control.xml or control file but since there is a real control.xml on each SUSE Linux CD which has nothing to do with autoyast, I call it autoyast profile to prevent confusion (well, which did not work out in this case ;) ).
thank you, that's a bug. I fixed that and you can download new RPMs from
here:
ftp://ftp.suse.com/pub/people/ug/RPMs/9.3/autoyast/
buy the way, the RPMs are not there yet. I hope to get them on the ftp today but I can't promise.
Is there a way to tell yast to create a xml file on installation time, like kickstart?
I don't know kickstart but wouldn't that be the "reference profile" from the autoyast UI?
That's right. Older RedHat installations (I think fedora still do) generated a kickstart file after installation. The machine can then be cloned using this file easily.
I don't think there is such a mechanism to do it automtically. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Uwe Gansert
error :
No declaration for attribute type of element device_map
^ What was wrong? I don't know. It might help to see the profile.xml. Can you post it?
thank you, that's a bug. I fixed that and you can download new RPMs
from
here:
ftp://ftp.suse.com/pub/people/ug/RPMs/9.3/autoyast/
Thanks for the updates. It seems that yast shows the logical volumes exactly now.
Is there a way to tell yast to create a xml file on installation time, like kickstart?
I don't know kickstart but wouldn't that be the "reference profile" from the autoyast UI?
That's right. Older RedHat installations (I think fedora still does) generated a kickstart file after installation. The machine can then be cloned using this file easily.
I don't think there is such a mechanism to do it automtically.
Autoyast doesn't seem to be embedded to the SuSE installation routine.
Wouldn't it be easier to modify the default installer to generate the xml
files?
The installer already has the required plausibility checks and is very
easy to use.
In addition this would give the possibility to generate a profile.xml
after
every installation with very little effort.
So back to my problem. The dtd validation now tells me following:
/tmp/YaST2-25586-KulPYS/valid.xml:7: element device_map: validity error :
No declaration for attribute type of element device_map
On Monday 23 May 2005 10:30, Matthias.Eble@kaufland.de wrote:
So back to my problem. The dtd validation now tells me following:
/tmp/YaST2-25586-KulPYS/valid.xml:7: element device_map: validity error : No declaration for attribute type of element device_map
^
that looks like there is something wrong with the bootloader module if you
clone a system. I'll take a look at this.
In the meantime, if you did not do any changes to the bootloader config during
the installation of the reference system, you can remove the complete
bootloader section from the profile. It will be autodetected then during the
autoinstallation process. So just drop everything between <bootloader> and/or
replace it by a minimal more or less empty version:
<bootloader>
<activate config:type="boolean">false</activate>
<global config:type="list"/>
Uwe Gansert
replace it by a minimal more or less empty version:
<bootloader> <activate config:type="boolean">false</activate> <global config:type="list"/>
grub <location></location>false <sections config:type="list"/> </bootloader>If you did some changes to the bootloader proposal during the installation of the reference machine, just remove the
section.
Nothing was changed in the bootloader section during the installation, so
I
changed the bootloader properties to the ones you posted.
OK, we're getting better... :)
/tmp/YaST2-26198-xnfhXx/valid.xml:12: element sections: validity error :
Element sections content does not follow the DTD, expecting (section)+,
got
<sections config:type="list"/>
^
/tmp/YaST2-26198-xnfhXx/valid.xml:62: element lvm2: validity error : No
declaration for element lvm2
<lvm2 config:type="boolean">true</lvm2>
^
/tmp/YaST2-26198-xnfhXx/valid.xml:139: 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 lvm2 partitions pesize use )
</drive>
^
Now my xml looks like this:
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns"
xmlns:config="http://www.suse.com/1.0/configns">
<install>
<bootloader>
<activate config:type="boolean">false</activate>
<global config:type="list"/>
On Monday 23 May 2005 11:42, Matthias.Eble@kaufland.de wrote:
/tmp/YaST2-26198-xnfhXx/valid.xml:12: element sections: validity error : Element sections content does not follow the DTD, expecting (section)+, got <sections config:type="list"/>
okay, empty <sections> seem not to be allowed in bootloader section. Remove that line then, it's an empty list anyway. Strange, I would have sworn I already used an empty <sections> in bootloader.
/tmp/YaST2-26198-xnfhXx/valid.xml:62: element lvm2: validity error : No declaration for element lvm2 <lvm2 config:type="boolean">true</lvm2>
you can try to delete that line too but I'm afraid that might lead to trouble. I never did anything with lvm, not even without autoyast.
/tmp/YaST2-26198-xnfhXx/valid.xml:139: 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 lvm2 partitions pesize use ) </drive> ^
I have to dig deeper into XML and DTD to understand that. It might be a bug in the DTD file but honestly, I don't know that at the moment. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert@suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de
Not sure if it is useful but here is the drive part of an autoyast
file being used to build 9.3 machines.
--------
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<initialize config:type="boolean">false</initialize>
<partitions config:type="list">
<partition>
<filesystem config:type="symbol">swap</filesystem>
<format config:type="boolean">true</format>
On Friday 20 May 2005 16:09, Matthias.Eble@kaufland.de wrote:
My aim is to clone this 9.3 machine. Starting with an empty profile looks kinda hard to me since I need to use LVM. Yast tells me:
"For LVM and RAID setup, consult the documentation and add the configuration to an existing control file."
Is the documentation mentioned the one located in /usr/share/doc/packages?
/usr/share/doc/packages/autoyast2/html/ or http://yast.suse.com/autoinstall/ref.html
LVM is documented there too. Unfortunatly I don't have any experiences with that topic but maybe someone else here.
participants (3)
-
Mark Keir -
Matthias.Eble＠kaufland.de -
Uwe Gansert