Override Tag starts up instance with an active schedule #42
Description
Hello,
I have set up override tags in addition to the Weekday and Weekend tags. I ran the script with the Up command with an override tag. It powered on the intended instance, but also powered on another instance with a that was already shut down, but had an active schedule. The unintended instance had a different override tag than the one I used in the command.
Intended instance:
Checking banner-oci14 (Instance) CurentState: STOPPED...
- Active schedule for banner-oci14: 1,1,1,1,1,1,1,1,1,[1],1,1,1,1,1,1,1,1,1,1,1,1,1,1,
- Initiate Compute VM startup for banner-oci14
Unintended instance:
Checking cleanaddr-oci01 (Instance) CurentState: STOPPED...
- Active schedule for cleanaddr-oci01: 0,0,0,0,0,0,0,1,1,[1],1,1,1,1,1,1,1,1,1,0,0,0,0,0,
- Initiate Compute VM startup for cleanaddr-oci01
banner-oci14 and cleanaddr-oci01 are both configured with the same schedule tags.
I am using the override tag to allow only a specific test environment to stay online ad-hoc.
Any help will be greatly appreciated!
Thank you!