| 2022-12-19 06:40:20 |
Bob Church |
description |
2022-12-18T23:04:42.862 Debug: 2022-12-18 23:04:41 +0000 Exec[mask kubelet for worker upgrade]: Adding default for path
2022-12-18T23:04:42.864 Error: 2022-12-18 23:04:41 +0000 Syntax error at '4' (line: 1, column: 6) on node compute-0
2022-12-18T23:04:42.866 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:133:in `on_error'
2022-12-18T23:04:42.868 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/lexer2.rb:708:in `scan'
2022-12-18T23:04:42.870 (eval):3:in `_racc_yyparse_c'
2022-12-18T23:04:42.872 (eval):3:in `yyparse'
2022-12-18T23:04:42.874 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:246:in `_parse'
2022-12-18T23:04:42.876 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:140:in `parse_string' |
Brief Description
-----------------
When attempting to upgrade kubernetes on a worker node the following error occurs
2022-12-18T23:04:42.862 Debug: 2022-12-18 23:04:41 +0000 Exec[mask kubelet for worker upgrade]: Adding default for path
2022-12-18T23:04:42.864 Error: 2022-12-18 23:04:41 +0000 Syntax error at '4' (line: 1, column: 6) on node compute-0
2022-12-18T23:04:42.866 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:133:in `on_error'
2022-12-18T23:04:42.868 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/lexer2.rb:708:in `scan'
2022-12-18T23:04:42.870 (eval):3:in `_racc_yyparse_c'
2022-12-18T23:04:42.872 (eval):3:in `yyparse'
2022-12-18T23:04:42.874 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:246:in `_parse'
2022-12-18T23:04:42.876 /usr/lib/ruby/vendor_ruby/puppet/pops/parser/parser_support.rb:140:in `parse_string'
Severity
--------
Provide the severity of the defect.
<Critical: System/Feature is not usable due to the defect>
<Major: System/Feature is usable but degraded>
<Minor: System/Feature is usable with minor issue>
Steps to Reproduce
------------------
Write down the steps to reproduce the issue
Expected Behavior
------------------
Write down what was expected after taking the steps written above
Actual Behavior
----------------
State what is the actual behavior
Reproducibility
---------------
<Reproducible/Intermittent/Seen once>
State if the issue is 100% reproducible, intermittent or seen once. If it is intermittent, state the frequency of occurrence
System Configuration
--------------------
<One node system, Two node system, Multi-node system, Dedicated storage, https, IPv4, IPv6 etc.>
Branch/Pull Time/Commit
-----------------------
Branch and the time when code was pulled or git commit or cengn load info
Last Pass
---------
Did this test scenario pass previously? If so, please indicate the load/pull time info of the last pass.
Use this section to also indicate if this is a new test scenario.
Timestamp/Logs
--------------
Attach the logs for debugging (use attachments in Launchpad or for large collect files use: https://files.starlingx.kube.cengn.ca/)
Provide a snippet of logs here and the timestamp when issue was seen.
Please indicate the unique identifier in the logs to highlight the problem
Test Activity
-------------
[Sanity, Feature Testing, Regression Testing, Developer Testing, Evaluation, Other - Please specify]
Workaround
----------
Describe workaround if available |
|
