So, this is merged to OSP-10. As there is a workaround for OSP-9, can we change the Target Release to osp-10 from osp-9, i.e. not merge to osp-9?
(In reply to Bob Fournier from comment #3) > So, this is merged to OSP-10. As there is a workaround for OSP-9, can we > change the > Target Release to osp-10 from osp-9, i.e. not merge to osp-9? Its already fixed in RHOS10 . https://bugzilla.redhat.com/show_bug.cgi?id=1428005
>> So, this is merged to OSP-10. As there is a workaround for OSP-9, can we >> change the >> Target Release to osp-10 from osp-9, i.e. not merge to osp-9? >Its already fixed in RHOS10 . >https://bugzilla.redhat.com/show_bug.cgi?id=1428005 Yes as I indicated this is fixed in OSP-10, but this bug is targeted to OSP-9. Can we just use the workaround for OSP-9 and not merge this fix?
Thanks a lot Jaison. I'm going to close this then as we have a separate BZ for OSP-10 that tracks the fix.