Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-7673

[RFE] Only allow setting resource meta attributes which are valid

    • FutureFeature
    • sst_high_availability
    • ssg_filesystems_storage_and_HA
    • 8
    • False
    • Hide

      None

      Show
      None
    • None
    • If docs needed, set a value
    • None

      Description of problem:

      There are no error checks or warnings when setting invalid resource meta attributes. This can lead to unexpected behaviors for users who believed they set a valid option.

      Version-Release number of selected component (if applicable):

      $ rpm -q pcs
      pcs-0.10.8-1.el8.x86_64

      How reproducible:

      Set an invalid meta attribute to either a specific resource or for resource defaults:

       

      [root@clusterb-rhel8 ~]# pcs resource defaults update resource-sti=1000
      Warning: Defaults do not apply to resources which override them with their own defined values
      [root@clusterb-rhel8 ~]# pcs resource update dummy1 meta resource-sti=100
      

       

      Actual results:

      This results in an update to the configuration, but the values won't actually do anything since the attribute are invalid:

      [root@clusterb-rhel8 ~]# pcs config
      ---------------->8--------------------
      Resources:
      Resource: dummy1 (class=ocf provider=heartbeat type=Dummy)
      Attributes: fake=1
      Meta Attrs: resource-sti=100
      ---------------->8--------------------
      Resources Defaults:
      Meta Attrs: rsc_defaults-meta_attributes
      resource-sti=1000
      resource-stickiness=1000

      Expected results:

      A warning or error that prevents an update to configuration, and requests additional "--force" option to set invalid values.

            tojeline@redhat.com Tomas Jelinek
            rhn-support-jobaker Joshua Baker
            Tomas Jelinek Tomas Jelinek
            Cluster QE Cluster QE
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated: