Description of problem: This is to track cellv2 multicell deployment in tls-everywhere environment. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Re-requesting blocker flag: given the discovered scope of the multi-cell issues (either tls-e, or not), there would be no multi-cell v2 feature in OSP17, until we set this bz and bz #2089512, that blocks its verification, as blockers.
Let me clarify, this is a regression that would block multi-cell v2 upgrades. I'm not sure why this had been created as an RFE in the first place, since multi-cell v2 GA'ed as of osp16. Perhaps we should rename this to "Multi-cell v2 in tls-everywhere environment" (no RFE), or even just "Multi-cell v2 on undercloud w/o Nova"
I0216dd555eacbcb37abd03a67fdd39f9244285db looks missing in downstream repos
It's all set, fixed the build versions now!
To effectively communicate the issue and receive appropriate help, please provide the following information: Version-Release Number: Specify the version and release number of the component or software you are using. https://www.myaarpmedicares.us/ This helps identify the specific version that may be causing the issue. Reproducibility: Indicate how frequently the issue occurs. Is it consistently reproducible, or does it happen sporadically? Steps to Reproduce: Provide a detailed description of the steps you took before encountering the problem. This should include any specific configurations, actions, or commands you executed. Actual Results: Explain the behavior or error messages you observed when following the steps to reproduce the issue. Expected Results: Describe the expected outcome or behavior that you were anticipating. Additional Information: Include any other relevant details that may help in understanding or resolving the problem. By providing these details, it will be easier for others to understand and assist with your specific issue.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577