command is not run on reboot

Bug #1334804 reported by Clint Byrum
This bug affects 4 people
Affects Status Importance Assigned to Milestone

Bug Description

If a system has rebooted, we should run the command again until it succeeds. This will handle the case where ephemeral state such as iptables rules or sysctl settings are asserted by the command.

This was most recently highlighted by this mailing list post:

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-collect-config (master)

Fix proposed to branch: master

Changed in os-collect-config:
assignee: nobody → Michael Kerrin (michael-kerrin-w)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-collect-config (master)

Change abandoned by Michael Kerrin (<email address hidden>) on branch: master
Reason: Time has moved on. A lot of work and a lot of people need to be on board for this to work.

In the past using o-r-c on reboot seemed the easiest thing to do as we where missing a lot of infrastructure that has since been added. A lot of work will need to be undone to get to using o-r-c on reboot. I could have listed the issues before that o-r-c would solve but can't now.

Changed in os-collect-config:
assignee: Michael Kerrin (michael-kerrin-w) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers