Back to bug 1323740
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Red Hat Bugzilla Rules Engine | 2016-04-04 15:02:57 UTC | Keywords | ZStream | |
| Soumya Koduri | 2016-04-04 15:21:31 UTC | CC | sraj | |
| Flags | needinfo?(sraj) | |||
| Shashank Raj | 2016-04-05 07:02:27 UTC | Flags | needinfo?(sraj) | |
| Shashank Raj | 2016-04-05 07:09:26 UTC | Blocks | 1323947 | |
| Soumya Koduri | 2016-04-05 07:12:03 UTC | Blocks | 1323947 | |
| Depends On | 1323947 | |||
| Niels de Vos | 2016-04-05 13:59:56 UTC | Keywords | SELinux | |
| Flags | needinfo?(sraj) | |||
| Shashank Raj | 2016-04-07 12:21:04 UTC | Flags | needinfo?(sraj) | |
| Niels de Vos | 2016-04-07 15:48:32 UTC | CC | pprakash | |
| Flags | needinfo?(sraj) | |||
| Soumya Koduri | 2016-04-11 11:25:17 UTC | Summary | nfs-ganesha.service status shows "failed to connect to statd" after node reboot | [SELinux]nfs-ganesha.service status shows "failed to connect to statd" after node reboot |
| Prasanth | 2016-04-13 06:47:50 UTC | QA Contact | storage-qa-internal | sraj |
| Prasanth | 2016-04-13 08:30:28 UTC | Flags | needinfo?(sraj) | |
| Shashank Raj | 2016-04-13 16:15:17 UTC | Flags | needinfo?(sraj) needinfo?(sraj) | |
| Rahul Hinduja | 2016-04-14 10:33:08 UTC | CC | rhinduja | |
| Blocks | 1311817 | |||
| Alok | 2016-04-18 17:21:49 UTC | CC | asrivast | |
| Red Hat Bugzilla Rules Engine | 2016-04-18 17:40:24 UTC | Target Release | --- | RHGS 3.1.3 |
| Lukas Vrabec | 2016-05-03 14:04:44 UTC | Depends On | 1332577 | |
| Shashank Raj | 2016-05-05 09:21:08 UTC | CC | lvrabec | |
| Kaleb KEITHLEY | 2016-05-05 11:34:22 UTC | Status | NEW | ASSIGNED |
| Assignee | rhs-bugs | kkeithle | ||
| Kaleb KEITHLEY | 2016-05-05 12:22:43 UTC | Status | ASSIGNED | POST |
| Kaleb KEITHLEY | 2016-05-05 12:46:24 UTC | Flags | needinfo?(lvrabec) | |
| Kaleb KEITHLEY | 2016-05-05 12:50:01 UTC | Status | POST | MODIFIED |
| Lukas Vrabec | 2016-05-05 13:11:30 UTC | Flags | needinfo?(lvrabec) | |
| Soumya Koduri | 2016-05-09 05:58:10 UTC | Status | MODIFIED | ON_QA |
| Fixed In Version | nfs-ganesha-2.3.1-5, selinux-policy-3.138.1-70 | |||
| Kaleb KEITHLEY | 2016-05-09 18:54:55 UTC | Flags | needinfo?(lvrabec) | |
| Prasanth | 2016-05-10 09:57:14 UTC | Depends On | 1333875 | |
| Fixed In Version | nfs-ganesha-2.3.1-5, selinux-policy-3.138.1-70 | nfs-ganesha-2.3.1-5, selinux-policy-3.13.1-60.el7_2.4 | ||
| Lukas Vrabec | 2016-05-10 11:31:47 UTC | Flags | needinfo?(lvrabec) | |
| Kaleb KEITHLEY | 2016-05-10 16:51:35 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1334760 | |
| Shashank Raj | 2016-05-11 08:56:58 UTC | Status | ON_QA | VERIFIED |
| Jiffin | 2016-05-19 07:07:15 UTC | Doc Text | Cause: The /var/lib/nfs symlink was mislabeled(should be labeled var_lib_nfs_t instead of var_lib_t), also certain selinux rules were missing Consequence: nfs-ganesha.service status shows "failed to connect to statd" after node reboot Fix: In new selinux policy, proper rules were written which fixes the issue Result: nfs-ganesha and nfs-ganesha-lock service is not going in failed state and no denial AVC's are seen in audit.log. |
|
| Marie Hornickova | 2016-06-02 08:58:02 UTC | CC | mdolezel | |
| Docs Contact | mdolezel | |||
| Doc Text | Cause: The /var/lib/nfs symlink was mislabeled(should be labeled var_lib_nfs_t instead of var_lib_t), also certain selinux rules were missing Consequence: nfs-ganesha.service status shows "failed to connect to statd" after node reboot Fix: In new selinux policy, proper rules were written which fixes the issue Result: nfs-ganesha and nfs-ganesha-lock service is not going in failed state and no denial AVC's are seen in audit.log. | Due to missing rules in Gluster SELinux policy, the nfs-ganesha service failed to connect to the rpc.statd daemon after the nfs-ganesha node reboot. The underlying code has been fixed, and nfs-ganesha no longer fails in the described scenario. | ||
| Marie Hornickova | 2016-06-07 13:36:37 UTC | Doc Text | Due to missing rules in Gluster SELinux policy, the nfs-ganesha service failed to connect to the rpc.statd daemon after the nfs-ganesha node reboot. The underlying code has been fixed, and nfs-ganesha no longer fails in the described scenario. | Due to missing rules in the Gluster SELinux policy, the nfs-ganesha service failed to connect to the rpc.statd daemon after a node reboot in the situation where the nfs-ganesha server was installed on four nodes. The underlying code has been fixed, and nfs-ganesha no longer fails in the described scenario. |
| errata-xmlrpc | 2016-06-23 00:59:30 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-06-23 05:35:06 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-06-23 01:35:06 UTC | |||
| John Skeoch | 2016-11-08 03:53:17 UTC | CC | sashinde |
Back to bug 1323740