(I'm new to SuSE & AutoYaST, and not sure whether this is a problem with AutoYaST, or a SuSE package, or my own mistake...)
I noticed that configuring both <proxy> and <suse_register> in an autoyast profile fails if <no_proxy> is needed to access the SMT server.
What seems to happen is that the <proxy> section of the autoyast profile is parsed, but the root user's .curlrc file only gets the --proxy setting and not any --noproxy setting. This makes SMT registration fail.
A workaround is to have a script like this in the autoyast profile:
<chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <source><![CDATA[ echo "--noproxy 'localhost,.example.com'" >> /root/.curlrc ]]> </source> </script> </chroot-scripts>
So, this message is partly for the benefit of people searching the list archives, but also an open question whether anyone else is aware of the problem.
For info, I am installing from a SLES 11 SP2 DVD, and the suseRegister package version is 1.4-1.24.1.