Bug 1238244
| Summary: | [New] - Cannot upgrade from rhsc2.16 to rhsc3.1 | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | RamaKasturi <knarra> |
| Component: | rhsc | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED WONTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> |
| Severity: | urgent | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.1 | CC: | mlawrenc, nlevinki, rhs-bugs, sabose, sankarshan, sgraf |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
Upgrade is supported from 3.0 to 3.1, but you cannot upgrade from 2.1 to 3.1.
Workaround:
Reinstall 3.1 on existing deployments of 2.1 and import existing clusters. Refer to the Installation Guide for further information.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-25 07:23:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1216951 | ||
I have tested in the way what has been suggested in comment 2 and things works fine. Here are the steps which i performed: 1) Moved all the hosts to maintenance. 2) Now click on Remove and check force remove button so that cluster will be intact and just gets removed from RHGSC. 3) Installed a new RHEL6.7 machine and installed RHSC 4) Create a cluster of 3.2 and select "Import existing cluster configuration" check box. 5) Provide the IP of one of the node in the cluster. 6) All the hosts and volumes attached to it will be imported. 7) Now stop the volume and move all the nodes to maintenance. 8) Follow the procedure in RHGS installation doc to migrate from 2.1 to 3.1 9) Once the migration is done, edit the cluster compatiblity level to 3.5. 10) Now click on the reinstall button to install the hosts. 11) once nodes are installed, start the volume. Sahina, can you please confirm if we can go ahead with the above steps to migrate from 2.1 to 3.1 so that i can raise a doc bug to change the flow of the migration. If we're updating the nodes to 3.1, the steps 4 to 8 is not required. In the newly installed RHGS-C instance, the user can create a 3.5 cluster and import the updated nodes. Doc text is edited. Please sign off to be included in Known Issues. Minor edit to doc text The process to move from RHSC 2.1.x version to RHSC 3.1 is to re-install rhsc Perform following steps on the RHSC host, to re-install 3.1 1. rhsc-cleanup 2. yum remove rhsc 3. find /usr/share/ovirt-engine/setup/plugins/ -name *.pyc | xargs rm 4. yum update 5. yum install rhsc 6. rhsc-setup 7. Import updated nodes to a 3.5 cluster. Closing this bug as we no longer have updates to 2.1 and upgrade flow from 2.1 has been documented |
Description of problem: When i try to upgrade from 2.1.6 to 3.1 i am facing the issue mentioned below. --> Processing Dependency: rhsc >= 3.0.3 for package: rhsc-setup-plugin-ovirt-engine-3.1.0-0.62.el6.noarch --> Running transaction check ---> Package otopi-java.noarch 0:1.1.2-1.el6ev will be updated ---> Package otopi-java.noarch 0:1.4.0-0.0.1.master.el6ev will be an update ---> Package rhsc-setup-plugin-ovirt-engine.noarch 0:3.1.0-0.62.el6 will be installed --> Processing Dependency: rhsc >= 3.0.3 for package: rhsc-setup-plugin-ovirt-engine-3.1.0-0.62.el6.noarch --> Processing Conflict: rhsc-setup-plugin-ovirt-engine-3.1.0-0.62.el6.noarch conflicts rhsc < 3.0.3 --> Finished Dependency Resolution Error: Package: rhsc-setup-plugin-ovirt-engine-3.1.0-0.62.el6.noarch (RH-Gluster-3-Console) Requires: rhsc >= 3.0.3 Installed: rhsc-2.1.6-0.45.el6rhs.noarch (@rhel-x86_64-server-6-rhs-rhsc-2.1) rhsc = 2.1.6-0.45.el6rhs Error: rhsc-setup-plugin-ovirt-engine conflicts with rhsc-2.1.6-0.45.el6rhs.noarch You could try using --skip-broken to work around the problem Version-Release number of selected component (if applicable): rhsc-2.1.6-0.45.el6rhs.noarch How reproducible: Always Steps to Reproduce: 1. Create a 2.1.6 node 2. Run the migrate script to move from RHN to CDN 3. Add the new rhsc puddles. 4. Run 'yum update rhsc-setup' Actual results: yum update rhsc-setup fails with error described above. Expected results: yum update rhsc-setup should not fail. Additional info: