Oidc-auth-app Apply Failed After Hugepage Addition And Unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Medium
|
Jerry Sun |
Bug Description
Brief Description
-----------------
Oidc-auth-manifest apply failed, after adding 1G hugepages and unlock the system.
Severity
--------
Major, Minor
Steps to Reproduce
------------------
1) Lock the system (system host-lock 1)
2) Modify hugepages (system host-memory-modify -1G 6 1 0 , system host-memory-modify -1G 6 1 1)
3) unlock the system. (system host-unlock 1)
....
TC-name: None (config change)
Expected Behavior
------------------
Expected the oidc-auth-manifest to be in applied state.
Actual Behavior
----------------
oidc-auth-manifest app is in apply-failed state with reason:Command '['helm', 'install', '--dry-run', '--debug', '--values', '/tmp/tmpfoOTkQ', '-- values', '/tmp/tmpc8k702', '/tmp/tmpI3L2OL']' returned non-zero exit status 1
Reproducibility
---------------
Reproducible
System Configuration
-------
One node system - IPV6
Branch/Pull Time/Commit
-------
2020-03-29
Last Pass
---------
N/A
Timestamp/Logs
--------------
2020-04-
Sat Apr 11 04:19:27 UTC 2020 (system host-unlock)
Test Activity
-------------
SystemTest
Workaround
-------------
Apply the application again.
tags: | added: stx.apps |
tags: | added: stx.retestneeded |
tags: | removed: stx.retestneeded |
Nimalini,
Can you clarify if the manifest failure is reproducible on lock/unlock w/o changing the hugepage configuration? It's not clear why these two actions are related.