fix(kebernetes): Apply fixes listed in issues #108
Closed
jasonpage.tas wants to merge 0 commits from
fixes
into development
pull from: fixes
merge into: ansible-collections:development
ansible-collections:development
ansible-collections:remove-cni
ansible-collections:master
No Reviewers
Labels
Clear labels
Bug
Used in discussion about a bug in comments or commits
CVE-2023-5764
Denotes items related to the CVE
CodeReview
Used in comments (issues/MR/commits) to denote code review related items
Documentation
Documentation items
Feature
Used in discussion about a Feature in comments or commits
Lint
Used in comments (issues/MR/commits) to denote lint tasks todo, done, fixed
Privacy
Used in comments (issues/MR/commits) to denote privacy related items
Security
Used in comments (issues/MR/commits) to denote Security related items
breaking-change
label used to denote that the issue/Merge Request does/will introduce a breaking change
bug::reproducable
Given to an issue when the bug has been confirmed as re-producable. Can also be used in comments and commits.
bug::unable to reproduce
Given to an issue when the bug that is not able to be reproduced. Can also be used in comments and commits.
code review::complete
code review::not started
code review::rejected
code review::underway
difficulty::Full Development
Level 3. Difficulty representing that the task to complete must be planned and created.
difficulty::Good First Issue
Level 1. Difficulty representing that the task is very simple and with limited knowledge can be completed.
difficulty::Prior Knowledge
Level 2. Difficulty representing that the task requires some prior knowledge of either the technology or the project for task completion.
documentation::complete
Issues, Merge Requests
documentation::no change required
Issues, Merge Requests and used to denote no documentation changes required
documentation::not started
Issues, Merge Requests
documentation::stalled
Issues, Merge Requests
documentation::underway
Issues, Merge Requests
impact::0
impact::1
impact::2
impact::3
impact::4
impact::5
ops::ansible-roles
OPS project tag
ops::automation
ops::gitlab-ci
OPS project tag
ops::marcas
OPS project tag
ops::python-gitlab-management
OPS project tag
ops::website
priority::0
priority::1
priority::2
priority::3
priority::4
priority::5
stage::Ready for Development
stage::develop
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::feedback required
stage::planning
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stage::test
Stage for use in Issues and Merge Requests. Can also be used in discussion in comments and commits
stale
Label given to issues/merge requests that are considered stale due to no collaboration and is a mark for closure.
triage
Tag given to issues/merge requests requiring triaging by the team.
triage::not_confidential
This tag is given by the triage bot so that URLs can be added to an issue/comment. A triage policy for NFC wide should remove this label.
type::CI / CD
type::automation
This type is used to denote an automation job
type::bug
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::compliance
type::discussion
Type for Issues. Can also be used in discussion in comments.
type::documentation
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::feature
type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::invalid
label given to tickets that require no action or are deem as invalid.
type::quality assurance
Type for Issues and Merge Requests. Can also be used in discussion in comments and commits
type::question
Type for Issues. Can also be used in discussion in comments.
type::security
Type for Issues and Merge Requests.
type::specification
Design specification
v1.0.0
Version that is affected
v1.0.1
Version that is affected
v1.1.0
Version that is affected
v1.1.1
Version that is affected
v1.1.2
Version that is affected
v1.10.0
Version that is affected
v1.10.1
Version that is affected
v1.10.2
Version that is affected
v1.10.3
Version that is affected
v1.11.0
Version that is affected
v1.12.0
Version that is affected
v1.13.0
Version that is affected
v1.13.1
Version that is affected
v1.13.2
Version that is affected
v1.2.0
Version that is affected
v1.3.0
Version that is affected
v1.4.0
Version that is affected
v1.5.0
Version that is affected
v1.6.0
Version that is affected
v1.7.0
Version that is affected
v1.7.1
Version that is affected
v1.7.2
Version that is affected
v1.8.0
Version that is affected
v1.8.1-a1
Version that is affected
v1.8.1-a2
Version that is affected
v1.9.0
Version that is affected
workflow::complete
Issues, Merge Requests
workflow::not ready
workflow::not ready::blocked
workflow::not started
Issues, Merge Requests
workflow::ready to commence
Issues, Merge Requests
workflow::stalled
Label given to issues/merge requests where no work has occured in x days iaw triage policy.
workflow::underway
Issues, Merge Requests
workflow::underway::develop
Area/CI-CD
Documentation changes
Area/Documentation
Documentation changes
Area/Security
This is security issue
Area/Testing
Issue or pull request related to testing
Bug
Failure to Confirm
Bug exists due to not confirming/testing code
Bug
Regression
THe bug is a regression of a feature
Bug
To be Confirmed
This bug is not confirmed
Bug
Unable to Reproduce
A developer can not re-create/re-produce the bug
Compat/Breaking
Breaking change that won't be backward compatible
Impact
Critical
1
The impact is critical in that it is blocking or prevents usage.
Impact
High
2
The impact requires that changes be made for continuted usage.
Impact
Low
4
The impact requires the user approach from a different angle for continued usage.
Impact
Medium
3
The impact requires a workaround for continued usage.
Impact
Very Low
5
The impact has a slight effect on usage.
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Priority
Very High
1
The priority is critical
Priority
Very Low
5
The priority is very low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Type
Bug
Something is not working
Type
Epic
Epic User Story
Type
Feature
Feature / Module
Type
Incident
Something occured related to a service
Type
RFE
Request for Enhancement
Type
Task
A work item that must be done
Urgency
Low
4
Prioritize this amoungst your list of things to do.
Urgency
Major
1
Urgency is so high it should have been dealt with last week.
Urgency
Medium
3
Start as soon as possible.
Urgency
Very High
2
Urgency is high enough to warrant near immediate commencement.
Urgency
Very Low
5
Add this to your list of things to do.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ansible-collections/kubernetes#108
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📚 Summary
nofusscomputing/projects/ansible/collections/kubernetes#33 var 'kubernetes_config.cluster.prime.name' still used in templates
nofusscomputing/projects/ansible/collections/kubernetes#32 ip6tables not set to legacy mode
🔗 Links / References
👷 Tasks
Playbook Update
This collection has a corresponding playbook that may need to be updated (Ansible Role), specifically Role Validation.
NetBox Rendered Config Update
This Collection has a NetBox Rendered Config template that may need to be updated. Specifically Section
cluster.type == 'kubernetes'
changed the description
assigned to @jasonpage.tas
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
you have removed the checks to determin if the node is the prime node. these need to remain for obvious reasons. the variable to determine if the host is a prime node is
nfc_role_kubernetes_prime
, which is of typeboolean
you have removed the checks to determin if the node is the prime node. these need to remain for obvious reasons. the variable to determine if the host is a prime node is
nfc_role_kubernetes_prime
, which is of typeboolean
you have removed the checks to determin if the node is the prime node. these need to remain for obvious reasons. the variable to determine if the host is a prime node is
nfc_role_kubernetes_prime
, which is of typeboolean
fix commits
kubernetes_role
nofusscomputing/projects/ansible/collections/kubernetes#32
=#32
added 10m of time spent
requested changes
changed this line in version 3 of the diff
changed this line in version 3 of the diff
changed this line in version 3 of the diff
added 2 commits
Compare with previous version
changed this line in version 5 of the diff
changed this line in version 5 of the diff
changed this line in version 5 of the diff
added 1 commit
f5bba112
- feat(kubernetes_role): set ip6tables to legacy modeCompare with previous version
added 1 commit
Compare with previous version
@jon_nfc
review 255cc01b79591acb9a889be1905439a75f6155e9
@jon_nfc
this variable has also been found in another location roles/nfc_kubernetes/tasks/k3s/migrate_to_operator.yaml
Should this be adjusted as well?
nfc_role_kubernetes_prime
is booleannfc_role_kubernetes_prime
is booleannfc_role_kubernetes_prime
is booleannfc_role_kubernetes_prime
is booleanadded 3m of time spent
requested changes
added 1 commit
576ab623
- fix(kubernetes_role): update var kubernetes_config.cluster.prime.name -> nfc_role_kubernetes_primeCompare with previous version
changed this line in version 8 of the diff
changed this line in version 8 of the diff
changed this line in version 8 of the diff
added 1 commit
28c4e3bb
- feat(kubernetes_role): set var nfc_role_kubernetes_prime type booleanCompare with previous version
@jon_nfc
tentatively requesting a review
missed that one. Also not sure how to do that......
would it be
requested review from @jon_nfc
inventory_hostname
is of type string andnfc_role_kubernetes_prime
is of type boolean a non-strict logical comparison will fail.review the failed test jobs logs as there is an error in the playbook. if the job fails (there are 4 different os's tested), the deployment should at least pass.
inventory_hostname
is of type string andnfc_role_kubernetes_prime
is of type boolean a non-strict logical comparison will fail.no, as currently
https://" + hostvars[nfc_role_kubernetes_prime |default(false) | boolean].ansible_host + ":6443"
will produce an error which more than likely will crash ansible. however when correctly defined would expand tohttps://false:6443
orhttps://true:6443
for non-prime and prime respectively.inventory_hostname
is of type string andnfc_role_kubernetes_prime
is of type boolean a non-strict logical comparison will fail.inventory_hostname
is of type string andnfc_role_kubernetes_prime
is of type boolean a non-strict logical comparison will fail.point of note when working with logical comparisons is to consider what the values are left and right of the comparitor. if they are not of the same type, generally the comparison will fail without an error, as is the case with python-it will crash and return a stack trace.
added 13m of time spent
requested changes
Genuinely got no idea
changed this line in version 9 of the diff
changed this line in version 9 of the diff
changed this line in version 9 of the diff
added 1 commit
a2580f93
- fix(kubernetes_roles): update variable nfc_role_kubernetes_prime type to booleanCompare with previous version
changed this line in version 10 of the diff
added 1 commit
14a2cbed
- fix(kubernetes_role): set variable prime_hostnameCompare with previous version
added 1 commit
4d51d3ca
- fix(kubernetes_roles): update variable nfc_role_kubernetes_prime |...Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
2d5eb7c3
- fix(kubernetes_roles): update cmd for setting ip6tablesCompare with previous version
added 2 commits
044c9146
- feat(kubernetes_role): nfc_role_kubernetes_prime cast type to bool55cc0075
- fix(kubernetes_roles): use inventory_hostnameCompare with previous version
Pipeline passed with errors. The issue is I do not even understand the errors to be able to begin fault finding this.
I did not expect that the changes in
55cc0075
would work. However the error log has confused me further as I cannot see where the unexpected char is.See error log below:
Error log
Changed
to comment out an item in jinga substitute the
%
for#
. i.e.{% jinja %}
would become{# jinja #}
.any jinja placed within a standard comment line (prefixed with
#
), will still be parsed by the jinja templating engine.added 5m of time spent
requested changes
I can make that change but it will likely use my remaining compute usage. I'm at 346 of 400 for this month.
changed this line in version 16 of the diff
added 1 commit
23808704
- fix(kubernetes_role): remove commented out sectionCompare with previous version
added 1 commit
d59f2007
- test(kubernetes_role): set prime default value to trueCompare with previous version
mentioned in commit
576ab623d8
mentioned in commit
14a2cbed98
mentioned in commit
55cc007575
mentioned in commit
4d51d3ca00
mentioned in commit
2d5eb7c375
mentioned in commit
a2580f9328
mentioned in commit
044c914617
mentioned in commit
28c4e3bbca
mentioned in commit
f5bba112cf
mentioned in merge request !75
closing in favour of !75
added 1m of time spent
mentioned in commit
d59f20077e
mentioned in commit
23808704ae
Pull request closed