Skip to content

rename eos login/password variable name for clarity#793

Merged
lguohan merged 3 commits intosonic-net:masterfrom
lguohan:eospass
Jan 30, 2019
Merged

rename eos login/password variable name for clarity#793
lguohan merged 3 commits intosonic-net:masterfrom
lguohan:eospass

Conversation

@lguohan
Copy link
Contributor

@lguohan lguohan commented Jan 30, 2019

Signed-off-by: Guohan Lu gulv@microsoft.com

Description of PR

Summary:
Fixes # (issue)

Type of change

  • [] Bug fix
  • [] Testbed and Framework(new/improvement)
  • [] Test case(new/improvement)

Approach

How did you do it?

How did you verify/test it?

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

Signed-off-by: Guohan Lu <gulv@microsoft.com>
Signed-off-by: Guohan Lu <gulv@microsoft.com>
…t roles

Signed-off-by: Guohan Lu <gulv@microsoft.com>
@lguohan lguohan merged commit a88042a into sonic-net:master Jan 30, 2019
deerao02 pushed a commit to deerao02/sonic-mgmt that referenced this pull request Dec 18, 2025
…mbers on Broadcom (sonic-net#793)

<!--
Please make sure you've read and understood our contributing guidelines;
https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md

Please provide following information to help code review process a bit easier:
-->
### Description of PR
<!--
- Please include a summary of the change and which issue is fixed.
- Please also include relevant motivation and context. Where should reviewer start? background context?
- List any dependencies that are required for this change.
-->

Summary:
Fixes # (issue) https://github.com/aristanetworks/sonic-qual.msft/issues/629

### Type of change

<!--
- Fill x for your type of change.
- e.g.
- [x] Bug fix
-->

- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
 - [ ] Skipped for non-supported platforms
- [x] Test case improvement

### Back port request
- [x] 202412
- [x] 202505

### Approach
#### What is the motivation for this PR?
The `drop_packets` tests were intermittently failing on certain Broadcom platforms. The root cause was identified as the test selecting interfaces where the FEC counters are not functional.

#### How did you do it?
Update the `rif_members` construction logic. The logic for populating `rif_members` was modified to check the `minigraph_neighbors` for each interface. If an interface's neighbor device name contains the string "PT0", it is excluded from the list of potential test interfaces.

#### How did you verify/test it?
Run the `drop_packets` test suite on an affected Broadcom platform and confirmed that the tests now consistently pass by avoiding the problematic interfaces. The test continues to function correctly on other platforms where this issue is not present.

#### Any platform specific information?

#### Supported testbed topology if it's a new test case?

### Documentation
<!--
(If it's a new feature, new test case)
Did you update documentation/Wiki relevant to your implementation?
Link to the wiki page?
-->

Signed-off-by: zitingguo-ms <zitingguo@microsoft.com>
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
[config] Add 'config interface mtu' command sonic-net#793
add fec configuration 'config interface fec [OPTIONS] <interface_name>
<interface_fec>' sonic-net#764
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants