[UNEXPECTED]Master node for the current patching cycle is node_name.

Error:

Checking for existing adop sessions.
    Continuing with existing session [Session ID: 13].
    [UNEXPECTED]Master node for the current patching cycle is Node_name.
    [UNEXPECTED]Options such as "allnodes=yes" or "allnodes=no action=db" must be run from the master node.
    [UNEXPECTED]Unrecoverable error occurred. Exiting current adop session.


[STATEMENT] Please run adopscanlog utility, using the command

"adopscanlog -latest=yes"

to get the list of the log files along with snippet of the error message corresponding to each log file.


adop exiting with status = 2 (Fail)


Cause:
This issue normally occurs on cloned instance due to invalid entries in ADOP_VALID_NODES and TXK_TCC_RESULTS table.
Refer: http://www.global-dba.com/2017/12/running-adop-fails-with-error-etcc-not.html

Solution:
Login with apps user and perform the following tasks.

SQL> create table apps.ad_adop_sessions_bkp as select * from apps.ad_adop_sessions;

Table created.

update apps.ad_adop_sessions
set node_name='node_name'
where ADOP_SESSION_ID=13

SQL> commit;

Commit complete.

SQL>

Now abort patch session and run cleanup:

$ adop phase=abort
$ adop phase=cleanup cleanup_mode=full

You can now run the patching successfully on cloned instance