'[Spacewalk-list] Re-provisioning issues'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       spacewalk-list
Subject:    [Spacewalk-list] Re-provisioning issues
From:       Tomi Salmi <tomisalmi123 () gmail ! com>
Date:       2012-10-25 7:44:36
Message-ID: CAHrPdoazisgyKXj9=pAwpyB7UvokC8uuU03fAuEtP9zvkAeikQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

Hi,

I'm noticing some unexpected behaviour when re-provisioning physical Fedora
16 systems from Spacewalk 1.7. While the following problems are most likely
not directly related to each other, they are a part of the same workflow.

1) In my environment, most network interfaces get renamed to p5p1 or
similar during the initial bare-metal install, which works flawlessly.
However, re-provisioning a system from Spacewalk causes Cobbler to add an
additional eth0 interface to the profile with the same preferences as the
original interface has. This will generate a duplicate entry in dnsmasq
(managed by cobbler), which then causes dnsmasq to crash/stop.

2) The webgui does not update the "deploy configuration files" and
"kickstart complete" checkmarks when re-provisioning a system, while the
client has finished all steps succesfully. I have added "reset_base_channel
= 0" to /usr/share/rhn/config-defaults/rhn_server.conf but it should be the
cause of this issue?

Basically, re-provisioning a system from SW leaves me with dnsmasq stopped
and a never ending kickstart task in the webgui.

Any advice or suggestions are welcome.

Best regards,
Tomi Salmi

[Attachment #5 (text/html)]

<div>Hi,</div><div> </div><div>I&#39;m noticing some unexpected behaviour when \
re-provisioning physical Fedora 16 systems from Spacewalk 1.7. While the following \
problems are most likely not directly related to each other, they are a part of the \
same workflow.</div> <div> </div><div>1) In my environment, most network interfaces \
get renamed to p5p1 or similar during the initial bare-metal install, which works \
flawlessly. However, re-provisioning a system from Spacewalk causes Cobbler to add an \
additional eth0 interface to the profile with the same preferences as the original \
interface has. This will generate a duplicate entry in dnsmasq (managed by cobbler), \
which then causes dnsmasq to crash/stop.</div> <div> </div><div>2) The webgui does \
not update the &quot;deploy configuration files&quot; and &quot;kickstart \
complete&quot; checkmarks when re-provisioning a system, while the client has \
finished all steps succesfully. I have added &quot;reset_base_channel = 0&quot; to \
/usr/share/rhn/config-defaults/rhn_server.conf but it should be the cause of this \
issue?</div> <div> </div><div>Basically, re-provisioning a system from SW leaves me \
with dnsmasq stopped and a never ending kickstart task in the webgui. </div><div> \
</div><div>Any advice or suggestions are welcome.</div><div> </div><div> Best \
regards,</div><div>Tomi Salmi</div>

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

[prev in list] [next in list] [prev in thread] [next in thread] 