Anders,The error which you are seeing is not related to your TOTP issue. It looks like, based on the container name, that you are attempting to run the reload command from within the configuration container. This command is not really designed to be run from within the configuration container as the configuration container should always be running with the latest configuration.So, you can ignore this error and will instead need to focus on the TOTP issue.I hope that this helps.Scott A. ExtonSenior Software EngineerChief Programmer - IBM Security Access ManagerIBM Master Inventor
Anders,I just had another quick look and something very strange is going on in your environment. The reload command should work successfully in a configuration container - even if it doesn't really do anything useful. In my environment the reload command works fine, even if I enable the DSC. You might need to open a support ticket to get the support team to investigate the issue. Thanks.Scott A. ExtonSenior Software EngineerChief Programmer - IBM Security Access ManagerIBM Master Inventor
# What's new in verify-access v1.3.0 Chart
The following enhancements have been made:
* Support for function-specific containers
* Support to set service name (which is hostname)
* Added startupProbe for config and runtime containers
* Allow service type to be set per WRP instance
* Improvements to NOTES.txt
For detailed documentation instructions go to [https://www.ibm.com/support/knowledgecenter/en/SSPREK/welcome.html](https://www.ibm.com/support/knowledgecenter/en/SSPREK/welcome.html).
# Required configuration changes for lightweight containers
The new lightweight runtime container in v10.0.2.0 does not listen on port 443. Instead it listens on port 9443. You will need to update junctions and WRP configuration items that reference the runtime to set this new port.
The new lightweight DSC containers in v10.0.2.0 do not listen on ports 443 and 444. Instead they listen on ports 9443 and 9444. You will need to update you cluster configuration to reflect this change.
The new lightweight reverse proxy container in v10.0.2.0 does not listen on port 443. Instead it listens on port 9443. You may need to update ingress or loadbalancer configurations to reflect this.
----Also, since changes were made in v1.2.1 too, here's the release notes from that version too:---
# What's new in verify-access v1.2.1 Chart
* Ability to set timezone for containers
* Ability to set port for NodePorts
* Change to preferred antiAffinity to allow for in-place upgrade
* Mark PVCs as "keep" so not deleted with release
* Change to Reverse Proxy definition to allow per-instance settings
# Values migration
In previous versions the Reverse Proxy instances were defined with an array containing a list of instance names. e.g.
In this version, the array must now contain a list of instances with attributes defined for each instance. The `name` attribute is required. Other optional attributes are `nodePort` and `replicas` e.g.```
- name: rp1
- name: rp2
Waiting with interest to hear how you get on with the ingress configuration. Hopefully it will be simple enough to get working.