Autoupgrade to SLE15 from SCC and SMT #4707
Conversation
Workaround for bsc#1084997: removing packages libburnia-tools error during upgrade from SLE 12 to 15. -poo#33784
The autoyast profile required to autoupgrade from SLES 12 to 15 via SCC. -poo#33778
To support autoupgrade SLE 12 -> 15 via SMT, the untrusted certificate of SMT should be imported -poo#33778
QingmingSu
force-pushed
the
sle15_upgrade
branch
from
4138508
to
2c2ed8b
Compare
|
The failure at the end of installation should be a bug of autoyast, I will report a bug against it. |
| next; | ||
| } | ||
| elsif (match_has_tag('ERROR-removing-package')) { | ||
| send_key 'alt-i'; # ignore |
There was a problem hiding this comment.
Do we have a bug for this scenario? I would add soft_failure here as it doesn't look like expected behavior.
There was a problem hiding this comment.
Yes, we have a bug bsc#1084997: removing packages libburnia-tools failed during upgrade.
ERROR-removing-package could happen on any package, it would be misunderstanding if I add record_soft_failure("bsc#1084997") here but another package failed to remove after libburnia-tools issue fixed.
So I prefer to create package specific needle with "workaround" label, just like the existing one for libburnia-tools:
ERROR-removing-package-bsc1084997-20180320.json
ERROR-removing-package-bsc1084997-20180320.png
There was a problem hiding this comment.
@rwx788 about your concern I had already talked offline with @QingmingSu. So let me merge it since we need autoupgrade on o.s.d. asap.
| <upgrade> | ||
| <stop_on_solver_conflict config:type="boolean">true</stop_on_solver_conflict> | ||
| </upgrade> | ||
| </profile> |
There was a problem hiding this comment.
The profile looks not properly for sle15, that maybe the reason of failure: http://openqa-apac1.suse.de/tests/555#step/installation/44
Please refer this: https://github.com/os-autoinst/os-autoinst-distri-opensuse/blob/master/data/autoyast_sle15/autoyast_gnome.xml
There was a problem hiding this comment.
Or maybe you need this: https://github.com/yast/yast-registration/wiki/Available-SCC-Extensions-for-Use-in-Autoyast#sles-15
@rwx788 as a autoyast expert, could you give some hint about autoyast profile on sle15 upgrade? Thanks.
There was a problem hiding this comment.
I actually was surprised that no repos are defined and no modules activated in the profile, but I'm not sure how is it supposed to look like
There was a problem hiding this comment.
I'm not sure about upgrade scenarios, I guess it's better to ask on #yast irc channel. But I would expect registration part similarly as we have here, for instance. But somehow we get packages, as we end up with minimal x, which cannot be done with unregistered system.
There was a problem hiding this comment.
@mitiao , @rwx788
Yes, there is no registration code and modules in the autoyast profile, because it showed an error when I included them in the profile, such as:
<suse_register>
<do_registration config:type="boolean">true</do_registration>
<email/>
<reg_code>{{SCC_REGCODE}}</reg_code>
<install_updates config:type="boolean">true</install_updates>
<reg_server>{{SCC_URL}}</reg_server>
<addons config:type="list">
<addon>
<name>sle-module-server-applications</name>
<version>{{VERSION}}</version>
<arch>{{ARCH}}</arch>
</addon>
<addon>
<name>sle-module-desktop-applications</name>
<version>{{VERSION}}</version>
<arch>{{ARCH}}</arch>
</addon>
<addon>
<name>sle-legacy</name>
<version>{{VERSION}}</version>
<arch>{{ARCH}}</arch>
</addon>
</addons>
</suse_register>
Maybe some section is still missing in my autoyast profile, but I can't figure it out.
There was a problem hiding this comment.
Do you pass settings? We expand variables in {{}} which is done in prepare_profile test module. It's scheduled with AUTOYAST_PREPARE_PROFILE setting. Not sure if smt registration has any special flow. As I've said, best way to ask yast team, which I can do later today. Unfortunately, we have end of the sprint and some meetings.
It is required to test autoupgrade (upgrade with autoyast) from SLE 12 to 15 via SCC or SMT.