| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Bug 4672
By using ip command instead of sysfs, avoid subshell quoting issues.
(cherry picked from commit 1755bfab4b22cc822f96fb78a1e05392d5f07398)
|
|
Need bonded device to have slave devices to inherit VLAN_CHALLENGED
property correctly
(cherry picked from commit 9b3608eb80a26061004db394d7535706fd2bae0b)
|
|
values.
(cherry picked from commit f6d95484a2f04633767409a565debe149ef5f56c)
|
|
(active plus working commited) nodes for comparison.
(cherry picked from commit a09624069795b49d12fd5d4be40dd2eb702b97a4)
|
|
Fix bug 4673.
(cherry picked from commit 35590240b908c8fbd4913990e5a1a75909ab9df2)
|
|
|
|
missing the last 4 bytes on 64 bit copy.
|
|
|
|
|
|
|
|
|
|
functional without additional testing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CREATE, DELETE, END, BEGIN) within a priority tree.
That means that all work (include the commit-check pass) will be
performed on a priority tree before proceeding to the next priority tree.
If a priority tree generates a failure in the commit-check pass
processing will halt on the priority tree and no further processing will
be performed on the priority tree. The failed priority tree will NOT be
copied to the active working directory.
All nodes in the priority tree will execute SYNTAX and COMMIT actions
except for nodes that have been deleted. Note this iteration is
performed on the working tree, so all commit-check nodes will either be
directly modified or have a node down the hierarchy that had been modified.
The working directory and active directory will not be modified until
after all priority trees have been processed.
|
|
Note that commit check only applies in the following cases:
1) On nodes or ancestors of nodes that have been set or modified
2) Does not applied to deleted nodes
Feature developers should:
1) locate commit checks at a common ancestor if checking across a hierarchy
2) expect that the commit check only enforces created behavior (therefore behaves more like a create check).
An additional flag is provided "-f" to allow for full syntax and commit checks. This allows a complete single pass on all syntax and
commit errors. The default behavior is to stop processing on the first error.
|
|
in the node.def. This change only affects display of nodes when -a option is used.
|
|
|
|
|
|
|
|
Bug 4501
This solves the problem that 'show interfaces ethernet' also
shows pseudo ethernet (peth0) device. The problem was that peth0
matched the regex since it was missing start/end.
(cherry picked from commit 71fb6be3ac3d7ce3c7f08b1408c8c9a6b9fc0422)
|
|
Move the speed/duplex setting into script where we can handle errors
better, and avoid setting speed/duplex twice.
(cherry picked from commit 330470f1f060f579434eb89469f4ed021c95449d)
|
|
This solves the problem that 'show interfaces ethernet' also
shows pseudo ethernet (peth0) device. The problem was that peth0
matched the regex since it was missing start/end.
(cherry picked from commit 77fb131b888bafd815722ebdceb5282b43dbb96d)
|
|
More bug 3952 fixes
(cherry picked from commit 2619f6c8fa01ab3ade6dfe6edb6815825c89cfd0)
|
|
Bugs 3952 and 3797
Make the ethtool settings management smarter.
Don't try and set a device that has been unplugged (causing commit fail).
Don't force autonegotiation if device is already in that mode.
(cherry picked from commit ad4f2a101203e71076a3e23a0a2a093326927d45)
|
|
update tag on loopback is incorrect since address is multi-value node.
(cherry picked from commit cd119fead01c35eae68b3383a2ab12fb9f2d4767)
|
|
|
|
passes regression
|
|
|
|
Post unionfs directory magic until after all actions have been applied to node tree.
|
|
|
|
|
|
|
|
|
|
"ENV_SIBLING_POSITION". This value will either be "FIRST" or "LAST" or undefined.
"FIRST" means that the sibling is the first in the list of a common parent, provided that the sibling resides in the same priority group
"LAST" means that the sibling is the last in the list of a common parent, provided that the sibling resides in the same priority group
|
|
|
|
Conflicts:
debian/changelog
|
|
|
|
|
|
|
|
Don't need OSPF/RIP parameters set after protocols/ospf anymore.
Setting bandwidth, etc after OSPF could cause unnecessary flapping.
|
|
|
