Unable to add port 1/1/2 to auto-vfl-link-ports on OS6865-P16X

[dartzen]

Hello together,

I have a strange behavior on a OS6865-P16X running software version 8.10.102.R01. The switch was the only one in the standard VC configuration and with an existing configuration. In this config the ports 1/1/1 and 1/1/2 (this are the 2 10G ports) are part of a LACP. Now I wanted to add a second OS6865-P16X (same software version) and extend the virtual chassis. On the new switch I configured the chassis-id as 2 and configured port 1/1/2 as an auto-vf-port. That worked fine. On the existing switch I removed port 1/1/2 from the linkagg with the command "no linkagg lacp port 1/1/2" after disconnecting the SFP. Then I wanted to add this port as auto-vf-port with the command "virtual-chassis auto-vf-link-port 1/1/2", but the switch refuses this with the error: "Unable to set VFL port property. Remove other configuration on this port". The thing is, I can't find any config on that interface, it is only part of default vlan 1, no tags, no UNP-configuration. I even did a "show configuration snapshot | grep 1/1/2", but there was no result. So for me it seems that there is no additional config on this port. The only thing I did not do was a reboot (since we are a 24/7 producing company I can't reboot easily), but I have found nothing in the docs that this would be necessary.
Can anyone of you give me a hint why I can't add that port to the auto-vf-ports?

Thanks in advance.
Best regards
Daniel

[dartzen]

OK, we could solve the problem but this is either a bug in this version or I am not understanding something right. My co-worker rebooted the switch this morning, but the error persisted. He then changed the untagged VLAN on port 1/1/2 to another VLAN (it was in the default VLAN 1 originally) and after that it was possible to add the port to the auto-vf-ports. The VC is now correctly running with the additional switch.
I still don't really understand this, since for me it makes no sense that there is a different behavior depending on which VLAN the port is in. But either way it works now.