Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

invalid XML error from SUMA 4.3 #39

Open
kbmetz opened this issue Apr 2, 2023 · 2 comments
Open

invalid XML error from SUMA 4.3 #39

kbmetz opened this issue Apr 2, 2023 · 2 comments

Comments

@kbmetz
Copy link

kbmetz commented Apr 2, 2023

I'm trying to use https://github.com/SUSE/manager-build-profiles/tree/master/AutoYaST/SLES-12-SPn-to-SLES-15-SP2)/autoyast.xml and when the server attempts autoinstallation I'm getting the error 'Invalid XML' from the server when it boots and attempts to start the autoinstallation. This is on SUMA 4.3 using a Autoinstallation profile and this XML example

@aaannz
Copy link
Member

aaannz commented Apr 3, 2023

Thank you for the feedback. I assume you have correctly setup autoinstallation distribution and profile on the SUMA server.

On SUMA server please run cobbler profile get-autoinstall --name <name of the autoinstallation profile>. To get the correct name of the profile, you can list known profiles using cobbler profile list and find the one you specified in the WebUI, notice that there will be org id and name appended.

Once you get autoinstall xml from cobbler, compare it with the one from this repository, particularly if all $SNIPPET entries were replaced. Also check if there is no sensitive info and if you can provide it here that would help with finding the error.

@stdevel
Copy link

stdevel commented Jan 16, 2024

We're having the same issues with upgrading from SLES SAP 12.5 to SLES 15 SP5. We were using the SAP Client-Upgrade-12-SPn-to-15 profile from the repository.

When using the profile, the installer reports an issue with the following line:

<!-- when client is traditional registered, please use this snippet
      $SNIPPET('spacewalk/sles_register_script')
-->

We removed that comment and during the next run, the whole <script> block threw another error and we removed it:

  <scripts>
    <init-scripts config:type="list">
      $SNIPPET('spacewalk/minion_script')
    </init-scripts>
  </scripts>

Lastly, another error occured:

ERROR: Extra element software in interleave<br>137:0:
ERROR: Element profile failed to validate content

xmllint doesn't help here:

 # xmllint --noout --relaxng /usr/share/YaST2/schema/autoyast/rng/profile.rng /root/sap_autoyast.xml
Relax-NG validity error : Extra element software in interleave
/root/sap_autoyast.xml:137: element software: Relax-NG validity error : Element profile failed to validate content
/root/sap_autoyast.xml fails to validate

jing has some insights:

/root/sap_autoyast.xml:129:52: error: element "only_installed_packages" not allowed here; expected the element end-tag or element "stop_on_solver_conflict"
/root/sap_autoyast.xml:140:16: error: element "patterns" missing one or more required attributes; expected attribute "config:type", "t" or "type"
/root/sap_autoyast.xml:140:16: error: element "patterns" incomplete; expected element "listentry" or "pattern"

What do you think? I've also attached the XML as ZIP to this comment.

profile.zip

EDIT: It also looks like the installer (or cobbler) isn't able to substitue the $distotree variable - we needed to set it manually to the appropriate value.

EDIT2: We also opened the SUSE customer ticket 01081395 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants