That looks right to me, at least to fix the issue as you described. How often does the issue occur? I have had issues with flakiness of the password server in the past but it has been a few months since I have seen an issue, last one was well before I started looking at code.
If it fixes your problem we should submit it for 4.0.1 as well. On Nov 22, 2012 5:11 AM, "Rohit Yadav" <[email protected]> wrote: > > On 22-Nov-2012, at 4:43 PM, Rohit Yadav <[email protected]> wrote: > > > Issue: cloud-passwd-server and (the default) iptables have the same run > level in /etc/rcS.d (S13xxx). By default port 8080 is not opened, and > cloud-passwd-server checks and enables port such that it accepts traffic > from the guest cidr only. The issue is sometimes, the default iptables > rules are applied after the password server has been started which causes > the port 8080 related rules to be flushed. > > > > How is systemvm template created? > > Found a partial answer by reading the code, still if anyone wants to > discuss. > > > How do we set run level for a service, how to change sequence of > services to start in a defined way? > > Okay got the fix, you're supposed to fix them in a comment block for all > init.d scripts and specify required processes and run levels; > --- a/patches/systemvm/debian/config/etc/init.d/cloud-passwd-srvr > +++ b/patches/systemvm/debian/config/etc/init.d/cloud-passwd-srvr > @@ -1,7 +1,7 @@ > #!/bin/bash > ### BEGIN INIT INFO > # Provides: cloud-passwd-srvr > -# Required-Start: mountkernfs $local_fs cloud-early-config > +# Required-Start: mountkernfs $local_fs cloud-early-config > iptables-persistent > # Required-Stop: $local_fs > # Should-Start: > # Should-Stop: > > Pl. check, if what I found is correct? > > Thanks. > > > > > Regards. > >
