Giter Club home page Giter Club logo

Comments (4)

nbalacha avatar nbalacha commented on July 23, 2024

I have created a second LVMCluster because I thought this would collect the new disks. Now I understand it is only one LVMCluster supported, would this have interfere?

It should not. Do you see any errors in the controller-manager or vgmanager logs files?

from lvm-operator.

jgato avatar jgato commented on July 23, 2024

From the controller-manager:

{
  "level": "error",
  "ts": 1644229480.7411144,
  "logger": "controller.lvmcluster.lvmcluster-controller",
  "msg": "failed to create or update vgManager daemonset",
  "reconciler group": "lvm.topolvm.io",
  "reconciler kind": "LVMCluster",
  "name": "vg-manager",
  "namespace": "lvm-operator-system",
  "error": "failed to update controller reference on vgManager daemonset \"vg-manager\". Object lvm-operator-system/vg-manager is already owned by another LVMCluster controller lvmcluster-sample",
  "stacktrace": "github.com/red-hat-storage/lvm-operator/controllers.(*LVMClusterReconciler).Reconcile\n\t/workspace/controllers/lvmcluster_controller.go:104\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:114\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:311\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:227"
}
{
  "level": "error",
  "ts": 1644229480.7504883,
  "logger": "controller.lvmcluster",
  "msg": "Reconciler error",
  "reconciler group": "lvm.topolvm.io",
  "reconciler kind": "LVMCluster",
  "name": "lvmcluster-sample-2",
  "namespace": "lvm-operator-system",
  "error": "failed reconciling: vg-manager failed to update controller reference on vgManager daemonset \"vg-manager\". Object lvm-operator-system/vg-manager is already owned by another LVMCluster controller lvmcluster-sample",
  "stacktrace": "sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/go/pkg/mod/sigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:227"
}

So it could be the second LVMCCluster creation could be causing problems. Do you want me to delete it?

No errors in the vgmanager.

from lvm-operator.

nbalacha avatar nbalacha commented on July 23, 2024

So it could be the second LVMCCluster creation could be causing problems. Do you want me to delete it?

Yes, please delete the second LVMCluster.

from lvm-operator.

jgato avatar jgato commented on July 23, 2024

Ok, I have cleaned up everything. The second LVMCluster was causing problems and it is something not supported yet.
I have repeated the process:
Phase 1)

  • Everything in a clean stage
  • Operator deployed an LVMCluster created.
  • it detects all the available disks and the VG/PV are created correctly
 Device Class Statuses:
   Name:  vg1
   Node Status:
     Devices:
       /dev/nvme0n1
       /dev/nvme1n1
       /dev/sda
       /dev/sdc
       /dev/sdd
       /dev/sdg
     Node:    master-0.apollo2.hpecloud.org
[root@master-0 core]# vgs                                                                                                                                                                                                                                     
  VG  #PV #LV #SN Attr   VSize VFree                                                                                                                                                                                                                          
  vg1   6   6   0 wz--n- 6.91t 6.90t       
[root@master-0 core]# pvs                                                                                                                                                                                                                                     
  PV           VG  Fmt  Attr PSize   PFree                                                                                                                                                                                                                    
  /dev/nvme0n1 vg1 lvm2 a--  745.21g 745.21g                                                                                                                                                                                                                  
  /dev/nvme1n1 vg1 lvm2 a--  745.21g 745.21g                                                                                                                                                                                                                  
  /dev/sda     vg1 lvm2 a--   <2.73t  <2.72t                                                                                                                                                                                                                  
  /dev/sdc     vg1 lvm2 a--  931.48g 931.48g                                                                                                                                                                                                                  
  /dev/sdd     vg1 lvm2 a--  931.48g 931.48g                                                                                                                                                                                                                  
  /dev/sdg     vg1 lvm2 a--  931.48g 931.48g    

Phase 2)

  • Notice /dev/sde and /dev/sdf were not included initialy. This is ok, because these were not empty.
  • Cleaning both disks but these are still not included into the VG
  • Reboot the sno
  • Now the disks have been included in the VG
# pvs
  PV           VG  Fmt  Attr PSize   PFree  
  /dev/nvme0n1 vg1 lvm2 a--  745.21g 745.21g
  /dev/nvme1n1 vg1 lvm2 a--  745.21g 745.21g
  /dev/sda     vg1 lvm2 a--   <2.73t  <2.72t
  /dev/sdc     vg1 lvm2 a--  931.48g 931.48g
  /dev/sdd     vg1 lvm2 a--  931.48g 931.48g
  /dev/sde     vg1 lvm2 a--  931.48g 931.48g
  /dev/sdf     vg1 lvm2 a--  931.48g 931.48g
  /dev/sdg     vg1 lvm2 a--  931.48g 931.48g

  • But still not recognizable by the LVMCluster
  Device Class Statuses:
    Name:  vg1
    Node Status:
      Devices:
        /dev/nvme0n1
        /dev/nvme1n1
        /dev/sda
        /dev/sdc
        /dev/sdd
        /dev/sdg

from lvm-operator.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.