Sean, I cloned 1775246 as TestOnly for NFV with a target of RHOSP 17. I have marked DFG:NFV in the internal whiteboard so I'm not sure why a DFGCOMPUTE JIRA task was created and not an NFV JIRA task. That is how I m flagging this work for NFV. You can disregard the DFGCOMPUTE jira task that was created while I try and figure out why an NFV JIRA task was not created. I tried and scrubbing out all other references/indicators that would put this as a NOVA task in an effort to keep it only for NFV. Do you see soemting else I can modify in this BZ?
Do you think I should have cloned 1700412 rather than 1775246 if we're trying to verify this in RHOSP 17 or 1775246 is fine for our purpose?
if you use the copy function instead of clone i think it will cause less issues. the compute jira task was created because there was a short window while the dfg was set to compute
and the jira sync task ran. either would be fine but i think using copy instead of clone might be better as it wont copy the metadata in the internal whiteboard