- refactor handling of configuration values (supports environment variables
to override configuration values and accepts missing config file)
- add different modes how to list and group the output
- add different levels of verbosity
- add --rh-search and --rh-search-since flag
Signed-off-by: Thomas Haller <thaller@redhat.com>
Configure jenkins project to accept a boolean build parameter "RPM" to
control whether to build the RPM packages.
Also, adjust the trigger_build.sh script, to support this parameter and
accept command line arguments.
Signed-off-by: Thomas Haller <thaller@redhat.com>
makerepo.sh failed on RHEL6, because
- realpath was not available
- git-config did not understand the --local option
Fix these issues.
Signed-off-by: Thomas Haller <thaller@redhat.com>
Also, allow makerepo.sh not to be in the root directory of the
dist-git checkout. Instead, your current working directory
must now be inside the git working copy
Signed-off-by: Thomas Haller <thaller@redhat.com>
This script can be used when backporting patches in dist-git for
Fedora and RHEL. Try `./makerepo.sh -h`
Signed-off-by: Thomas Haller <thaller@redhat.com>
Lease expiry means that the DHCP configuration is no longer valid, and
that all attempts to renew/rebind the lease have failed. The IP config
needs to be removed. NetworkManager also sets prefered/valid lifetimes
on addresses, so the kernel will remove them when the lease expires
anyway. That causes removal of the default route, if the default route
was through the device whose config has now expired.
DHCP clients will typically move to the 'renew' or 'rebind' states when
nearing lease expiry, then if no answer is received move to the 'expire'
state. Eventually they move to the 'fail' state when all attempts to
contact the server have failed.
Previously, since NM ignored the 'expire' DHCP state it would not clear
out the DHCP IP4 config immediately when the lease expired, instead
waiting for the DHCP client to move to the 'fail' state. But if the
DHCP server appeared between the 'expire' and 'fail' states, NM would
not notice and the device's NMIP4Config would not change, and thus the
Policy would not get the "ip4-config-changed" signal to re-add the
default route that the kernel had previously removed due to the valid
lifetime reaching zero when the lease expired.
https://bugzilla.redhat.com/show_bug.cgi?id=1139326
If DHCP fails to renew or rebind a lease, fail the device since the
IP config is no longer valid. Commit e2b7c482 was actually wrong for
dhcp[4|6]_fail(), since (ip_state == IP_FAIL) will never be true if
DHCP has ever been started, as IP_FAIL is only set from
nm_device_activate_ip[4|6]_config_timeout(), which obviously will not
be called in DHCP code paths if DHCP has previously succeeded.
